accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3393) Volume Chooser clean-up.
Date Wed, 10 Dec 2014 21:16:13 GMT


Christopher Tubbs commented on ACCUMULO-3393:

Some of the changes could be considered clean-up of the work done for ACCUMULO-3177 / ACCUMULO-3178.
But some of them (the sanity check, in particular, to ensure other implementations of VolumeChooser
do not choose something not available), has absolutely nothing to do with these changes, and
would make more sense as a separate issue (which also applies to 1.6, whereas this does not).
Maybe if just that were moved to a separate top-level task, along with a description update
here, it would help clarify the relationship between the changes which remain and the parent

bq. More importantly, there's no reason for it to be called out in release notes independent
of the parent issue.

Sub-tasks are already listed separately in our CHANGES file, independent of their parent issues,
and we manually select what to include in the published release notes, so this is not a good
reason to organize something as a sub-task. A good reason for organizing something as a sub-task,
is that the goals it describes represents a distinct task in order to label the parent task
as completed. Some of the changes in the review are of that nature, but some are not (in particular,
the sanity check I described). I'd just prefer we keep JIRA organized a bit better. Don't
forget, we can also link issues with a particular relationship type in JIRA.

> Volume Chooser clean-up.
> ------------------------
>                 Key: ACCUMULO-3393
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: tserver
>    Affects Versions: 1.7.0
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Blocker
>             Fix For: 1.7.0
> clean up of the Volume Chooser additions needed for per-table use.

This message was sent by Atlassian JIRA

View raw message