tephra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Poorna Chandra (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TEPHRA-159) Optimize read-only client
Date Wed, 12 Oct 2016 19:35:20 GMT

     [ https://issues.apache.org/jira/browse/TEPHRA-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

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

View raw message