[ASTERIXDB-3492] Not evaluating next tuple in case of skip while column filtering

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.9.10
• Fix Version/s: 0.9.10
• Component/s: STO - Storage
• Labels: triaged
• Epic Link: Columnar Format
• Assignee: Ritik Raj
• Reporter: Ritik Raj
• Created: 27/Aug/24 08:41
• Updated: 31/Aug/24 02:12
• Resolved: 30/Aug/24 17:44

Description

We are not evaluating the next tuple in case of skipping a tuple while column filtering, leading to inaccurate results.

Test Case:

 DROP DATAVERSE test IF EXISTS;
 CREATE DATAVERSE test;

 USE test;

 CREATE DATASET ColumnDataset
 PRIMARY KEY (uid:int) WITH {
     "storage-format": {"format": "column"}
 };

 USE test;
UPSERT INTO ColumnDataset(
    {"uid": 1, "a": [{"x": "aaaaaaaaaazzzz"}, {"x": "aaaaaaaaaaabzzzz"}, {"x": "aaaaaaaaaaaaabzzzzzzzz"}]},
    {"uid": 2, "a": [{"x": "aaaaaaaaaazzzz"}, {"x": "aaaaaaaaaaabzzzz"}, {"x": "aaaaaaaaaaaaabzzzzzzzz"}]}
);

USE test; 
DELETE FROM ColumnDataset WHERE uid = 1;

 

 USE test;
 SELECT VALUE a.x
 FROM ColumnDataset c, c.a a
 WHERE a.x = "aaaaaaaaaaaaabzzzzzzzz"; 

 

gives no result, but should give one output.