[
https://issues.apache.org/jira/browse/ACCUMULO-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281259#comment-13281259
]
Keith Turner commented on ACCUMULO-420:
---------------------------------------
According to the following its seems that write are applied in the order that
they are made. Also the tserver may need to call sync before reading, but as
long as it always sees data in order written it should be ok to not call sync.
http://zookeeper.apache.org/doc/r3.1.2/zookeeperProgrammers.html#ch_zkGuarantees
Other places in existing code may need to call sync.
> Allow per compaction iterator settings
> --------------------------------------
>
> Key: ACCUMULO-420
> URL: https://issues.apache.org/jira/browse/ACCUMULO-420
> Project: Accumulo
> Issue Type: New Feature
> Reporter: Keith Turner
> Assignee: Sapan Shah
> Fix For: 1.5.0
>
>
> It may be useful to allow the compact command to specify an iterator to be
> used for that compaction. For example if someone wanted to apply a filter
> once to a table, they could force a compaction with that filter.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
