[COMPASS-6357] Investigate changes in PM-2646: Columnstore indexes for analytic queries Created: 07/Dec/22  Updated: 24/Jan/23  Resolved: 24/Jan/23

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: No version

Type: Investigation Priority: Major - P3
Reporter: Jessica Sigafoos Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Epic Link: COMPASS-5986
Documentation Changes: Not Needed

 Description   

Downstream Attention Summary
new Column Store Index option for creating indexes in Compass

PM Ticket Summary
Add a new type of an index, columnar index, that substantially improves performance of analytic queries.

Motivation
Document-based collections with B-Tree indexes ensure fast writes and point or selective range reads. They are efficient transactional and search scenarios that process entire documents. On the other hand, analytic queries usually reference a handful of fields and perform well against column-oriented formats. In this case, fields are highly-compressed and can be loaded selectively providing dramatic savings in I/O. Other techniques, such as skip-scans or operations on compressed data can push performance even further.

Allowing users to supplement their collections with columnar indexes is a seamless way of adding support for analytic workloads to their systems trading off storage and write throughput. In addition, it can improve performance not only for a known upfront fixed workload but also for ad hoc queries.


Generated at Wed Feb 07 22:42:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.