accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Berman (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1397) Provide shell support for .accumulorc file
Date Mon, 11 Nov 2013 19:05:18 GMT


Michael Berman commented on ACCUMULO-1397:

I'm not doing any more work on this than is covered by my work on SSL (ACCUMULO-1009), which
includes the introduction of ClientConfiguration.  The files I attached to this bug are way
old and are subsumed by work on that ticket.  I was hoping to get the config changes in early
so I could focus on the transport part of the SSL changes on the other ticket, but the config
changes turned out to be one of the most contentious parts, so the possibility of the standalone
config changes kind of got lost.

As far as this ticket goes, I think it should be implemented with the ClientConfig changes
in mind, but my changes don't actually include the switches that shell users are most interested
in (user, auth, default table, etc), so I wouldn't say it actually addresses this ticket.

I'd be happy to take this up in 1.7, but I think at this point it should be considered to
not have made the feature freeze for 1.6.

> Provide shell support for .accumulorc file
> ------------------------------------------
>                 Key: ACCUMULO-1397
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: shell
>            Reporter: Mike Drob
>             Fix For: 1.6.0
>         Attachments:,
> It would be nice to support a {{.accumulorc}} file for specifying some amount of configured
default values for each shell.
> Probably would want to have a tiered approach with values in {{$ACCUMULO_HOME/conf/accumulorc}}
being overwritten by those in {{$HOME/.accumulorc}} if present. Might also check for {{/etc/accumulorc}}
or similar.
> This should support some level of specifying a user principal and authentication token.
Might also be useful to specify debug mode on/off, traces on/off, a default table/pattern
to perform operations against. Other ideas appreciated, but not required. We can always create
more tickets for them in the future.
> For inspiration, see {{.eucarc}}

This message was sent by Atlassian JIRA

View raw message