You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2015/12/30 22:46:49 UTC

[jira] [Commented] (ACCUMULO-3734) Possible bug in VisibilityConstraint

    [ https://issues.apache.org/jira/browse/ACCUMULO-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075438#comment-15075438 ] 

Josh Elser commented on ACCUMULO-3734:
--------------------------------------

Deferred out of 1.7.1 since 1.7.0 already has the potential bug. [~kturner], feel free to bring it back if you think 1.7.1 should require this investigation to happen (and, ideally, you can do such investigation :D)

> Possible bug in VisibilityConstraint
> ------------------------------------
>
>                 Key: ACCUMULO-3734
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3734
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Keith Turner
>             Fix For: 1.7.2, 1.8.0
>
>
> ACCUMULO-1681 modified which constructor from {{VisibilityEvaluator}} that  {{VisibilityConstraint}} uses.  After the modification {{escape()}} is no longer called (the old constructor called escape, and the new one does not).  Not sure if this is a problem.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)