[JAVA-737] DBEncoderFactory setting on MongoOptions is ignored Created: 18/Jan/13  Updated: 31/Mar/15  Resolved: 22/Aug/13

Status: Closed
Project: Java Driver
Component/s: Configuration
Affects Version/s: 2.9.1
Fix Version/s: 3.0.0

Type: Bug Priority: Major - P3
Reporter: Gijs Kruitbosch Assignee: Uladzimir Mihura
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

MongoOptions has an option to set a global DBEncoderFactory, but as far as I can tell, it is never used and you thus always have to set it on individual DBCollection objects. This is quite inconvenient if you always want to use non-default ones. Could this be fixed or at least documented?



 Comments   
Comment by Jeffrey Yemin [ 31/Mar/15 ]

Closing all resolved 3.0.0 issues, as 3.0.0 has been tagged and released.

Comment by Uladzimir Mihura [ 16/Aug/13 ]

In 2.x situation a bit more complex: we have MongoOptions and MongoClientOptions and in DB we need to have to determine are we connected with Mongo or MongoClient and invoke appropriate getter.

-vova

Comment by auto [ 16/Aug/13 ]

Author:

{u'username': u'trnl', u'name': u'Uladzimir Mihura', u'email': u'trnl.me@gmail.com'}

Message: fix(driver-compat) JAVA-737: DBEncoderFactory setting on MongoOptions is ignored
Branch: 3.0.x
https://github.com/mongodb/mongo-java-driver/commit/7f22d26220da40594f0439af3423e853dde98ad2

Generated at Thu Feb 08 08:52:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.