Changelog History
Page 97
-
v1.7.9 Changes
January 24, 2013(RB=129334) ➕ add try/catch to PropertyEvent runnables, add UnhandledExceptionHandler to NamedThreadFactory
(RB=129193) 🛠 fix a bug where the LoadBalancer config gets overwritten by empty map and causes D2 Strategy to not instantiate properly
(RB=123406) 🔄 Change to allow clients to request data in pson-encoded format (and interpet pson-encoded data), and for servers to be able to send pson-encoded responses.
Clients can signify that a response should be in pson format by sending the request with the header "Accept-Type : application/x-pson". The server will then encode the result in pson and send it back with the header "Content-Type : application/x-pson". If the client recieves a response with this header it will decode it with the pson codec.
Some headers will now work a bit differently: Content-Type headers will no longer be sent with responses unless there is actual body content to encode. This change was made primarily to simplify picking the right header. There's no point in trying to figure out the right content-type header to send back if there isn't actually any content to send. 0️⃣ Accept-Type headers can now be sent with requests. The default client won't send Accept-Type headers (same as the old code), but users can use the new RestClient constructor to create a client that will send Accept-Type headers. Right now there are four basic options for Accept-Type headers:
- no header: server will send back result as application/json. This is required for backwards compatibility.
- application/json highest quality in header: server will send back result as application/json
- application/x-pson highest quality in header: server will send back result as application/x-pson. If the server code is old, result will be sent back as application/json
- / highest quality in header: for now, server will send back result as application/json, if no other accept types are found. However, the server will prefer to send back responses in formats that are explicitly mentioned in the header, even when they are lower quality than /
(RB=128653) ActionResponseDecoder.getEntity() will return Void.class if its fieldDef is null, to preserve compatibility from before the Action response changes.
(RB=128251) ➕ Add javadoc to rest.li docgen and include restspec.json files as resource in rest.li server jars.
-
v1.7.8 Changes
January 16, 2013(RB=119453) ➕ Add default value handling for query parameter in complex type, including all DataTemplate subclasses, array of simple types and complex types. Union can be used as query parameter type.
(RB=127439) 🛠 Fix NPE resulting from calling .getEntityClass() on an ActionResponseDecoder for a void-returning Action.
-
v1.7.7 Changes
December 21, 2012(RB=123370) ➕ Add TextDataCodec to support serializing and deserializing to String, Writer and Reader. 🚚 Move getStringEncoding() from DataCodec to TextDataCodec interface. This is potentially a backwards incompatible change.
Replace use of ByteArrayInputStream(string.getBytes(Data.UTF_8_CHARSET)) with new JacksonDataCodec 📜 and SchemaParser APIs that take String as input.
-
v1.7.6 Changes
December 20, 2012(RB=122933) If union is named because it is typeref'ed, the typeref schema was originally not available through the generated code. This change ➕ add a new HasTyperefInfo interface. If the union is named through through typeref, the generated subclass of UnionTemplate will also implement this interface. This interface provides the TyperefInfo of the typeref that names the union.
(RB=121895) 🛠 Fix encoding bug in QueryTunnel Util. ✅ Make ByteString.toString() to return a summary instead of the whole array as an Avro string. 🌲 HttpBridge for RPC requests should not log the whole entity. ✂ Remove Entity body from Request/Response toString().
(RB=122813) restli-docgen displays all nested subresources and related models in the JSON format.
-
v1.7.5 Changes
December 18, 2012(RB=122512) 🚚 Move PsonDataCodec from test to main source dir.
-
v1.7.4 Changes
December 17, 2012(RB=122372) 📜 RequestContext should not be shared across requests in ParSeqRestClient
-
v1.7.3 Changes
December 17, 2012(RB=122016) Add support for Avro 1.6. To use Avro 1.6, depend on data-avro_1_6. Also fix getBytes() to explicitly specify UTF-8. This has no impact 0️⃣ on platforms whose default encoding is UTF-8.
(RB=121948) ➕ Add DataList serialization and deserialization to JacksonDataCodec.
-
v1.7.2 Changes
December 13, 2012(RB=120743) Infer order of include and fields properties of record if location information is not available.
🔄 Change generated and up-to-date log messages to info. This was useful initially for debugging. Since 🏗 it has not been a problem, changing to info will reduce build output noise from generator.
(RB=120925) ➕ Add requisite maven configuration and pom generation to root build.gradle to enable releasing pegasus to maven central.
(RB=120249) 🔌 Copy 'pegasus' gradle plugin into pegasus codebase from RUM, so 3rd party developers have access to 🏗 the build tools required for a working development flow. Also add maven central and maven local as repos 🏗 so developers can publish pegasus artifacts to their local repo and build standalone apps based on those artifacts (this part will not be needed after we push pegasus artifacts to the maven central repo but helps in the short term).
(RB=119121) 🛠 Fixed an issue where Actions that declare their return types as primitives (return int instead of Integer, for example) no longer fail while trying to coercer the response into the correct type.
-
v1.7.1 Changes
December 13, 2012- 🏗 Bad build, not published
-
v1.7.0 Changes
December 10, 2012(RB=116297) ➕ Add Schema compatibility checker. See com.linkedin.data.schema.compatibility.CompatibilityChecker and CompatibilityOptions for details.
There is a change in MessageList class to take a type parameter. This is binary compatible but may ⚠ result in unchecked compilation warning/errors (depending on compiler setting.) Impact should be minimum since this class is mostly for use within pegasus. However, it leaked by data-transform 📦 package by DataProcessingException. This has been fixed to use List instead of MessageList.
(RB=118831) ⬇️ In idl compatibility checker, allow parameter optional to be upgraded to default, and allow default to be downgraded to optional.
(RB=119617) ➕ Add PageIncrement.FIXED to better support post-filtered search result paging.