[
https://issues.apache.org/jira/browse/ACCUMULO-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs updated ACCUMULO-1394:
----------------------------------------
Affects Version/s: (was: 1.4.4)
(was: 1.6.0)
1.4.0
Fix Version/s: (was: 1.5.0)
1.5.1
1.6.0
> 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.4.0, 1.4.1, 1.4.2, 1.4.3, 1.5.0
> Reporter: David Medinets
> Assignee: Christopher Tubbs
> Priority: Minor
> Fix For: 1.4.4, 1.5.1, 1.6.0
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)
