[
https://issues.apache.org/jira/browse/ASTERIXDB-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090979#comment-16090979
]
ASF subversion and git services commented on ASTERIXDB-1946:
------------------------------------------------------------
Commit e856e1e8f583829a08ccb631cf4ba780c7e7770c in asterixdb's branch
refs/heads/master from [~luochen01]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=e856e1e ]
[ASTERIXDB-1946][STO][IDX]Create RTree/InvertedIdx for Correlated Datasets
- user model changes: allow creating secondary rtree and inverted index
for datasets using correlated merge policy
- storage format changes: no
- interface changes: no
details:
- Implmeneted create secondary RTree and Inverted Index for datasets
using correlated merge policy.
- Add tests for RTree and Inverted Index creation job
Change-Id: I100fc0b86b8a6fa36a95d77806107bad0307544e
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1845
Sonar-Qube: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
BAD: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Reviewed-by: Yingyi Bu <buyin...@gmail.com>
> Support Create Secondary Index for Correlated Datasets
> ------------------------------------------------------
>
> Key: ASTERIXDB-1946
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1946
> Project: Apache AsterixDB
> Issue Type: Improvement
> Components: IDX - Indexes, STO - Storage
> Reporter: Chen Luo
> Assignee: Chen Luo
>
> Currently, when we create a secondary index, the result index would contain
> only one disk component. This is undesirable for datasets using correlated
> merge policy. Instead, it would be desirable for the new index to create one
> disk component for each component of the primary index.
> This issue would implement this behavior for secondary BTree, RTree and
> InvertedIndex.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
