Mailing-List: contact issues-help@carbondata.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@carbondata.incubator.apache.org
From: sounakr <git@git.apache.org>
To: issues@carbondata.incubator.apache.org
Reply-To: issues@carbondata.incubator.apache.org
Message-ID: <git-pr-670-incubator-carbondata@git.apache.org>
Subject: [GitHub] incubator-carbondata pull request #670: [CARBONDATA-792] Range Filter Optimi...
Content-Type: text/plain
Date: Sat, 18 Mar 2017 15:20:09 +0000 (UTC)
archived-at: Sat, 18 Mar 2017 15:20:13 -0000

GitHub user sounakr opened a pull request:

    https://github.com/apache/incubator-carbondata/pull/670

    [CARBONDATA-792] Range Filter Optimization

    Problem : LessThan and GreaterThan Expression are merged into a single RANGE expression.
    
    Analysis : If LessThan and GreaterThan Expression on a same column given as filter predicates, then each expression is evaluated independently and finally AND operator is applied on individual results to get the final output. 
    
    Fix : If the LessThan and GreaterThan Expression values can form a Range then it is Converted into a RANGE expression and results are evaluated through single expression. I.e. if the value lies within Range then choosen. This fix will optimize Block Prunning and Reduce Scanning time in case queries have range expressions in filter.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sounakr/incubator-carbondata range1

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-carbondata/pull/670.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #670
    
----
commit e77cc5a84e9d6313383cb6347f78846f3319442e
Author: sounakr <sounakr@gmail.com>
Date:   2017-03-15T16:06:16Z

    [CARBONDATA-792] Range Filter Optimization

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---