Atlas Data Federation returns failed to parse BSON errors on valid gzipped bson

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Incomplete
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We are using Atlas Data Federation on Azure blob storage to query data. However, some queries are inconsistently returning errors that look like: 

       

      (FailedToParse) parse error on BSON document 2112 from "https://sttabulardataprod1.blob.core.windows.net/viam-data-614f6caa-56cc-4565-8b97-037032430eeb/614f6caa-56cc-4565-8b97-037032430eeb/2ia26a46on/00fa49c9-a111-47f8-875c-2a61ad21276b/bbb7c844-ea4c-46c8-9bd6-779c7910e8f6/rdk:component:sensor/<REDACTED>/Readings/2025-07-02/data-1.bson.gz?delimiter=%2F&region=eastus2", correlationID = 185287510f93e52884abafc2" 

      This error is inconsistent as the document number and full blob path change from query run to query run. The query also succeeds sometimes. 
      We've verified these are valid BSON documents by downloading them and running bsondump on them. We see the expected number of files and no errors about invalid bson. Here are a few other correlation IDs that exhibit this behaviour:

      185284bbeb5c2b60f6147551

      185284bbec99089d7a83d98

      185284bbeb5c2b60f6147551

      1852843c69ca6ca17ff5d245

       

            Assignee:
            Chris Kelly
            Reporter:
            Vijay Vuyyuru
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: