diff options
author | Michael Cahill <michael.cahill@mongodb.com> | 2016-03-24 13:52:04 +1100 |
---|---|---|
committer | Michael Cahill <michael.cahill@mongodb.com> | 2016-03-24 13:52:04 +1100 |
commit | d9a28c1c5b3bd3128f2c7b4265425c52c87165c0 (patch) | |
tree | a9496803ef626de77b20b5d948f3ad671109f4e5 /src/docs | |
parent | fc99d7e5307ef6a57b3a53edde16d9b9490fe982 (diff) | |
download | mongo-d9a28c1c5b3bd3128f2c7b4265425c52c87165c0.tar.gz |
Change version to 2.8.0 in upgrading notes.
Diffstat (limited to 'src/docs')
-rw-r--r-- | src/docs/upgrading.dox | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/docs/upgrading.dox b/src/docs/upgrading.dox index 5c5be214915..5e824fee977 100644 --- a/src/docs/upgrading.dox +++ b/src/docs/upgrading.dox @@ -1,6 +1,6 @@ /*! @page upgrading Upgrading WiredTiger applications -@section version_271 Upgrading to Version 2.7.1 +@section version_280 Upgrading to Version 2.8.0 <dl> <dt>LSM metadata</dt> <dd> @@ -14,7 +14,7 @@ format will be upgraded automatically, but once updated to the new version <dd> Historically, bulk-load of a column-store object ignored any key set in the cursor and automatically assigned each inserted row the next sequential -record number for its key. In the 2.7.1 release, column-store objects match +record number for its key. In the 2.8.0 release, column-store objects match row-store behavior and require the cursor key be set before an insert. (This allows sparse tables to be created in column-store objects, any skipped records are created as already-deleted rows.) To match the previous |