Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@phoenix.apache.org
Date: Wed, 4 Mar 2015 01:10:04 +0000 (UTC)
From: "James Taylor (JIRA)" <jira@apache.org>
To: dev@phoenix.incubator.apache.org
Message-ID: <JIRA.12779206.1425421211000.70686.1425431404873@Atlassian.JIRA>
In-Reply-To: <JIRA.12779206.1425421211000@Atlassian.JIRA>
References: <JIRA.12779206.1425421211000@Atlassian.JIRA>
 <JIRA.12779206.1425421211160@arcas>
Subject: [jira] [Commented] (PHOENIX-1694) Update statistics fail to
 complete when client disconnects
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

James Taylor commented on PHOENIX-1694:
---------------------------------------

[~lhofhansl] - is this what you'd expect? That a COUNT(1) query would stop (on the server) when the client disconnects?

> Update statistics fail to complete when client disconnects
> ----------------------------------------------------------
>
>                 Key: PHOENIX-1694
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1694
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 5.0.0, 4.3
>         Environment: HBase 0.98.10, Phoenix 4.3 branch
>            Reporter: Mujtaba Chohan
>            Assignee: James Taylor
>            Priority: Minor
>
> [~jamestaylor] You mentioned that after initiating _update statistics_ command even if client disconnects, statistics would still get generated by server side process. 
> Just checked it this. As soon as client disconnects stats table population halts if client disconnects any time after update statistics command is issued.


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