You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Greg Bowyer (Created) (JIRA)" <ji...@apache.org> on 2011/11/02 21:39:32 UTC
[jira] [Created] (SOLR-2871) Add the ability to assert SOLR cache
contents
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
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)
--
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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-2871) Add the ability to assert SOLR cache
contents
Posted by "Greg Bowyer (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Greg Bowyer updated SOLR-2871:
------------------------------
Attachment: 0001-Added-in-assertions-for-solr-caches.patch
patch to add assertions / guarantees etc to solr caches
> 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)
--
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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-2871) Add the ability to assert SOLR cache
contents
Posted by "Greg Bowyer (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Greg Bowyer updated SOLR-2871:
------------------------------
Description:
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
was:
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)
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org