You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, unless I am confused about what to expect, I believe
getKeyValuePairsForKeysPrefixing() is not returning the correct information.
In fact, I believe it is returning "keys" that aren't even in the tree. It is
returning the values at a node, but not the full key that was stored.
What steps will reproduce the problem?
1. Run the attached TreeTest class.
Here is the output I am getting (using the most recent jar downloaded
yesterday):
**** Constructing new tree
Added key/value pair: /a/b/ -> 1
Added key/value pair: /a/blob/ -> 2
Added key/value pair: /a/blog/ -> 3
○
└── ○ /a/b
├── ○ / (1)
└── ○ lo
├── ○ b/ (2)
└── ○ g/ (3)
Keys prefixing /: {/, 1}
Keys prefixing /a/: {/, 1}
Keys prefixing /a/b/: {/a/b/, 1}
Keys prefixing /a/bl/:
Keys prefixing /a/blo/:
Keys prefixing /a/blob/: {/a/blob/, 2}
Keys prefixing /a/blog/: {/a/blog/, 3}
**** Constructing new tree
Added key/value pair: /a/b -> 1
Added key/value pair: /a/blob -> 2
Added key/value pair: /a/blog -> 3
○
└── ○ /a/b (1)
└── ○ lo
├── ○ b (2)
└── ○ g (3)
Keys prefixing /:
Keys prefixing /a:
Keys prefixing /a/b: {/a/b, 1}
Keys prefixing /a/bl: {/a/b, 1}
Keys prefixing /a/blo: {/a/b, 1}
Keys prefixing /a/blob: {/a/b, 1} {/a/blob, 2}
Keys prefixing /a/blog: {/a/b, 1} {/a/blog, 3}
It looks to me like the tree structure is correct, but
getKeyVAluePairsForKeysPrefixing() is returning the incorrect key/value pairs
for several values. For example, with first tree in the example above:
Keys prefixing /: {/, 1} <- No key "/" stored; this is the node for /a/b/
Keys prefixing /a/: {/, 1} <- Ditto; no key / was stored
I am using concurrent-trees-2.1.0.jar on Fedora 17.
Original issue reported on code.google.com by [email protected] on 5 Oct 2013 at 7:29
Original issue reported on code.google.com by
[email protected]
on 5 Oct 2013 at 7:29Attachments:
The text was updated successfully, but these errors were encountered: