[jira] [Commented] (PHOENIX-1370) Allow query timeout to differ from RPC timeout

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on PHOENIX-1370:
---------------------------------

SUCCESS: Integrated in Phoenix | Master #451 (See [https://builds.apache.org/job/Phoenix-master/451/])
PHOENIX-1370 Allow query timeout to differ from RPC timeout (jtaylor: rev b8526707b081ae7e5addf4c435921c066064cd6b)
* phoenix-core/src/main/java/org/apache/phoenix/query/QueryServicesOptions.java
* phoenix-core/src/main/java/org/apache/phoenix/mapreduce/CsvBulkLoadTool.java


> Allow query timeout to differ from RPC timeout
> ----------------------------------------------
>
>                 Key: PHOENIX-1370
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1370
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 5.0.0, 4.2, 3.2
>
>         Attachments: PHOENIX-1370.patch, PHOENIX-1370_v2.patch
>
>
> We previously forced hbase.rpc.timeout to match phoenix.query.timeoutMs because our queries would often perform a scan over an entire region's worth of data. These timeouts can really be independent now that stats are in place. Forcing them to be the same is not the right thing to do any longer.



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