: I tried your suggestion, Hoss, but committing to the new coordinator
: core doesn't change the indexVersion and therefore the ETag value isn't
: changed.
Hmmm... so the "empty" commit doesn't change the indexVersion? ... i
didn't realize that.
Well, I suppose you could replace your empty comm
rom: Chris Hostetter [mailto:hossman_luc...@fucit.org]
Sent: Thursday, February 04, 2010 2:16 PM
To: solr-user@lucene.apache.org
Subject: Re: HTTP caching and distributed search
: >
http://localhost:8080/solr/core1/select/?q=google&start=0&rows=10&shards
: > =localhost:8080/solr/cor
: > http://localhost:8080/solr/core1/select/?q=google&start=0&rows=10&shards
: > =localhost:8080/solr/core1,localhost:8080/solr/core2
: You are right, etag is calculated using the searcher on core1 only and it
: does not take other shards into account. Can you open a Jira issue?
...as a possible
On Wed, Feb 3, 2010 at 12:21 AM, Charlie Jackson wrote:
> Currently, I've got a Solr setup in which we're distributing searches
> across two cores on a machine, say core1 and core2. I'm toying with the
> notion of enabling Solr's HTTP caching on our system, but I noticed an
> oddity when using it
