accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1160) Clean up usage of Passwords where possible, deprecate others
Date Thu, 07 Mar 2013 19:28:13 GMT


Christopher Tubbs commented on ACCUMULO-1160:

I put a lot of work into the mapreduce APIs, but they got broken as a result of this new security
token stuff (ACCUMULO-259) before I had a chance to test all of it (especially ACCUMULO-829).
I will fix them once I'm satisfied the token stuff is stable. Especially, because I want to
ensure ACCUMULO-829 changes are compatible, and that depends on consistent, convenient, and
stable serialization of these new tokens.
> Clean up usage of Passwords where possible, deprecate others
> ------------------------------------------------------------
>                 Key: ACCUMULO-1160
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client
>            Reporter: John Vines
>            Assignee: Billie Rinaldi
>             Fix For: 1.5.0
> Littered throughout the code we still have anticipation of password vs. token items.
We need to determine which items have changed sufficiently that we can remove any notion of
a password field before release.
> I think the candidates are-
> Shell
> mapreduce APIs
> I think Shell needs it, but I think the CLI can scratch it. I'm uncertain about mapred(uce)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message