[
https://issues.apache.org/jira/browse/PHOENIX-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16746697#comment-16746697
]
Thomas D'Silva commented on PHOENIX-4936:
-----------------------------------------
Not necessarily, I think it could happen for any query that scan a large number
of rows. We see it often for SYSTEM.CATALOG since its not allowed to split.
> Empty resultset returned when hbase.rpc.timeout hit
> ---------------------------------------------------
>
> Key: PHOENIX-4936
> URL: https://issues.apache.org/jira/browse/PHOENIX-4936
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.14.0
> Reporter: Vincent Poon
> Assignee: Xinyi Yan
> Priority: Blocker
> Labels: SFDC
> Fix For: 4.15.0, 5.1.0
>
>
> Seeing this on a large syscat table (~11gb)
> From sqlline, issue a SELECT statement which does a full table scan
> hbase.rpc.timeout gets hit, and instead of getting an exception, an empty
> resultset is silently returned.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
