accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1757) Create BatchDeleter with a provided BatchWriter instead of creating a new one
Date Mon, 07 Oct 2013 22:49:42 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13788665#comment-13788665
] 

Josh Elser commented on ACCUMULO-1757:
--------------------------------------

Not a huge issue, but you would also have to make a getter for the 'table' member on BatchWriterImpl
so we can assert that the BatchWriter passed into the BatchDeleter is actually writing to
the correct table provided by the createBatchDeleter method on Connector.

I can see the worth in being able to reuse one BatchWriter in a VM to minimize the overhead
of the Thrift calls that these classes require, but it looks like it might require a little
bit of thought to make sure the API doesn't get convoluted.

> Create BatchDeleter with a provided BatchWriter instead of creating a new one
> -----------------------------------------------------------------------------
>
>                 Key: ACCUMULO-1757
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1757
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>            Reporter: John Vines
>            Priority: Minor
>             Fix For: 1.6.0
>
>
> For the BatchDeleter, you pass it all the configs you need to create both a Scanner and
a BatchWriter for it to provide really convenient deletes. However, if a client already has
a BatchWriter, it would be convenient to just hand it an existing BatchWriter to use instead
of creating a separate one.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message