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 2014/08/11 23:04:13 UTC
[jira] [Updated] (ACCUMULO-3019) Fix ServerConfiguration
deprecation
[ https://issues.apache.org/jira/browse/ACCUMULO-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Tubbs updated ACCUMULO-3019:
----------------------------------------
Fix Version/s: 1.6.1
> Fix ServerConfiguration deprecation
> -----------------------------------
>
> Key: ACCUMULO-3019
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3019
> Project: Accumulo
> Issue Type: Sub-task
> Components: master, tserver
> Reporter: Eric Newton
> Assignee: Eric Newton
> Fix For: 1.6.1, 1.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The deprecation of ServerConfiguration causes two problems:
> 1) eclipse is showing me ~300 warnings, so I'm missing other warnings in the noise
> 2) ServerConfiguration is passed to some plug-ins (Balancer, at least), so any existing plug-ins are broken by the change.
> In the past, I would have been fine with just switching to the new class {{ServerConfigurationFactory}} but a growing user base and petabytes of existing systems gives me pause.
> Instead, I'm thinking we hoist the most popular methods to an abstract ServerConfiguration, and provide ServerConfiguationFactory as the implementation. This way the extensions continue to work.
> I'm still not sure what to do about static calls to get the SiteConfiguration.
--
This message was sent by Atlassian JIRA
(v6.2#6252)