Applications that opened cursors on checkpoints and relied on their statistics being aggregated into a single statistics cursor will need to open statistics cursors on each checkpoint.
The statistic for the number of bytes written to the log minus the overhead of log record headers and padding was renamed to make the intent clearer.
Applications using the existing WT_COLLATOR interface that do not require the new functionality should set this callback to We have updated the configure logic used to search for Java Native Interface files.
This fixes problems building Wired Tiger's Java API, particularly on OS X, but may introduce problems if your build procedure relied on the old search behavior.
In the 2.1.1 release of Wired Tiger the configuration string parsing API has been changed and added to a new public handle.
The WT_EXTENSION_API::config_strget, WT_EXTENSION_API::config_scan_begin, WT_EXTENSION_API::config_scan_next and WT_EXTENSION_API::config_scan_end have been removed.
All configuration options to WT_SESSION::create that previously had a prefix of configuration group.
If you are explicitly configuring any of the following options, you should review the WT_SESSION::create documentation for details of the updated syntax: lsm_auto_throttle, lsm_bloom, lsm_bloom_config, lsm_bloom_bit_count, lsm_bloom_hash_count, lsm_bloom_oldest, lsm_chunk_max, lsm_chunk_size, lsm_merge_max and lsm_merge_threads.
This change means that a cursor can be used to iterate through a table and perform transactional updates based on the visited records without the cursor losing its position.configuration setting default value has changed from "dsync" to "fsync".This is due to enhancements to the group commit implementation in Wired Tiger - which mean that greater throughput can be achieved with explicit "fsync" calls than by enabling "dsync" on a file handle.The configuration settings related to file handle management have changed significantly in this release.If your application uses the file_manager configuration setting, please refer to the API documentation for the latest settings.