Oracle NoSQL Database 11gR18.104.22.168 Community Edition has moved to Admin version 2.
This version is available for download at this address.
This is an on-disk format change which affects internal data stored by the Admin services. The change is forward compatible in that Admin services deployed using 11gR22.214.171.124 Community Edition can read data created by older releases. The change is not backwards compatible in that Admin services which have been deployed with the new release cannot be restarted using older NoSQL releases.
See the section on Updating an Existing Oracle NoSQL Database Deployment in the Admin Guide.
- This release provides the ability to add storage nodes to the system after it has been deployed. The system will rebalance and redistribute the data onto the new nodes without stopping operations. See Chapter 6, of the Admin Guide, Determining your Store’s Configuration, for more details.
- A new
oracle.kv.lobpackage provides operations that can be used to read and write Large Objects (LOBs) such as audio and video files. As a general rule, any object larger than 1 MB is a good candidate for representation as a LOB. The LOB API permits access to large values without having to materialize the value in its entirety by providing streaming APIs for reading and writing these objects.
- A C API has been added. The implementation uses Java JNI and requires a Java virtual machine to run on the client. It is available as a separate download.
- Added a new remove-storagenode plan. This command will remove a storage node which is not hosting any NoSQL Database components from the system’s topology. Two examples of when this might be useful are:
A storage node was incorrectly configured, and cannot be deployed.
A storage node was once part of a NoSQL Database, but all components have been migrated from it using the migrate-storagenode command, and the storage node should be decommissioned.
- Added the ability to specify additional physical configuration information about storage nodes including:
- Capacity – the number of RepNodes the SN may host
- Number of CPUs
- Amount of memory to use
- Specific directory paths (mount points) to use for RepNodes
This information is used by the system to make more intelligent choices about resource allocation and consumption. The administration documentation discusses how these parameters are set and used. [#20951]
- Added Avro support. The value of a kv pair can now be stored in Avro binary format. An Avro schema is defined for each type of data stored. The Avro schema is used to efficiently and compactly serialize the data, to guarantee that the data conforms to the schema, and to perform automatic evolution of the data as the schema changes over time. Bindings are supplied that allow representing Avro data as a POJO (Plain Old Java Object), a JSON object, or a generic Map-like data structure. For more information, see Chapter 7 – Avro Schemas and Chapter 8 – Avro Bindings in the Getting Started Guide. The
oracle.kv.avropackage is described in the Javadoc. The use of the Avro format is strongly recommended. NoSQL DB will leverage Avro in the future to provide additional features and capabilities. [#21213]
- Added Avro support for the Hadoop
KVInputFormatclasses. A new
oracle.kv.hadoop.KVAvroInputFormatclass returns Avro
IndexedRecords to the caller. When this class is used in conjunction with Oracle Loader for Hadoop, it is possible to read data directly from NoSQL Database using OLH without using an interim Map-Reduce job to store data in HDFS. [#21157]
- Added a feature which allows Oracle Database External Tables to be used to access Oracle NoSQL Database records. There is more information in javadoc for the
oracle.kv.exttabpackage and an “cookbook” example in the
examples/externaltablesdirectory. [#20981] Javadoc