Skip to content

Releases: mongodb/mongo-java-driver

2.8.0

13 Sep 14:39
Compare
Choose a tag to compare

Java Driver 2.8.0 (June 18, 2012)

Highlights:

  • JAVA-458: With slaveOk, query distribution to slaves is not even
  • JAVA-429: Allow DBCollections to be modified using raw/binary BSON.
  • JAVA-509: ClassMap synchronization is a major source of contention
  • JAVA-249: Java Driver cannot connect to "localhost" when mongod is listening only on 127.0.0.1 (or "localhost")
  • JAVA-488: Support serialization to Mongo extended JSON format
  • JAVA-561: Add getX with default methods for missing values
  • JAVA-332: GridFS: Allow seek/reads (get part of a chunk) on stream interface
  • JAVA-272: OSGi Manifest is incorrect

Tickets

Full ticket information can be seen at https://jira.mongodb.org/secure/ReleaseNote.jspa?projectId=10006&version=10980

2.7.3

13 Sep 14:39
Compare
Choose a tag to compare

Java Driver 2.7.3 (January 30, 2012)

  • JAVA-505: Performance regression due to increased memory allocation

Tickets

Full ticket information can be seen at https://jira.mongodb.org/browse/JAVA/fixforversion/11002

2.7.2

13 Sep 14:40
Compare
Choose a tag to compare

Java Driver 2.7.2 (November 10, 2011)

  • JAVA-467: Calling setReadPreference(ReadPreference.SECONDARY) is not reading from secondary servers

Tickets

Full ticket information can be seen at https://jira.mongodb.org/browse/JAVA/fixforversion/10997

2.7.0

13 Sep 14:41
Compare
Choose a tag to compare

Java Driver 2.7.0 (November 4, 2011)

  • JAVA-439: Embedded Map allows dot in key names
  • JAVA-427: Support ContinueOnError Flag for bulk insert
  • JAVA-393: add support for "j" option to WriteConcern
  • JAVA-333: Allow bson decoder per operation (find/cusor)
  • JAVA-404: Allow inline M/R w/SlaveOk go to secondaries
  • JAVA-461: the logic to spread requests around slaves may select a slave over latency limit
  • JAVA-448: Tailable Cursor and awaitdata
  • JAVA-428: Support new ReadPreference semantics, deprecate SlaveOK
  • JAVA-459: smooth the latency measurements
  • JAVA-425: Support MongoDB Server 2.0 getLastError Changes (j, w=string/number)
  • JAVA-462: GridFSInputFile does not close input streams when constructed by the driver
  • JAVA-363: NPE in GridFSFile.validate
  • JAVA-364: MapReduceOutput sometimes returns empty results in a replica set when SLAVE_OK=true
  • JAVA-323: when executing a command, only top level object returned should be a CommandResult, not sub-objects
  • JAVA-444: make ensureIndex first do a read on index collection to see if index exists
  • JAVA-356: JSONParseException class not public

Tickets

Full ticket information can be seen at https://jira.mongodb.org/browse/JAVA/fixforversion/10480

2.6.5

13 Sep 14:41
Compare
Choose a tag to compare

Java Driver 2.6.5 (August 09, 2011)

  • JAVA-411: Java Driver 2.6.4 findOne fails when fields are specified but no document is found ( NullPointerException )

Tickets

Full ticket information can be seen at http://jira.mongodb.org/browse/JAVA/fixforversion/10684

2.6.4

13 Sep 14:41
Compare
Choose a tag to compare

Java Driver 2.6.4 (August 08, 2011)

  • JAVA-319: JSON parser to not require quotes around keys
  • JAVA-382: NPE in ReplicaSetStatus.ensureMaster
  • JAVA-387: DBCollection#findOne(DBObject o, DBObject fields) doesn't markAsPartialObject
  • JAVA-390: Make it possible to override the bson decoder, not just the callback
  • JAVA-396: improve javadocs for connection options, they confuse people
  • JAVA-397: authentication for replica set fails frequently because 'getnonce' and 'authenticate' command is issued to different server
  • JAVA-398: Configure max connection retry time
  • JAVA-406: Java driver does not accept empty keys
  • JAVA-407: some source files do not include licence information
  • JAVA-409: when creating Mongo to single server, its address appears twice (ipv4/ipv6) and it gets exploded into a replica set
  • JAVA-410: if using DBAddress instead of ServerAddress, server matching in replica set doesnt work
  • JAVA-395: Date Time values do not preserve milliseconds when serialized to or deserialized from JSON

Tickets

Full ticket information can be seen at https://jira.mongodb.org/browse/JAVA/fixforversion/10490

2.6.3

13 Sep 14:42
Compare
Choose a tag to compare

Java Driver 2.6.3 (June 08, 2011)

This release addresses bug fixes only.

  • Connector does not get started in one of the constructor, so replica set thread is not activated

Tickets

Full ticket information can be seen at http://jira.mongodb.org/browse/JAVA/fixforversion/10486

2.6.2

13 Sep 14:42
Compare
Choose a tag to compare

Java Driver 2.6.2 (June 02, 2011)

This release addresses bug fixes only.

  • Fixed GridFS file issues stemming from the default default byte[] encoding
  • Unclosed background connections connecting to replicasets (only an issue if not using Mongo as a singleton)
  • Race-condition on Mongo constructor with replicasets

Tickets

Full ticket information can be seen at http://jira.mongodb.org/browse/JAVA/fixforversion/10484

2.6.1

13 Sep 14:43
Compare
Choose a tag to compare

Java Driver 2.6.1 (May 29, 2011)

This release addresses bug fixes only.

  • Fixed incorrect implementation of the Binary/byte[] encoding (from the 2.6 release).

2.6

13 Sep 14:43
Compare
Choose a tag to compare
2.6

Java Driver 2.6 (May 27, 2011) (removed)

This release addresses bug fixes and includes some minor improvements.

Tickets

Full ticket information can be seen at http://jira.mongodb.org/browse/JAVA/fixforversion/10249

Breaking Changes

  • Changed default binary type (for java byte[]) from subtype 2->0. The will save 4 bytes but uses a different storage format on the server so it is not compatible for existing data; you will be able to save and read data without problem but searching against the data will result in inconsistent results. As you read and save data (using a byte[]) this will update the old subtype to the new one.

These are all bug-fixes but may affect your code if you depend on the buggy behavior.

  • JSON parser treated int/long values as longs -- reverted back to old behavior of converting to best fit
  • query/DBCursor.hint(DBObject) created an index name; very unlikely to be breaking in any way.