[ASTERIXDB-2829] Add Support for Composite Atomic-Array Indexes

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: IDX - Indexes
• Assignee: Glenn Justo Galvizo
• Reporter: Glenn Justo Galvizo
• Created: 11/Feb/21 03:11
• Updated: 30/Aug/21 17:32
• Resolved: 30/Aug/21 17:32

Description

Currently array indexes only support indexing on the elements of an array. It would be beneficial to add atomic fields as prefix(es) / suffix(es) to an array index, to allow for more queries to use an array index as an access method.

 

As it stands composite array indexes are allowed in the grammar and should be maintainable (i.e. bulk loading, insert, delete, and upserts should work), but care must be given when recognizing that the index is applicable. In the IntroduceSelectAccessMethodRule, we currently only attempt to optimize a single SELECT (and thus, only keep context for that specific SELECT)- but applicable composite atomic-array index queries have SELECTs that span multiple levels (one before the unnest and one after).