asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ASTERIXDB-1886) Filter is not selective
Date Thu, 20 Apr 2017 22:18:04 GMT


ASF subversion and git services commented on ASTERIXDB-1886:

Commit b1a07a07e681aed03157621801ced1ce687ec6f2 in asterixdb's branch refs/heads/master from
[;h=b1a07a0 ]

Fix for ASTERIXDB-1886: Filter not selective

The filter was not being reset in the memory component.

Change-Id: I123438c7fe5fba64aff4e88b1bda0e2be1a32574
Sonar-Qube: Jenkins <>
Tested-by: Jenkins <>
BAD: Jenkins <>
Integration-Tests: Jenkins <>
Reviewed-by: abdullah alamoudi <>

> Filter is not selective
> -----------------------
>                 Key: ASTERIXDB-1886
>                 URL:
>             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

View raw message