Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

[BP to 7.1.5/7.2.1 MB-56562] - Covering FLATTEN_KEYS() may generate wrong results

Description

Found by  

Due to false positives and Distinct scan rows eliminated

We should apply filter on indexScan or disable covering

Issue

Resolution

Covering FLATTEN_KEYS() on an array index generated incorrect results. This was because a modified version of the ANY clause was applied after the index which meant false positives were retained and Distinct scan rows were eliminated.

The ANY filter is now applied on an index scan itself when covering an index scan with flatten keys.

Components

Affects versions

Fix versions

Labels

Environment

None

Link to Log File, atop/blg, CBCollectInfo, Core dump

None

Release Notes Description

None

Activity

Show:

Ajay Pal Bhullar June 14, 2023 at 7:06 PM

verified in 7.2.1-5791

[
{
"id": "k01"
}
]

Ajay Pal Bhullar June 14, 2023 at 6:54 PM

verified in 7.1.5-3846 the above is now returning results

[
{
"id": "k01"
}
]

will close bug when i have verified in 7.2.1

CB robot June 9, 2023 at 2:07 AM

Build couchbase-server-7.1.5-3837 contains query commit 9ee4376 with commit message:
Update unit test infrastructure

CB robot May 23, 2023 at 12:37 PM

Build couchbase-server-7.1.5-3814 contains query commit 9aed152 with commit message:
Apply ANY filter on index scan for covering index scan with flatten keys

CB robot May 23, 2023 at 12:13 AM

Build couchbase-server-7.2.1-5738 contains query commit 47d880f with commit message:
Apply ANY filter on index scan for covering index scan with flatten keys

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Is this a Regression?

Unknown

Triage

Untriaged

Story Points

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created April 22, 2023 at 4:32 PM
Updated September 18, 2023 at 2:47 PM
Resolved May 23, 2023 at 8:57 PM
Instabug