[
https://issues.apache.org/jira/browse/SOLR-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Bowyer closed SOLR-2871.
-----------------------------
Resolution: Invalid
When I raised this issue I had a poor understanding about what solr caches
contain
> Add the ability to assert SOLR cache contents
> ---------------------------------------------
>
> Key: SOLR-2871
> URL: https://issues.apache.org/jira/browse/SOLR-2871
> Project: Solr
> Issue Type: Improvement
> Components: search
> Affects Versions: 3.3
> Reporter: Greg Bowyer
> Labels: cache, patch
> Attachments: 0001-Added-in-assertions-for-solr-caches.patch
>
>
> Due to investigations on my part in looking into a possible misbehaviour (or
> misunderstanding of the correct behaviour) of the filter cache this commit
> adds in the ability to assert that the form of items presented to solr caches
> are valid and expected.
> The interface for this is known as a CacheGuarantor, by default this interface
> resolves a NoOp implementation that does nothing (and should be nicely
> eliminated by the JIT as dead code).
> For the filterCache a basic (and potentially incorrect) guarantor is setup
> that demands all keys presented to the filter cache are FilterQueries.
> This currently makes function queries fail unit tests, which may (or may
> not !) be a bug (and I am guessing probably not here since I am clearly
> missing some deeper truth)
> I tend to work off github so the patch is also on the tip of this branch
> https://github.com/GregBowyer/lucene-solr/commits/cache-guarantors
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
