Erick,
Thanks a lot for the detailed explanation. That clarified things for me
better.
On Sun, Mar 2, 2014 at 10:04 AM, Erick Erickson wrote:
> Well, in M/S setups the master shouldn't be searching at all,
> but that's a nit.
>
> That aside, whether the master has opened a new or
> searcher or n
Well, in M/S setups the master shouldn't be searching at all,
but that's a nit.
That aside, whether the master has opened a new or
searcher or not is irrelevant to what the slave replicates.
What _is_ relevant is whether any of the files on disk that
comprise the index (i.e. the segment files) hav
> The slave is polling the master after the interval specified in
solrconfig.xml. The slave essentially asks "has anything changed?" If so, the
changes are brought down to the slave.
Yes, I understand this, but if master does not open a new searcher after
auto commits (which would indicate that the
bq: the slave anyway replicates the index after auto commits! (Is this
desired behavior?)
Absolutely it's desired behavior. The slave is polling the master
after the interval
specified in solrconfig.xml. The slave essentially asks "has anything
changed?" If so,
the changes are brought down to the
I believe I figured out what the issue is. Even though we do not open a new
searcher on master during full import, the slave anyway replicates the
index after auto commits! (Is this desired behavior?) Since "clean=true"
this meant all the docs were deleted on slave and a partial index got
replicate
Well, I'd certainly try removing parts of the query to see
what was actually in the index.
I don't see anything obvious though...
Erick
On Fri, Feb 28, 2014 at 8:06 PM, Arun Rangarajan
wrote:
> Thx, Erick and Chris.
>
> This is indeed very strange. Other queries which do not restrict by the
>
Thx, Erick and Chris.
This is indeed very strange. Other queries which do not restrict by the
date field are returning results, so the index is definitely not empty. Has
it got something to do with the date query part, with NOW/DAY or something
in here?
first_publish_date:[NOW/DAY-33DAYS TO NOW/DA
: This is odd. The full import, I think, deletes the
: docs in the index when it starts.
Yeah, if you are doing a full-import everyday, and you don't want it to
delete all docs when it starts, you need to specify "clearn=false"
https://cwiki.apache.org/confluence/display/solr/Uploading+Structur
gt; > Or, maybe you actually wanted this:
> >
> > first_publish_date:[NOW/DAY-33DAYS TO NOW/DAY-3DAYS] -tag_id:268702
> >
> > -- Jack Krupansky
> >
> > -Original Message- From: Arun Rangarajan
> > Sent: Friday, February 28, 2014 11:15 AM
> > To
AND (*:* -tag_id:268702)
>
> Or, maybe you actually wanted this:
>
> first_publish_date:[NOW/DAY-33DAYS TO NOW/DAY-3DAYS] -tag_id:268702
>
> -- Jack Krupansky
>
> -Original Message- From: Arun Rangarajan
> Sent: Friday, February 28, 2014 11:15 AM
> To: solr-user@lucene.apache.
: Arun Rangarajan
Sent: Friday, February 28, 2014 11:15 AM
To: solr-user@lucene.apache.org
Subject: Date query not returning results only some time
Solr server version 4.2.1
I am facing a strange issue with a date query like this:
q=first_publish_date:[NOW/DAY-33DAYS TO NOW/DAY-3DAYS] AND
-tag_id
Solr server version 4.2.1
I am facing a strange issue with a date query like this:
q=first_publish_date:[NOW/DAY-33DAYS TO NOW/DAY-3DAYS] AND
-tag_id:268702&fq=(burial_score:[* TO 0.49] AND
-tag_id:286006)&rows=1&sort=random_906313237 asc&fl=id
The only process by which we add documents to the c
12 matches
Mail list logo
