Document that CodecRegistry instances configured by the application are treated as CodecProvider

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Unknown
    • 4.8.0
    • Affects Version/s: None
    • Component/s: Codecs
    • None
    • None
    • Fully Compatible
    • Not Needed
    • None
    • None
    • None
    • None
    • None
    • None

      All instances of CodecRegistry configured by the application, via MongoClientSettings or withCodecRegistry method on MongoDatabase or MongoCollection are actually wrapped by the driver in another CodecRegistry, so effectively the application-provided instances are used only as a CodecProvider. This should be documented clearly, as it's confusing to both users and to driver developers.

            Assignee:
            Jeffrey Yemin
            Reporter:
            Jeffrey Yemin
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: