[SERVER-71180] Review whether columnstore_index_per_path_filters.js needs explicit CSI creation and/or checks Created: 08/Nov/22  Updated: 12/Jan/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Irina Yatsenko (Inactive) Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: pm2646-m5
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Execution
Participants:

 Description   

Most tests in columnstore_index_per_path_filters.js don't assert that CSI is actually used but they do explicitly create the columnstore index. This approach makes it somewhat unclear what the tests expect to cover.

Proposal:

  1. remove explicit columnstore index creation
  2. remove uses_column_store_index tag to allow this test in columnstore job
  3. remove feature guard tags
  4. split out any of the tests that explicitly depend on using CSI

As a result, the tests will run both with and without CSI ensuring that the semantics they expect match across engines and access paths.

Or we could move the tests in the other direction, that is, make them explicitly CSI-only and add checks about the correct plan selection, etc.


Generated at Thu Feb 08 06:18:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.