hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "CHIA-PING TSAI (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-17735) The usage of getTable() is different between AsyncConnection and Connection
Date Sun, 05 Mar 2017 08:13:32 GMT

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

CHIA-PING TSAI updated HBASE-17735:
-----------------------------------
    Description: 
I'm employing the AsyncConnection to rewrite our application. I find that the AsyncConnection#getTable()
and Connection#getTable() have some "slight" differences.
# Connection#getTable() throws IOException;
# AsyncConnection#getTable() requires the pool;
# AsyncTable doesn't need to be closed

It may confuse the developers if they have no time to trace the source code (smile). Should
we unify them?

Any suggestion is welcomed

  was:
I'm employing the AsyncConnection to rewrite our application. I find that the AsyncConnection#getTable()
and Connection#getTable() have some "slight" differences.
# Connection#getTable() throws IOException;
# AsyncConnection#getTable() requires the pool;
# AsyncTable doesn't need to be closed

It may confuse the developers if they have no time to trace the source code (smile). May be
we can unify them?

Any suggestion is welcomed


> The usage of getTable() is different between AsyncConnection and Connection
> ---------------------------------------------------------------------------
>
>                 Key: HBASE-17735
>                 URL: https://issues.apache.org/jira/browse/HBASE-17735
>             Project: HBase
>          Issue Type: Wish
>            Reporter: CHIA-PING TSAI
>            Priority: Minor
>
> I'm employing the AsyncConnection to rewrite our application. I find that the AsyncConnection#getTable()
and Connection#getTable() have some "slight" differences.
> # Connection#getTable() throws IOException;
> # AsyncConnection#getTable() requires the pool;
> # AsyncTable doesn't need to be closed
> It may confuse the developers if they have no time to trace the source code (smile).
Should we unify them?
> Any suggestion is welcomed



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message