[
https://issues.apache.org/jira/browse/LUCENE-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748412#comment-13748412
]
ASF subversion and git services commented on LUCENE-5186:
---------------------------------------------------------
Commit 1516773 from [~jpountz] in branch 'dev/trunk'
[ https://svn.apache.org/r1516773 ]
LUCENE-5186: Added CachingWrapperFilter.getFilter.
> Add CachingWrapperFilter.getFilter()
> ------------------------------------
>
> Key: LUCENE-5186
> URL: https://issues.apache.org/jira/browse/LUCENE-5186
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Reporter: Trejkaz
> Assignee: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-5186.patch
>
>
> There are a couple of use cases I can think of where being able to get the
> underlying filter out of CachingWrapperFilter would be useful:
> 1. You might want to introspect the filter to figure out what's in it (the
> use case we hit.)
> 2. You might want to serialise the filter since Lucene no longer supports
> that itself.
> We currently work around this by subclassing, keeping another copy of the
> underlying filter reference and implementing a trivial getter, which is an
> easy workaround, but the trap is that a junior developer could unknowingly
> create a CachingWrapperFilter without knowing that the
> BetterCachingWrapperFilter exists, introducing a filter which cannot be
> introspected.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
