asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glenn Justo Galvizo (Jira)" <j...@apache.org>
Subject [jira] [Assigned] (ASTERIXDB-2829) Add Support for Composite Atomic-Array Indexes
Date Fri, 25 Jun 2021 22:19:00 GMT

     [ https://issues.apache.org/jira/browse/ASTERIXDB-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Glenn Justo Galvizo reassigned ASTERIXDB-2829:
----------------------------------------------

    Assignee: Glenn Justo Galvizo

> Add Support for Composite Atomic-Array Indexes
> ----------------------------------------------
>
>                 Key: ASTERIXDB-2829
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2829
>             Project: Apache AsterixDB
>          Issue Type: Improvement
>          Components: IDX - Indexes
>            Reporter: Glenn Justo Galvizo
>            Assignee: Glenn Justo Galvizo
>            Priority: Major
>
> 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).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message