accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3742) Multiple-valued client properties don't work
Date Tue, 21 Apr 2015 03:42:59 GMT

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

Josh Elser commented on ACCUMULO-3742:
--------------------------------------

+1 on {{ACCUMULO-3742.1.patch}}.

Only thought I had when looking it over was that it might be better for our purposes to only
expose a ClientConfiguration constructor that takes a {{File}} instead of a {{String}}, but,
looking at the PropertiesConfiguration hierarchy (specifically AbstractFileConfiguration),
they internally maintain the filename as a string, so it's no different than how we do things
now unless we add more checks ourselves.

> 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
>            Priority: Blocker
>             Fix For: 1.7.0
>
>         Attachments: ACCUMULO-3742.1.patch
>
>
> 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)

Mime
View raw message