You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Billie Rinaldi (JIRA)" <ji...@apache.org> on 2015/04/20 22:54:00 UTC
[jira] [Commented] (ACCUMULO-3742) Multiple-valued client
properties don't work
[ https://issues.apache.org/jira/browse/ACCUMULO-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503590#comment-14503590 ]
Billie Rinaldi commented on ACCUMULO-3742:
------------------------------------------
Mostly we are using PropertiesConfiguration to read a config file. We could introduce a new constructor to ClientConfiguration that takes a config file and handles it properly (see below), although that would not prevent people from using it the broken way.
{noformat}
public ClientConfiguration(String configFile) throws ConfigurationException {
this(new PropertiesConfiguration(), configFile);
}
private ClientConfiguration(PropertiesConfiguration propertiesConfiguration, String configFile) throws ConfigurationException {
super(propertiesConfiguration);
// Don't do list interpolation
propertiesConfiguration.setListDelimiter('\0');
propertiesConfiguration.load(configFile);
}
{noformat}
> Multiple-valued client properties don't work
> --------------------------------------------
>
> Key: ACCUMULO-3742
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3742
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Reporter: Billie Rinaldi
> Assignee: Billie Rinaldi
> Fix For: 1.7.0
>
>
> When we use the pattern new ClientConfiguration(new PropertiesConfiguration), the PropertiesConfiguration has already interpreted any multi-valued properties as lists, so when we read those properties as strings we only get the first value in the list. This affects instance.zookeeper.host and trace.span.receivers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)