summaryrefslogtreecommitdiff
path: root/jstests/core/geo_update_btree2.js
diff options
context:
space:
mode:
authorRandolph Tan <randolph@10gen.com>2014-01-14 14:09:42 -0500
committerRandolph Tan <randolph@10gen.com>2014-02-28 16:26:33 -0500
commit5595b945603b0712c537787e31e6da661c424fee (patch)
tree90945ee3fe4931032f3af2d397bb755fbf5d30ef /jstests/core/geo_update_btree2.js
parentcd62080dcb036e83f8fca6d68d9bcab67bf7a21c (diff)
downloadmongo-5595b945603b0712c537787e31e6da661c424fee.tar.gz
SERVER-12127 migrate js tests to jscore suite when not related to writes
Moved test jstest/[a-i].js -> jstests/core/ and made changes to comply with write command api
Diffstat (limited to 'jstests/core/geo_update_btree2.js')
-rw-r--r--jstests/core/geo_update_btree2.js71
1 files changed, 71 insertions, 0 deletions
diff --git a/jstests/core/geo_update_btree2.js b/jstests/core/geo_update_btree2.js
new file mode 100644
index 00000000000..d99970c73e0
--- /dev/null
+++ b/jstests/core/geo_update_btree2.js
@@ -0,0 +1,71 @@
+// Tests whether the geospatial search is stable under btree updates
+//
+// Tests the implementation of the 2d search, not the behavior we promise. MongoDB currently
+// promises no isolation, so there is no guarantee that we get the results we expect in this file.
+
+// The old query system, if it saw a 2d query, would never consider a collscan.
+//
+// The new query system can answer the queries in this file with a collscan and ranks
+// the collscan against the indexed result.
+//
+// In order to expose the specific NON GUARANTEED isolation behavior this file tests
+// we disable table scans to ensure that the new query system only looks at the 2d
+// scan.
+assert.commandWorked( db._adminCommand( { setParameter:1, notablescan:true } ) );
+
+var status = function( msg ){
+ print( "\n\n###\n" + msg + "\n###\n\n" )
+}
+
+var coll = db.getCollection( "jstests_geo_update_btree2" )
+coll.drop()
+
+coll.ensureIndex( { loc : '2d' } )
+
+status( "Inserting points..." )
+
+var numPoints = 10
+for ( i = 0; i < numPoints; i++ ) {
+ coll.insert( { _id : i, loc : [ Random.rand() * 180, Random.rand() * 180 ], i : i % 2 } );
+}
+
+status( "Starting long query..." )
+
+var query = coll.find({ loc : { $within : { $box : [[-180, -180], [180, 180]] } } }).batchSize( 2 )
+var firstValues = [ query.next()._id, query.next()._id ]
+printjson( firstValues )
+
+status( "Removing points not returned by query..." )
+
+var allQuery = coll.find()
+var removeIds = []
+while( allQuery.hasNext() ){
+ var id = allQuery.next()._id
+ if( firstValues.indexOf( id ) < 0 ){
+ removeIds.push( id )
+ }
+}
+
+var updateIds = []
+for( var i = 0, max = removeIds.length / 2; i < max; i++ ) updateIds.push( removeIds.pop() )
+
+printjson( removeIds )
+coll.remove({ _id : { $in : removeIds } })
+
+status( "Updating points returned by query..." )
+printjson(updateIds);
+
+var big = new Array( 3000 ).toString()
+for( var i = 0; i < updateIds.length; i++ )
+ coll.update({ _id : updateIds[i] }, { $set : { data : big } })
+
+status( "Counting final points..." )
+
+// It's not defined whether or not we return documents that are modified during a query. We
+// shouldn't crash, but it's not defined how many results we get back. This test is modifying every
+// doc not returned by the query, and since we currently handle the invalidation by removing them,
+// we won't return them. But we shouldn't crash.
+// assert.eq( ( numPoints - 2 ) / 2, query.itcount() )
+query.itcount();
+
+assert.commandWorked( db._adminCommand( { setParameter:1, notablescan:false} ) );