[
https://issues.apache.org/jira/browse/ACCUMULO-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Stoneham reopened ACCUMULO-1730:
-------------------------------------
This mentions it was fixed in 1.4.5 and 1.5.1, but it appears that no commit
was actually pushed to any of the backport branches.
Appears that c091b54 was intended for 1.4.5, and a25e3af was intended for 1.5.1.
I've got some further commits that fix the offsets for the AND and OR nodes in
such a way as they are useful for substringing the actual expression. Will
provide pull requests on GitHub.
> ColumnVisibility parse tree nodes do not have correct location offsets for
> AND and OR nodes
> -------------------------------------------------------------------------------------------
>
> Key: ACCUMULO-1730
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1730
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.5.0
> Reporter: John Stoneham
> Assignee: Eric Newton
> Priority: Trivial
> Fix For: 1.4.5, 1.5.1, 1.6.0
>
>
> Trying to do some transformations on visibility strings and running into
> issues working with the parse tree:
> Clojure 1.5.1
> user=> (import [org.apache.accumulo.core.security ColumnVisibility])
> org.apache.accumulo.core.security.ColumnVisibility
> user=> (def vis (ColumnVisibility. "(W)|(U|V)"))
> #'user/vis
> user=> (.getTermStart (first (.getChildren (.getParseTree vis))))
> 1
> user=> (.getTermEnd (first (.getChildren (.getParseTree vis))))
> 2
> user=> (.getTermStart (second (.getChildren (.getParseTree vis))))
> 0
> user=> (.getTermEnd (second (.getChildren (.getParseTree vis))))
> 8
> Shouldn't those last two be 5 and 8?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
