[
https://issues.apache.org/jira/browse/ASTERIXDB-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16199708#comment-16199708
]
ASF subversion and git services commented on ASTERIXDB-2103:
------------------------------------------------------------
Commit 1dc8228b7262e47c06487443da0f735321e63afe in asterixdb's branch
refs/heads/master from [~luochen01]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=1dc8228 ]
Revert "[ASTERIXDB-2103][STO] Too many disk components for CorrelatedPolicy"
This reverts commit 21ed0f72681a20ccb6a654f9aa4d54b8d0ea9c5c.
Change-Id: I670545acd09c678f21be25313353ab306be86202
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2063
Tested-by: Jenkins <[email protected]>
Contrib: Jenkins <[email protected]>
Reviewed-by: Ian Maxon <[email protected]>
Integration-Tests: Jenkins <[email protected]>
> Too many disk components for InvertedIndex with CorrelatedMergePolicy
> ---------------------------------------------------------------------
>
> Key: ASTERIXDB-2103
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2103
> Project: Apache AsterixDB
> Issue Type: Bug
> Reporter: Chen Luo
> Assignee: Chen Luo
>
> As reported by [~javierjia], when using CorrelatedPrefixMergePolicy, the
> secondary InvertedIndex could have too many disk components (the primary
> index has ~ 200 disk components, while the InvertedIndex has ~500 disk
> components).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
