Use Lossy UTF8 Decoding when decoding writeErrors returned from the server

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 2.2.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None

      Given that the server can return invalid UTF-8 sequences, it seems safer to handle them gracefully in the driver by default rather than via our special Document::from_reader_utf8_lossy. This is currently the behavior in the Node and Python drivers.

      Acceptance Criteria

      • When decoding server errors use lossy decoding

            Assignee:
            Kaitlin Mahar
            Reporter:
            Patrick Freed
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: