accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Drew Farris (JIRA)" <>
Subject [jira] [Updated] (ACCUMULO-795) MockTable doesn't obey useVersions parameter
Date Thu, 11 Oct 2012 00:29:03 GMT


Drew Farris updated ACCUMULO-795:

    Attachment: ACCUMULO-795.patch

Shuffled things around a bit -- {{IteratorUtil.generateInitialTableProperties()}} now takes
a boolean argument {{limitVersion}} what will cause the Versioning Iterator to be added to
the table if true. 

This way, if we add additional default table properties, such as a Constraint that limits
key size, we can add them here, and not worry about code calling {{generateInitialTableProperties}}
or not. 

The general contract would be that {{generateInitialTableProperties}} is always called when
a new table is created regardless of whether it is mock or real.
> MockTable doesn't obey useVersions parameter
> --------------------------------------------
>                 Key: ACCUMULO-795
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.5.0, 1.4.1
>            Reporter: Drew Farris
>            Assignee: John Vines
>            Priority: Minor
>         Attachments: ACCUMULO-795.patch, ACCUMULO-795.patch, ACCUMULO-795.patch
> The constructor for {{MockTable}} will call {{IteratorUtil.generateInitialTableProperties()}},
and thus set a versioning iterator on itself regardless of whether the useVersion parameter
is set to true or false. 
> I believe {{MockTable}}'s constructor should call IteratorUtil.generateInitialTableProperties()
only if useVersions is true, otherwise, it should populate {{settings}} with a new {{TreeMap}}

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