[
https://issues.apache.org/jira/browse/ACCUMULO-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796304#comment-13796304
]
John Stoneham commented on ACCUMULO-1730:
-----------------------------------------
Sorry about that. I ran the tests after the cherry-pick but must have done
something out of order or pushed the wrong commits. Attached patch 0001 fixes
tests and behavior.
> 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
>
> Attachments:
> 0001-ACCUMULO-1730-Reinsert-changes-inadvertently-lost-in.patch
>
>
> 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)
