[
https://issues.apache.org/jira/browse/HBASE-21392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702152#comment-16702152
]
Xu Cang commented on HBASE-21392:
---------------------------------
Just some observation: On branch-1, we already have this mechanism in
HTablePool class.
[https://github.com/apache/hbase/blob/branch-1/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTablePool.java#L638]
But seems it doesn't cover all the cases.
I do agree this feature is logical and good. +0 (non-binding)
The exception method could be clearer.
> HTable can still write data after calling the close method.
> -----------------------------------------------------------
>
> Key: HBASE-21392
> URL: https://issues.apache.org/jira/browse/HBASE-21392
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Affects Versions: 1.2.0, 2.1.0, 2.0.0
> Environment: HBase 1.2.0
> Reporter: lixiaobao
> Assignee: lixiaobao
> Priority: Major
> Attachments: HBASE-21392.patch, HBASE-21392.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> HTable can still write data after calling the close method.
>
> {code:java}
> val conn = ConnectionFactory.createConnection(conf)
> var table = conn.getTable(TableName.valueOf(tableName))
> val put = new Put(rowKey.getBytes())
> put.addColumn("cf".getBytes(), columnField.getBytes(), endTimeLong,
> Bytes.toBytes(line.getLong(8)))
> table.put(put)
> //call table close() method
> table.close()
> //put again
> val put1 = new Put(rowKey4.getBytes())
> out1.addColumn("cf".getBytes(), columnField.getBytes(), endTimeLong,
> Bytes.toBytes(line.getLong(8)))
> table.put(put1)
> {code}
>
> after call close method ,can alse write data into HBase,I think this does not
> match close logic.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
