Poorna Chandra updated TEPHRA-159:
    Issue Type: Sub-task  (was: Improvement)
        Parent: TEPHRA-189

> Optimize read-only client
> -------------------------
>                 Key: TEPHRA-159
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-159
>             Project: Tephra
>          Issue Type: Sub-task
>            Reporter: James Taylor
>            Assignee: Poorna Chandra
>              Labels: phoenix
> Allow a transaction client to declare itself as read-only to prevent the 
> necessity of adding its transaction IDs to the in-flight transaction list. 
> It's pretty typical that separate connections are used for reading and 
> writing. Phoenix would leverage this when a connection is declared as 
> read-only through standard JDBC Connection.setReadOnly(boolean) method.

This message was sent by Atlassian JIRA

Reply via email to