Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-28769

Documents with numbers greater than long integer are not ingested by analytics.

    XMLWordPrintable

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 5.5.0
    • Morpheus
    • analytics
    • Enterprise Edition 5.5.0 build 2211
    • Untriaged
    • No
    • CX Sprint 96, CX Sprint 97, CX Sprint 98, CX Sprint 100, CX Sprint 101, CX Sprint 102, CX Sprint 103, CX Sprint 104, CX Sprint 105, CX Sprint 106, CX Sprint 107, CX Sprint 108, CX Sprint 109, CX Sprint 110, CX Sprint 111, CX Sprint 112

    Description

      Document:

      { "long-long-int": 11111111111111111111 }

      Field has a 20 digit integer.
      In N1QL it is queried properly.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            I just inserted 1 document manually in bucket default. Document is present in the description.
            In N1QL:
            Case1: select * from default
            It gives the correct result:
            [{
            "default":

            { "long-int": 11111111111111111111 }

            }]
            Case2: select `long-long-int` from default
            It gives the wrong result:
            [

            { "long-int": 11111111111111110000 }

            ]

            ritesh.agarwal Ritesh Agarwal added a comment - I just inserted 1 document manually in bucket default. Document is present in the description. In N1QL: Case1: select * from default It gives the correct result: [{ "default": { "long-int": 11111111111111111111 } }] Case2: select `long-long-int` from default It gives the wrong result: [ { "long-int": 11111111111111110000 } ]

            We need an alignment between the 

            • select * case in N1QL
            • select field case in N1QL and the
            • behavior during ingestion for Analytics.

            Also need to understand how this interacts with indexing in both services.
             

            till Till Westmann added a comment - We need an alignment between the  select * case in N1QL select field case in N1QL and the behavior during ingestion for Analytics. Also need to understand how this interacts with indexing in both services.  

            This issue requires further discussion and alignment between the N1QL & Analytics teams for an approach that will work across the data platform.

            All existing Couchbase customers have either not dealt with the issue or have workarounds in place. We will document it as a know issue for Alice and address it in the MadHatter time frame as discussed with Till Westmann

            sachin.smotra Sachin Smotra (Inactive) added a comment - This issue requires further discussion and alignment between the N1QL & Analytics teams for an approach that will work across the data platform. All existing Couchbase customers have either not dealt with the issue or have workarounds in place. We will document it as a know issue for Alice and address it in the MadHatter time frame as discussed with Till Westmann

            Re-triage issues for the next release.

            till Till Westmann added a comment - Re-triage issues for the next release.

            Moved to Chesire-Cat after discussion with Till Westmann

            sachin.smotra Sachin Smotra (Inactive) added a comment - Moved to Chesire-Cat after discussion with Till Westmann

            People

              till Till Westmann
              ritesh.agarwal Ritesh Agarwal
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty