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-264) Limit query scan time statistics issue
Date Wed, 21 Sep 2016 03:48:20 GMT

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

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

GitHub user kumarvishal09 opened a pull request:

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

    [CARBONDATA-264]Fixed limit query scan time statistics issue

    Problem: Scan time is not logging in statistics in case of limit query 
    Soluntion: Moved statistics recording from iterator to queryExecutor finish method as
in case of limit query after consuming records call is not coming to hasNext method 

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

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

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

    https://github.com/apache/incubator-carbondata/pull/184.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 #184
    
----
commit 60c92b08d642c9580533b5cf7cc27e0ecf84b244
Author: kumarvishal <kumarvishal.1802@gmail.com>
Date:   2016-09-21T03:37:09Z

    Fixed limit query statistics issue

----


> Limit query scan time statistics issue 
> ---------------------------------------
>
>                 Key: CARBONDATA-264
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-264
>             Project: CarbonData
>          Issue Type: Bug
>            Reporter: kumar vishal
>            Priority: Minor
>
> Problem: Scan time is not logging in statistics in case of limit query 
> Soluntion: Moved statistics from iterator to queryExecutor finish method as in case of
limit query after consuming records call is not coming to hasNext method 



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

Mime
View raw message