[
https://issues.apache.org/jira/browse/ASTERIXDB-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977696#comment-15977696
]
ASF subversion and git services commented on ASTERIXDB-1886:
------------------------------------------------------------
Commit b1a07a07e681aed03157621801ced1ce687ec6f2 in asterixdb's branch
refs/heads/master from [~imaxon]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=b1a07a0 ]
Fix for ASTERIXDB-1886: Filter not selective
The filter was not being reset in the memory component.
Change-Id: I123438c7fe5fba64aff4e88b1bda0e2be1a32574
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1691
Sonar-Qube: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
BAD: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Reviewed-by: abdullah alamoudi <bamou...@gmail.com>
> Filter is not selective
> -----------------------
>
> Key: ASTERIXDB-1886
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1886
> Project: Apache AsterixDB
> Issue Type: Bug
> Reporter: Jianfeng Jia
> Assignee: Ian Maxon
>
> In a large enough dataset that has gone through enough merges, the filter
> will not be selective. The min and max are global for the lifetime of the
> memory component rather than being reset per flush.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
