accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-420) Allow per compaction iterator settings
Date Wed, 23 May 2012 20:39:41 GMT


Keith Turner commented on ACCUMULO-420:

Adding this to the API should be fairly simple.  Thinking of simply adding the following to

  public void compact(String tableName, Text start, Text end, List<IteratorSettings>
iterators, boolean flush, boolean wait)

However making this functionality available from the shell does not seem so simple.  Billie
and I discussed this today and came up with some initial thoughts, but did not decide on anything.

 * Allow arguments to the compact command like <prio>=<iterclass>{ <prio>=<iterclass>).
 For each iterator argument given to the compact command it would then prompt you for options.
 This does not seem great for writing scripts that initiate compactions.
 * Repurpose the setscaniter command to allow creating an iterator profile in the shell. 
Then a scan or compact command could reference this iterator profile.  This way iterators
configured on the shell are only used if explicitly requested.  This also does not seem great
for scripting compactions.
 * Compact command could take an argument that is a complex expression that encapsulates iterators
and their options.   This is great for scripting but not so good for interactive use.  

> Allow per compaction iterator settings
> --------------------------------------
>                 Key: ACCUMULO-420
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message