Changes in 12cR1.4.0.9

The following changes were made in Oracle NoSQL Database 12cR1.4.0.9.

New Features

  1. Added the ability to define a Time To Live (TTL) on an individual table row. The TTL can be defined in terms of hours or days and can be declared as a default on a table or applied per-row on put operations. Applying a TTL to a row results in an absolute expiration time on that row after which it will not be available. The expiration time is available using new API on Row. [#24743]

  2. Includes a preview release of an SQL-like declarative query language, called ONQL, that can be used to access data in tables in a read-only fashion. As a preview release its use and feedback is encouraged. We expect that additions and changes done for a later formal release will be backward-compatible with this preview, however we cannot rule out minor incompatibilities.

    As of this preview release the language supports SELECT-FROM-WHERE-ORDERBY queries that can perform projection, predicate-based filtering, simple arithmetic operations, index-based sorting, and path expressions for navigating and projecting out data from complex structures (records, arrays, and maps). Bind variables are also supported for reuse of prepared queries.

    The ONQL processor performs all operations on the server side and automatically takes advantage of primary and secondary indexes to increase query performance. The language also supports hints to allow users to explicitly choose an index for a query, in cases where the query processor is not making the best choice among the multiple indexes applicable to a query.

    In addition a new ONQL shell has been added to facilitate use of the query language in an interactive, command line interface. [#24186]

  3. Added Export/Import utility. Export utility allows a user to export the contents from Oracle NoSql Store to an external export store (Local File System / Oracle Storage Cloud Service). Import utility allows a user to import the contents from an external export store (Local File System / Oracle Storage Cloud Service) to Oracle NoSQL store. [#24734]

  4. Added a preview release of integration with Elasticsearch to provide full text search indexing. Text indexes can be added to tables in Oracle NoSQL Database, which will cause a corresponding index in an attached Elasticsearch cluster to be populated and maintained. [#23733]

    To use this feature, users must first make available on the network an Elasticsearch 2.0 cluster, and register the cluster with the NoSQL Store. This enables use of the CREATE FULLTEXT INDEX DDL command.

  5. Added mechanism to support creating statistics tables automatically at the end of the existing plan deploy-topology. [#24768]

  6. Added a predicate pushdown mechanism to the Oracle NoSQL Database Table API Hive Integration classes. Specifically, a mechanism was added which supports the decomposition of a Hive or Big Data SQL query's WHERE clause (the predicates) into information that can be passed to the KVStore database so that some/all search processing can be performed in the database itself rather than in the processing performed on the client side of the query. [#24525]

  7. Added a non-interactive login mode for command line utilities like Admin command line interface and Ping utility. Setting the login property introduced this release, "oracle.kv.password.noPrompt" as true, the non-interactive login mode will be enabled. If users are not using password store and configuring login properties incorrectly, the utilities would directly exit without automatically prompting password or user name like previous releases. [#24931]

  8. Added a new example that demonstrates how to perform Kerberos authentication on the client side. [#24328]

  9. Ranges declared on fields in DDL "CREATE TABLE" expressions are no longer supported. In previous releases it was possible to declare range constraints on fields in tables. This was done using the data definition language (DDL) keyword "CHECK" and providing a range. The primary intent of this feature was to allow the system to optimize primary key size for such fields because keep primary key size small is an important optimization. This feature was allowed for numeric and String types.

    As of this release the CHECK syntax and generalized ranges are no longer supported. Existing tables created with such fields will continue to operate correctly and enforce the range constraints. To replace this function, an optional storage size specification is allowed on fields declared in the primary key. This makes the intent of the feature very clear — reducing primary key size. This is only allowed on fields of type INTEGER at this time. [#24769]

  10. Added new methods to support bulk put operations in the table API. See the documentation for the TableAPI.put(List<EntryStream<Row>>, BulkWriteOptions) and KVstore.put(List<EntryStream<KeyValue>>, BulkWriteOptions)  methods for more details. [#24563]

Bug and Performance Fixes

  1. Changes have been made to the Admin and Rep Node service's persistent store to support more flexible upgrades in future releases. This change will have a one-time impact when upgrading from a previous release to this release. During the upgrade the Admin may temporarily enter a "read-only" mode. While in the read-only mode it will not be possible to change the persistent state of the Admin. This includes creating new topologies, changing parameters, creating new plans, or running existing plans. A read-only Admin will attempt to exit this mode by transferring control to another Admin node. [#24634], [#24725]

  2. System tables that are internally managed and maintained by the system are now read-only when security is enabled on the store. In addition, whether or not security is enabled, the schema for system tables are now immutable, and users are not permitted to alter, or drop or add indexes for system tables. The old tables (TableStatsPartition, TableStatsIndex, PartitionStatsLease and IndexStatsLease) used by statistics gathering are deprecated in this release. If enabled statistics gathering in an earlier release, you are still able to read these tables to check old statistics data, but they will not be updated in this release. You can drop old tables if you do not have any plan to maintain old statistics. [#24467]

  3. Fixed a problem that prevented the ping command from authenticating properly when used with a secure store. [#24808]

Utility Changes

  1. Due to changes in the Admin service's persist store (described in the "Bug and Performance Fixes" section above) the new versions of the dump and load utilities can only be used after the store has been fully upgraded. Also, previous versions of these utilities will no longer work once an upgrade to this release has begun. During an upgrade the new utilities will not operate until all of the Admin nodes have been upgraded and the Admin is no longer in the read-only mode described above. [#24634], [#24725]

  2. The "table size" sub command was mistakenly marked to be deprecated together with its parent command "table" command in release 12cR1.3.5.2, move "table size" to top level command and rename it to "table-size".

  3. Added a new status utility command that shows the status of a storage node agent. [#23561]

  4. Fixed a problem where executing a Hive query against a table containing an array with no elements would cause an exception like the following: [#24900]

    2016-02-09 13:31:24,213 ERROR [main]: CliDriver ( - Failed with exception Index: 0, Size: 0 java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
    at org.apache.hadoop.hive.ql.exec.FetchOperator.getNextRow(
    at org.apache.hadoop.hive.ql.exec.FetchOperator.pushRow(
    at org.apache.hadoop.hive.ql.exec.FetchTask.fetch(
    at org.apache.hadoop.hive.ql.Driver.getResults(
    at org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(
    at org.apache.hadoop.hive.cli.CliDriver.processCmd(
    at org.apache.hadoop.hive.cli.CliDriver.processLine(
    at org.apache.hadoop.hive.cli.CliDriver.executeDriver(
    at org.apache.hadoop.hive.cli.CliDriver.main(
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(
    at java.lang.reflect.Method.invoke(
    at org.apache.hadoop.util.RunJar.main(
    Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
    at java.util.ArrayList.rangeCheck(
    at java.util.ArrayList.get(
    at oracle.kv.impl.api.table.ArrayValueImpl.get(
    at oracle.kv.hadoop.hive.table.TableSerDe.objectInspector(
    at oracle.kv.hadoop.hive.table.TableSerDe.deserialize(
    at org.apache.hadoop.hive.ql.exec.FetchOperator.getNextRow(
    ... 15 more

Deprecated Features

  1. The interfaces and classes related to support of Avro have been deprecated in favor of the use of tables and the table API. All Avro features are available more simply using the table API. The interfaces and code supporting Avro will continue remain available for some time, but users are encouraged to migrate to the table API.

    The interfaces and classes affected are mostly in the oracle.kv.avro package. Interfaces that use those classes are also affected.