Release 11gR188.8.131.52 Community Edition
See the section on Updating an Existing Oracle NoSQL Database Deployment in the Admin Guide.
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 storage node was incorrectly configured, and cannot be deployed.[#20530]
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.
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]
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]
oracle.kv.exttabpackage and an "cookbook" example in the
examples/externaltablesdirectory. [#20981] Javadoc
R1 installations must ensure that the software on the storage nodes has been upgraded as described in the upgrade documentation accompanying this release before using the above APIs on the client. [#20997]
rnMonitorSOBacklog(default 0), rnAdminSOBacklog (default 0),
snMonitorSOBacklog(default 0), and
snRegistrySOBacklog(default 1024). [#21322]
Key.isPrefixwith an argument containing a smaller major or minor path than the target Key object caused an IndexOutOfBoundsException in certain cases. This has been fixed.
KeyRange()constructor now checks that the start
Keyis less than the end
Keyif both are specified, otherwise an
fromString()methods for encoding and decoding
KeyRangeinstances, similar to the same methods in
Datacenters can now be expressed as # or dc#joinPool myStorageNodePool 17 show repnode-params 5,3
The commands shown above are still valid, but can also be expressed as:
[#21099]joinPool myStorageNodePool sn17 show repnode-params rg5-rn3
Key.createKeymethods has been improved to warn that List instances passed as parameters are owned by the Key object after calling the method. To avoid unpredictable results, they must not be modified. [#20530]
snapshot createcommand has been made significantly faster. Previously, it could take minutes if executed on a store with a large amount of data. This should be reduced to seconds. [#20772]
bin/kvctl, have been replaced by a
java -jar lib/kvstore-M.N.P.jarcommand. This provides portability to all Java platforms, including Windows. The two scripts are deprecated, but will be supported for at least one release cycle.
The translation from the old script commands to the new -jar commands is as follows:
|Old script command||New -jar command|
There are a few differences to be aware of between the old and new commands.
nohup, if desired, must be explicitly specified. In
bin/kvctl script, nohup was added automatically for the
restart commands. To specify the
equivalent command, use:
nohup java -jar lib/kvstore-M.N.P.jar start args... > /dev/null <
/dev/null 2<&1 &
The logging configuration file for kvlite is now specified using
standard Java syntax. Previously, the
examples/logging.properties configuration file was added
automatically when passing
-logging to the
run-kvlite.sh script. The new equivalent is:
-jar lib/kvstore-M.N.P.jar kvlite args...
-host argument defaulted to
the local machine name (via the
`hostname` command) when
kvctl script. Now, for all control commands, no
default hostname is used and the
-host argument must be
specified explicitly. This change was made for two reasons: 1)
consistency, since the port and other arguments have no default value for
control commands, and 2) safety, since specifying an explicit hostname
guards against accidental errors.
-host argument defaulted to
localhost when running the
Now, the default is the local machine name rather than (literally)
localhost. Note that the kvlite command, unlike the control
commands, has default values for all arguments. This is because the kvlite
command is designed for ease-of-use during development on a single machine.
kvlite should not be used in production or for performance testing.
java -jar lib/kvstore-M.N.P.jar, with or
without arguments, printed the product version. Now, if no arguments are
specified, a usage message is printed. To print the version, use the
java -jar lib/kvstore-M.N.P.jar version