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] [Commented] (ACCUMULO-324) System/site constraints and iterators should NOT affect the METADATA table
Date Thu, 13 Jun 2013 16:05:20 GMT

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

Christopher Tubbs commented on ACCUMULO-324:
--------------------------------------------

System-wide configuration should be added/merged with the default namespace configuration,
which won't apply to the system tables.
                
> System/site constraints and iterators should NOT affect the METADATA table
> --------------------------------------------------------------------------
>
>                 Key: ACCUMULO-324
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-324
>             Project: Accumulo
>          Issue Type: Sub-task
>    Affects Versions: 1.4.0
>            Reporter: John Vines
>             Fix For: 1.6.0
>
>
> Currently any system and site wide constraints and iterators set will affect the !METADATA
table. While we want to provide this level of configuration to make things easier for users,
we also don't want to have this feature which is essentially useless due to ill effects on
this critical table. We should make specific exceptions that any site/system-wide iterators,
constraints, and other scan/write-time affecting configurations do not affect the !METADATA
site. If we need an iterator/constraint running against the !METADATA table, it will have
to be configured for it specifically.
> Do not fix until after ACCUMULO-323 has been resolved.

--
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