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

Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2013/05/16 20:03:15 UTC

[jira] [Resolved] (ACCUMULO-1394) Allow RegExFilter subclass to call setNegate.

     [ https://issues.apache.org/jira/browse/ACCUMULO-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Tubbs resolved ACCUMULO-1394.
-----------------------------------------

    Resolution: Fixed
    
> Allow RegExFilter subclass to call setNegate.
> ---------------------------------------------
>
>                 Key: ACCUMULO-1394
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1394
>             Project: Accumulo
>          Issue Type: Improvement
>    Affects Versions: 1.5.0, 1.4.1, 1.4.2, 1.6.0, 1.4.3, 1.4.4
>            Reporter: David Medinets
>            Assignee: Christopher Tubbs
>            Priority: Minor
>             Fix For: 1.5.0, 1.4.4
>
>
> I wrote an iterator that sets RegExFilter options inside its init() method. I created a HashMap to hold options, then added entries for RegExFilter.COLF_REGEX. However, the Filter.NEGATE is private and the setNegate function only accepts an IteratorSetting option which I don't have inside my iterator's init() method (true?). So I simply used a "negate" string literal which I don't like.
> I propose making NEGATE public as is done in the RegExFilter class. Any reason not to? Is there a better approach?

--
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: http://www.atlassian.com/software/jira