accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <>
Subject [jira] [Created] (ACCUMULO-841) Randomwalk State is a strange tuple
Date Wed, 31 Oct 2012 18:08:14 GMT
John Vines created ACCUMULO-841:

             Summary: Randomwalk State is a strange tuple
                 Key: ACCUMULO-841
             Project: Accumulo
          Issue Type: Bug
          Components: test
            Reporter: John Vines
            Assignee: John Vines
             Fix For: 1.5.0

So, I'm working on the Security randomwalk test with ACCUMULO-259 and I stumbled across some
strange behavior.

State seems to be a fancy, but locked down, tuple. It contains a Map, Properties, and a few
other Accumulo related state items. And it has methods for accessing these, which are a bit
more defined. These are necessary because all of the internals are private. 

The Map specifically has a peculiar point where it will throw a RuntimeException when getting
a non-existant key. At first I found myself wondering how badly would things break if I changed
that behavior. But after talking to Adam, this lead to a larger question of why does a testing
framework have a tuple with locked down internal classes?

My knowledge on the background of the Randomwalk framework isn't the best, so I'm wondering
if I'm overlooking something or if the framework itself is too conservative. At the bare minimum,
I believe something needs to be changed with the get functionality. Though there is reasonable
suspicion to believe there is a larger change that needs to happen here.

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