[
https://issues.apache.org/jira/browse/ASTERIXDB-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16242734#comment-16242734
]
ASF subversion and git services commented on ASTERIXDB-2015:
------------------------------------------------------------
Commit 2031eda50414111105aedb3a82f0af1eec3bb543 in asterixdb's branch
refs/heads/master from [~alsuliman]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=2031eda ]
[ASTERIXDB-2015][IDX] Introduce Primary Index Optimization Rule
- user model changes: no
- storage format changes: no
- interface changes: no
details:
This is the optimization rule that will optimize aggregation queries
when only PKs are involved. The rule will use the primary index and
replace the dataset scan or unnest-map operator.
Change-Id: I3bbb2b5e1f25e61928d73b866e91c592ce0bf954
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2111
Sonar-Qube: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Contrib: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Reviewed-by: Dmitry Lychagin <dmitry.lycha...@couchbase.com>
> Create secondary primary index
> ------------------------------
>
> Key: ASTERIXDB-2015
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2015
> Project: Apache AsterixDB
> Issue Type: Improvement
> Components: IDX - Indexes
> Reporter: Ali Alsuliman
>
> This change is regarding introducing secondary primary index. The secondary
> primary index is a secondary B-Tree that is built on the primary keys of the
> dataset but only stores the {PK} instead of the regular case {SK,PK}. The
> purpose of this secondary is to optimize queries like SELECT count(*).
> Instead of scanning the primary index, the secondary primary index would be
> used to answer such queries.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
