You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/06/20 16:18:00 UTC
[jira] [Commented] (ASTERIXDB-1946) Support Create Secondary Index
for Correlated Datasets
[ https://issues.apache.org/jira/browse/ASTERIXDB-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056027#comment-16056027 ]
ASF subversion and git services commented on ASTERIXDB-1946:
------------------------------------------------------------
Commit a7fa05bb014503609d1b6287fa08b0a296098088 in asterixdb's branch refs/heads/master from [~luochen01]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=a7fa05b ]
[ASTERIXDB-1946][STO][IDX] Create BTreeIndex for Correlated Datasets
Implemented create seconary BTree index for datasets using
correlated merge policy. Instead of creating one component
for the new index, this change creates one component for each
component of the primary index to maintain the correlation.
The current implementation assumes when a secondary index is being
created, the dataset is locked with no modifications.
Change-Id: I2a3435e6720f07bd6a5092d4d9ce42e8d4b7894c
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1813
Sonar-Qube: Jenkins <je...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <je...@fulliautomatix.ics.uci.edu>
Reviewed-by: Yingyi Bu <bu...@gmail.com>
BAD: Jenkins <je...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <je...@fulliautomatix.ics.uci.edu>
> 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)