Chapter 6. Resolved Issues

6.1. Resolved Issues

This release of JBoss Data Grid resolves the following issues:

JDG-1739 - Socket Connections Leak When Unknown Host Exceptions Occur: In cases where the Hot Rod client continually attempted to connect to unknown or invalid hosts, socket connections were left open. This issue was observed when the org.infinispan log level was set to TRACE.

JDG-1768 - JBoss Data Grid Expiration Values Do Not Apply to Requests from REST API: Expiration values did not apply to requests to the JBoss Data Grid REST interface if headers were not included in the requests.
JDG-1143 - Merge Function Does Not Work as Expected for the Simple Cache Interface: The Merge method did not work as expected in the simple Cache interface.
JDG-1127 - Error Occurs for Spatial Query Requests under High Load: An org.hibernate.search.exception.SearchException error would occur if multiple queries with different query parameters were run concurrently.
JDG-1039 - Hot Rod Clients Cannot Resolve Topology Addresses After Connection Failure: In dynamic environments where JBoss Data Grid nodes restart with different IP address assignments, Hot Rod clients would fail to reconnect and could not resolve the IP addresses for the nodes.
JDG-1026 - Not Possible to Set the CompatibilityProtoStreamMarshaller Class: It was not possible to set the compatibility marshaller to CompatibilityProtoStreamMarshaller.

JDG-1122 - Writes Via Memcached Server Result in UnknownOperationException: In some cases, when using JBoss Data Grid as a memcache service in an application, an UnknownOperationException exception would occur and data would not be stored when writing key value pairs of different sizes.

JDG-954 - Ickle full text range query fails with numbers: Due to a bug in QueryRenderer, a full text range query with numbers as the range would result in a NullPointerException.
JDG-989 - Cache templates with Type fail when they enable indexing: In certain cases when using indexing with cache templates, a NullPointerException could be thrown.
JDG-952 - Null values are counted in remote queries with aggregations: When using the Hot Rod client, if a field was annotated with Store.YES, null values using the field would be counted.
JDG-893 - Implement @Analyzer and @Field.analyzer for protobuf: The @Analyzer and @Field.analyzer annotations were already recognized but they were not honored.
JDG-663 - Operator '-' doesn’t work in fulltext querying: When running a query like from Entity t where t.longDescription : (-'really'), all entities that didn’t contain the word really should have been printed, but they weren’t.
JDG-664 - Right operand in term query is not being analyzed: With the default configuration and the default analyzer, queries should be "lower-cased." For example, the following two queries should return the same results: from Entity where longDescription:'rent' and from Entity where longDescription:'RENT'. In reality, these queries did not return the same results.