[
https://issues.apache.org/jira/browse/ACCUMULO-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153078#comment-13153078
]
Jesse Yates commented on ACCUMULO-156:
--------------------------------------
So if its a toy project, it still shouldn't be in the codebase - github or
something similar would be a better place (its not really core to how accumulo
runs, which should be pretty solid), to branch the stuff for testing until it
is production ready.
As far as acceptance test, I'm talking about the randomwalk, performance,
scalability stuff under org.apache.accumulo.server.test* That stuff really
isn't core to how the system works, but is really better part of some testing
suite. The code base already has those tests (which are run on a live cluster
before we push out a release) under the /test fold. I'm just talking about
creating an acceptance-test module, where we can co-locate all those pieces,
rather than having them scattered.
> Refactor Trie
> -------------
>
> Key: ACCUMULO-156
> URL: https://issues.apache.org/jira/browse/ACCUMULO-156
> Project: Accumulo
> Issue Type: Improvement
> Components: client
> Affects Versions: 1.4.0, 1.3.6
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Fix For: 1.4.0
>
> Attachments: java_ACCUMULO-156.patch
>
>
> Trie has a main method (apparently) for testing. This needs to be moved to
> its own unit test. Also, Trie is located in core.impl, but is only used in
> the server module - it needs to be moved as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
