You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2012/10/09 21:30:02 UTC
[jira] [Commented] (ACCUMULO-795) MockTable doesn't obey
useVersions parameter
[ https://issues.apache.org/jira/browse/ACCUMULO-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472661#comment-13472661 ]
Keith Turner commented on ACCUMULO-795:
---------------------------------------
I think the test should that creates a table w/o the versioning iterator should also insert some data that would normally be suppressed by the versioning iterator. Do this before attaching the iterator.
> MockTable doesn't obey useVersions parameter
> --------------------------------------------
>
> Key: ACCUMULO-795
> URL: https://issues.apache.org/jira/browse/ACCUMULO-795
> 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
>
>
> 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: http://www.atlassian.com/software/jira