hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chia-Ping Tsai (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-3737) HTable - delete(List<Delete>) doesn't use writebuffer
Date Sat, 26 Aug 2017 15:13:01 GMT

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

Chia-Ping Tsai resolved HBASE-3737.
-----------------------------------
    Resolution: Not A Problem

HBASE-18500 remove the BM from HTable.

> HTable - delete(List<Delete>) doesn't use writebuffer
> -----------------------------------------------------
>
>                 Key: HBASE-3737
>                 URL: https://issues.apache.org/jira/browse/HBASE-3737
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Doug Meil
>            Priority: Minor
>
> I just realized that htable.delete(List<Delete>) doesn't use the writebuffer and
processes the list immediately, but htable.put(List<Put>) does use the writebuffer (i.e.,
send when filled). Likewise, htable.delete(Delete) sends immediately.
>  
> Out of sheer curiosity, why?  With the 'batch' methods now in place, it seems like it
would be consistent for 'delete' and 'put' to use the writebuffer (assuming it is expanded
to hold more than Puts), whereas 'batch' methods process immediately.
> This isn't a huge issue, but it does seem a little inconsistent. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message