Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

MongoDB 2.6 compatibility and test failures #741

Closed
jmikola opened this Issue · 5 comments

1 participant

@jmikola
Owner

Current test failures with the 2.5.x nightly build:

  • MongoCursorException: localhost:27017: Can't canonicalize query: BadValue $in needs an array
  • MongoCursorException: localhost:27017: '$set' is empty. You must specify a field like so: {$mod: {: ...}}" (SERVER-12266)
  • $elemMatch does not support DBRef objects (SERVER-12263)

These are coming out of various tests in the suite, so it's likely some common problem in DocumentPersister.

@jmikola
Owner

Cross-referencing the "$set is empty" error to SERVER-12266.

There is also a problem with DBRef objects and $elemMatch queries in SERVER-12263.

@jmikola jmikola was assigned
@jmikola
Owner

The "$set is empty" error (SERVER-12266) will require attempting either the pre-2.6 or 2.6+ method first, and then falling back on error. The server will not be removing the strictness check, nor can we rely on the pre-2.6 bug being backported (even if it was, it wouldn't help for versions prior to the 2.4.x bugfix). We can possibly check the server version up front.

The DBRef $elemMatch issue (SERVER-12263) should be fixed in a 2.6 release candidate.

@jmikola
Owner

SERVER-12263 was updated to support additional fields in $elemMatch DBRefs, but we're still missing support for querying with partial DBRef fields (e.g. just $id).

@jmikola
Owner

With #750 merged, we're just waiting on a server fix (hopefully in 2.6.0-rc0).

@jmikola
Owner

SERVER-12263 is resolved, so we'll have the fix in 2.6.0-rc0.

@jmikola jmikola closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.