You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2010/02/11 04:10:27 UTC
[jira] Updated: (SOLR-1765) HTTP Caching related headers are
incorrect for distributed searches
[ https://issues.apache.org/jira/browse/SOLR-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-1765:
---------------------------
Component/s: (was: multicore)
(was: search)
Description:
When searching across multiple shards with HTTP caching enabled, the Caching related headers (ETag, Cache-Control, Last-Modified) in the response are based on the "index" of the coordinating solr core, and are not influenced by the properties of the shards. For example, take the query
http://localhost:8983/solr/core1/select/?q=google&shards=localhost:8983/solr/core2,localhost:8983/solr/core3
ETag should be calculated off of core2 and core3, instead it's being calculated from the index of core1.
This results in index modificaitons to to core2 or core3 being "invisible" to clients which query this URL using "If-None-Match" or "If-Modified-Since" type requests
was:
When searching across multiple shards with HTTP caching enabled, the ETag value in the response is only using the searcher in the original request, not the shards. For example, take the query
http://localhost:8983/solr/core1/select/?q=google&shards=localhost:8983/solr/core2,localhost:8983/solr/core3
ETag should be calculated off of core2 and core3, instead it's being calculated from core1.
Summary: HTTP Caching related headers are incorrect for distributed searches (was: ETag calculation is incorrect for distributed searches)
> HTTP Caching related headers are incorrect for distributed searches
> -------------------------------------------------------------------
>
> Key: SOLR-1765
> URL: https://issues.apache.org/jira/browse/SOLR-1765
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.4
> Reporter: Charlie Jackson
> Priority: Minor
>
> When searching across multiple shards with HTTP caching enabled, the Caching related headers (ETag, Cache-Control, Last-Modified) in the response are based on the "index" of the coordinating solr core, and are not influenced by the properties of the shards. For example, take the query
> http://localhost:8983/solr/core1/select/?q=google&shards=localhost:8983/solr/core2,localhost:8983/solr/core3
> ETag should be calculated off of core2 and core3, instead it's being calculated from the index of core1.
> This results in index modificaitons to to core2 or core3 being "invisible" to clients which query this URL using "If-None-Match" or "If-Modified-Since" type requests
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.