accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-733) add description of the BatchWriter behavior
Date Tue, 18 Dec 2012 17:32:12 GMT

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

Christopher Tubbs updated ACCUMULO-733:
---------------------------------------

    Fix Version/s: 1.5.0
    
> add description of the BatchWriter behavior
> -------------------------------------------
>
>                 Key: ACCUMULO-733
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-733
>             Project: Accumulo
>          Issue Type: Bug
>          Components: docs
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>            Priority: Trivial
>             Fix For: 1.5.0
>
>
> Keith Turner wrote up a nice description of the BatchWriter on the gora mailing list.
I think it deserves to be in the BatchWriter documentation:
> {quote}
> When the user creates a
> BatchWriter to write to Accumulo they specify how much memory and how
> many threads it should use.  As the user adds mutations to the batch
> writer it buffers them.  Once the buffered mutations have used half of
> the user specified, the mutations are dumped into the background to be
> written by a thread pool.  If the user specified memory completely
> fills up, then writes are held.  When a user calls flush, it does not
> return until all buffered mutations are written.
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message