[
https://issues.apache.org/jira/browse/HBASE-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016685#comment-13016685
]
stack commented on HBASE-3750:
------------------------------
Do you think this the way to go Ted? How you think people use the HTablePool?
I'd think they'd check out an HTable instance, add an edit, then check it back
in? If this is the case, then we'll flush each single edit. Or, do you think
folks check out HTable instance, keep it around a while putting multiple edits
on it and only then check it back in perhaps not using it again?
I wonder if a warning up in javadoc that we do NOT flush on return to the pool,
so client needs to would be a better way to go?
I'm not sure.
> HTablePool.putTable() should call table.flushCommits()
> ------------------------------------------------------
>
> Key: HBASE-3750
> URL: https://issues.apache.org/jira/browse/HBASE-3750
> Project: HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.90.1
> Reporter: Ted Yu
> Assignee: Ted Yu
> Attachments: 3750.txt
>
>
> Currently HTablePool.putTable() doesn't call table.flushCommits()
> This may turn out to be surprise for users
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
