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-780) Accumulo should have a configurator
Date Tue, 25 Feb 2014 20:38:22 GMT

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

Josh Elser commented on ACCUMULO-780:
-------------------------------------

bq. I think the heuristics are a good idea, but it seems like they can be addressed in (more
specific) follow on issues, can't they?

I thought this was the initial intent of this ticket. Does that mean that the scope of this
ticket is to substitute Java, ZooKeeper and Hadoop home env vars into a template? I have no
problem if the work is broken down into pieces (in fact, it would probably be nice for everyone),
but I don't think what is currently targeted is sufficient to remove {{conf/examples/*}} completely.

> Accumulo should have a configurator
> -----------------------------------
>
>                 Key: ACCUMULO-780
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-780
>             Project: Accumulo
>          Issue Type: New Feature
>          Components: scripts
>            Reporter: John Vines
>            Assignee: John McNamee
>             Fix For: 1.7.0
>
>         Attachments: ACCUMULO-780.v1.patch
>
>
> We currently have a few different footprints available for users. We should use those
as a base and allow users to quickly and conveniently configure their system for whatever
size footprint they want. We can use the current as a baseline and extrapolate/interpolate
for whichever setup they're using. This way we don't have to worry about maintaining a bunch
of different sizes and instead just have an algorithm that needs occasional loving.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message