accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-4638) Simplify how we use AccumuloConfiguration
Date Fri, 12 May 2017 03:43:04 GMT

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

Christopher Tubbs resolved ACCUMULO-4638.
-----------------------------------------
    Resolution: Fixed

> Simplify how we use AccumuloConfiguration
> -----------------------------------------
>
>                 Key: ACCUMULO-4638
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4638
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>             Fix For: 2.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Working on ACCUMULO-4050, I've realized that there's a bunch of simplifications we can
do to the existing AccumuloConfiguration and related objects. These are generally lots of
small refactorings, but there's sufficient cleanup that I need to do it separately from ACCUMULO-4050,
otherwise it's going to overhwelm me and I'm never going to finish that issue.
> Specific things include:
> * Remove redundant ways to get the default config
> * Move static type converter method clutter from the AccumuloConfiguration API (to separate
class)
> * Streamline default config construction with stream syntax
> * Simplify internal predicates for filtering properties with lambdas
> * Rename ServerConfigurationFactory.getConfiguration() so it reflects that it is the
system config



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message