[
https://issues.apache.org/jira/browse/PHOENIX-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346225#comment-14346225
]
Lars Hofhansl commented on PHOENIX-1694:
----------------------------------------
Hmm... Not offhand. Would need to check the code. The count() is running with
the lease still in place (as discussed in some other issue) so the lease
expires while the query is running.
Generally, I would not even have an update statistics command. That did make
sense maybe for RDBMSs, but for BigData it does not. IMHO... stats are updated
by compactions and otherwise out of date.
> 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 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)
