You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2018/02/22 23:46:00 UTC

[jira] [Reopened] (ACCUMULO-4753) Update to commons-configuration2

     [ https://issues.apache.org/jira/browse/ACCUMULO-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Tubbs reopened ACCUMULO-4753:
-----------------------------------------
      Assignee: Christopher Tubbs  (was: Josh Elser)

Re-opening this issue as follow-on to the deprecation/removal path done in ACCUMULO-4611 to eliminate commons-configuration from the public API. This issue can be used to track the actual update to commons-configuration2.

As I see it, the most complicated part of this update involves migrating the file reloading code from our metrics configuration.

> Update to commons-configuration2
> --------------------------------
>
>                 Key: ACCUMULO-4753
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4753
>             Project: Accumulo
>          Issue Type: Task
>            Reporter: Josh Elser
>            Assignee: Christopher Tubbs
>            Priority: Critical
>             Fix For: 2.0.0
>
>
> I'm looking at what it would take to get Accumulo working against Hadoop 3.
> Thankfully, the only issue seems to be around the commons-configuration2 update that Hadoop has changed to. With our use of commons-configuration (1) for ClientConfiguration and others, this brings in multiple versions of commons-beanutils artifacts which result in exceptions at runtime.
> I think the quickest solution is to just upgrade ourselves to use commons-configuration2. The "long-term" solution is to try to switch over to the shaded jars that Hadoop is publishing (but I'm reticent to sign up for that right now :P).
> I think we need to have a discussion about where we want to land this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)