You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "John Vines (Created) (JIRA)" <ji...@apache.org> on 2012/02/17 00:38:57 UTC
[jira] [Created] (ACCUMULO-415) support iterator profiles
support iterator profiles
-------------------------
Key: ACCUMULO-415
URL: https://issues.apache.org/jira/browse/ACCUMULO-415
Project: Accumulo
Issue Type: Improvement
Reporter: John Vines
Fix For: 1.5.0
Currentlyif a user wants to have multiple iterator configurations for a table, they must be individually set on the scanner. This makes it difficult, so we should provide the ability for a table to have profiles. By default we should also support a naked profile for use by client side deletes so transformed keys do not create problems.
--
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
[jira] [Commented] (ACCUMULO-415) support iterator profiles
Posted by "Keith Turner (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210686#comment-13210686 ]
Keith Turner commented on ACCUMULO-415:
---------------------------------------
Currently scan iterators are stored as per table config as shown below.
{noformat}
root@test14 ctt_001> config -t ctt_001 -f iterator.scan
---------+---------------------------------------------+-------------------------------------------------------------------
SCOPE | NAME | VALUE
---------+---------------------------------------------+-------------------------------------------------------------------
table | table.iterator.scan.vers .................. | 20,org.apache.accumulo.core.iterators.user.VersioningIterator
table | table.iterator.scan.vers.opt.maxVersions .. | 1
---------+---------------------------------------------+-------------------------------------------------------------------
{noformat}
One way to support iterator profiles is to use a different prefix in the per table config. For example table.iterator.profile.<prof name>.scan.<iter name>.
The Scanner could have a method added to it that allows a user to select a profile to use. This is backwards compatible because it just adds a method to the scanner. Table operations API would need to be adjusted to support profiles, hopefully we can do this in a backwards compat way too.
> support iterator profiles
> -------------------------
>
> Key: ACCUMULO-415
> URL: https://issues.apache.org/jira/browse/ACCUMULO-415
> Project: Accumulo
> Issue Type: Improvement
> Reporter: John Vines
> Fix For: 1.5.0
>
>
> Currentlyif a user wants to have multiple iterator configurations for a table, they must be individually set on the scanner. This makes it difficult, so we should provide the ability for a table to have profiles. By default we should also support a naked profile for use by client side deletes so transformed keys do not create problems.
--
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