accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3057) Include "source" for configuration properties
Date Mon, 11 Aug 2014 18:56:12 GMT


Christopher Tubbs commented on ACCUMULO-3057:

The shell constructs an instance of each configuration in the hierarchy and shows when they
differ from one level to the next. The limitation is that if it is defined at a more proximal
scope, such as per-table, to be the same as the more distant scope, such as the default, one
can not tell that it is set in the per-table config. This was fine in most circumstances,
but may be confusing in some special cases.

 (default) K -> V1
 (namespace) null, inherits K -> V1
 (table) K -> V1

User sees:
 (default) K -> V1

User expects to be able to override by setting namespace to K -> V2, but in reality, this
is what happens:
 (default) K -> V1
 (namespace) K -> V2
 (table) K -> V1

This could be addressed if we show overrides even when they are identical to the previous
level in the hierarchy.

In code, I'm not sure how we'd want to do it, but that's basically how the shell works and
some of its nuances.

> Include "source" for configuration properties
> ---------------------------------------------
>                 Key: ACCUMULO-3057
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Josh Elser
> When using an AccumuloConfiguration, it would be nice to know the provenance of a Property.
Since these are typically constructed in some hierarchy (ZooConfiguration, SiteConfiguration,
DefaultConfiguration), it would be useful to know where the current value for a Property was

This message was sent by Atlassian JIRA

View raw message