carbondata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CARBONDATA-271) Non Filter data mismatch issue
Date Fri, 23 Sep 2016 11:08:21 GMT

    [ https://issues.apache.org/jira/browse/CARBONDATA-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516134#comment-15516134
] 

ASF GitHub Bot commented on CARBONDATA-271:
-------------------------------------------

GitHub user kumarvishal09 opened a pull request:

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

    [CARBONDATA-271]Fixed non filter data mismatch issue.

    Problem: While generating the default end key we are taking LONG.MAX key and using segment
key generator we are generating the end key if cardinality is less than it will give some
value with in its cardinality and btree searching will fail
    
    Solution: From segment property get the dimension cardinality as this is the max value
for segment 

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

    $ git pull https://github.com/kumarvishal09/incubator-carbondata NonFilterDataMismatchIssue

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

    https://github.com/apache/incubator-carbondata/pull/196.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 #196
    
----
commit db865d428639be04444ab7e593f92931f85fcf71
Author: kumarvishal <kumarvishal.1802@gmail.com>
Date:   2016-09-23T10:48:52Z

    Fixed non filter data mismatch issue.

----


> Non Filter data mismatch issue
> ------------------------------
>
>                 Key: CARBONDATA-271
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-271
>             Project: CarbonData
>          Issue Type: Bug
>            Reporter: kumar vishal
>            Assignee: kumar vishal
>
> Problem: While generating the default end key we are taking LONG.MAX key and using segment
key generator we are generating the end key if cardinality is less than it will give some
value with in its cardinality and btree searching will fail
> Solution: From segment property get the dimension cardinality as this is the max value
for segment 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message