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

Array key size should be based total length of expanded composite items to compare against max_array_seckey_size

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • 4.5.0
    • 4.5.0
    • secondary-index
    • None
    • Untriaged
    • Unknown

    Description

      Currently the unexpanded key size is being compared with max_array_seckey_size. But the total key size after exploding the array (along with composition) should be used for size limiting.

      Example: if array is created on (ALL scores, name), and the incoming key is [ [1, 2, 3], ABC], then total size of [1, ABC], [2, ABC], [3, ABC] should be used for comparison against max_array_seckey_size.

      Attachments

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

        Activity

          People

            prathibha Prathibha Bisarahalli (Inactive)
            prathibha Prathibha Bisarahalli (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty