DataStax Enterprise 3.1.x release notes cover these releases:
This release includes the following changes and enhancements:
Pig CQL 3 push down filter (DSP-2214)
Support for CQL collections in Pig (DSP 2373, DSP-2360)
Enforced syntax for flags, such as -h, prefaced by a hyphen. These flags must come before other dsetool command arguments. (DSP-2430) For example:
dsetool -h 127.0.0.1 ring
Error logging of Solr request errors that includes parameters sent. (DSP-2450)
Counting now performed when the commit log stores and replays Solr entries. A new CommitLog-core.name mbean publishes the counters, named entries and replayed. (DSP-2454)
Finalized finalized Pig formatting syntax, which differs from that of DSE 3.1.2-3.1.3 and conforms to Cassandra 1.2.10. (DSP-2464)
Includes tuning knobs for dealing with large blobs and many CFs (CASSANDRA-5982, DSP-2470)
Fixes the issue that deletes snapshots in use during snapshot repair. (CASSANDRA-6011, DSP-2489)
Updated version of Cassandra to 1.2.10 (DSP-2504)
This release fixes the following issues:
After deleting Solr data by dropping table using the CQL DROP TABLE command, or by manually deleting the Solr index directory, you needed to shut down and restart the server before attempting to recreate the Solr core. In this release, after dropping the table, you can upload the Solr schema and configuration and create the Solr core. (DSP-2024)
The issue causing DataStax Enterprise to crash when you added client_encryption_options to the dse.yaml file has been resolved. In this release, when you attempt to add these options to the dse.yaml file, an error message results. (DSP-2279)
The incorrect default gc_grace storage parameter for Cassandra tables has been corrected from 60 seconds to 10 days. (DSP-2342)
Added missing information in User resource limits. (DSP-2344)
The issue that prevented MapReduce Jobs from running longer than 24 hours on kerberized clusters is resolved. (DSP-2402)
Under certain circumstances the DataStax Enterprise service reported a failed exit status when the service actually started. This issue has been resolved. (DSP-2422)
The issue causing Pig to return an extraneous empty tuple has been resolved. (DSP-2424)
Fixed race condition between CFS compaction and nodetool scrub. (DSP-2425)
The issue causing complex Hive and Pig queries to cause a deadlock has been resolved. (DSP-2434)
The back-pressure implementation has been enhanced to improve indexing performance in the following ways: (DSP-2447)
Scrubbing SSTables in the CassandraFS erroneously removed information about CassandraFS files. This caused SSTables containing deleted CassandraFS files to accumulate despite compaction or other cleanup operations. This issue has been resolved. (DSP-2472)
The issue causing Solr multivalued date fields to malfunction has been resolved. Multivalued date fields now work. (DSP-2480)
The issue caused by pending compactions causing nodes to die as if disk space was low has been resolved. Cassandra-5605 has been backported to this release. (DSP-2485)
Liveness issues calling CassandraSolrConfig#getColumnLimit under high concurrency have been resolved. (DSP-2494)
The issue causing the ShardRouter to write many messages to the system.log has been resolved. (DSP-2495)
Solr core resource management has been made more robust. Core loading/creation/reload no longer fails at the first attempt when resource loading/writing fails. (DSP-2505)
The issue with inserting a NULL value using Hive, for example when import data into Cassandra, has been resolved. (DSP-2521)
Making a mistake when typing a Pig LOAD command, for example, a mistake in the kesypace name, would cause not only the mistaken command to fail, but also the next, corrected command to fail with the same message, for example:
Unexpected internal error. InvalidRequestException(why:Keyspace 'ks1' does not exist.)
This issue has been resolved. (DSP-2527)
The following issues are present in this release:
This release fixes the following issues:
This release includes the changes, enhancements, and resolved issues.
DataStax Enterprise 3.1.2 exposes the com.datastax.bdp:type=ShardRouter Mbean.
The cassandra-stop command provides a convenient way to stop a stand-alone process on a node:
From the install location:
In this release, you can determine the status of the Solr indexing process from log files.
A Cassandra issue can cause a problem when decommissioning a node that interferes with streaming data from the node to SSTables. The workaround is to decommission the node and then repair the cluster. The efficient and recommended way to repair a node, or cluster, is to use the subrange repair method.
This release resolves these issues:
Release 3.1.1 resolves this issue:
The issue that causes a Solr startup problem when a PropertyFileSnitch or GossipingPropertyFileSnitch is used is resolved. (DSP-2283)
Thread stack size. To avoid StackoverflowErrors, you may need to set the JVM option -Xss to 190k or higher in the cassandra-env.sh file:
Capability to perform a relatively fast repair of a subrange instead of repairing the entire range, which can incur a time-consuming, full re-index of Solr data.
Although announced in a minor release of DataStax Enterprise 3.0, this enhancement is listed here to raise awareness of its availability and use. Using the faster process to repair subranges is recommended for handling inconsistencies in Solr query results and for handling other problems.
Support for docValues, introduced in Solr 4.2, in the schema field definition.
Change to the DSE Search/Solr ttl rebuild timeout properties, which ensures purging of expired data from Solr indexes. New options are:
The ttl (time-to-live) field format and query on the Lucene side has not changed, so upgrading to DataStax Enterprise 3.1 is not affected by this change.
Configurable TTL for a field or document using the Solr HTTP API.
Configurable column limit prevents out of memory errors by controlling the maximum number of indexed columns overall, not just dynamic field columns, as well as columns returned during queries. Effective only when using dynamic fields.
Per-segment caching for filters and docsets, which improves real-time search performance.
The dseTypeMapping version includes a force option <changing-solr-type> (for use by experts only).
Solr shard routing has been changed resulting in a slightly improved throughput and query times on Solr clusters, but not when using Vnodes.
DSE Search Solr distributed delete and search performance has been improved using a technique that loads only the unique key and explicitly requested fields.
Solr integration will not work with PropertyFileSnitch or the GossipingPropertyFileSnitch. This limitation will be removed as soon as possible. (DSP-2283)
GLIBCXX_3.4.9 not found. This error may appear in older Linux distributions when installing DSE from the binary tarball. The workaround is to replace snappy-java-1.0.5.jar with snappy-java-188.8.131.52.jar. (DSP-2189)
Do not run MapReduce jobs while the cluster is in a partially upgraded state or fail to observe any other limitations during upgrading.
Before upgrading a cluster in which you have decommissioned a node, follow the relevant steps in Recommissioning a node.
Issuing a DESCRIBE SCHEMA command on an Analytics node results in an error message on the cqlsh command line that you can ignore: (DSP-2268)
Don't know how to parse type string u'org.apache.cassandra.db.marshal.DynamicCompositeType (t=>org.apache.cassandra.db.marshal.TimeUUIDType, . . .
The cqlsh DESCRIBE command can produce ddl that has the wrong parameters in it. If compression is not set for a table, cqlsh omits the compression attribute. If you rename the table and issue the DESCRIBE command again, the Snappy compression setting appears. This may occur with other parameters.(CASSANDRA-5766)