Strange search result (or lack of)

Hi, I have the following field defined in my schema: The field contains the value "Das Urteil" which is thus stored as "das urteil" The following query (using Solr 1.4) returns nothing name_de:das urteil But when I run the query name_de:"das urteil" t

Term is duplicated when updating a document

Hi, we are updating our documents (that represent products in our shop) when a dealer modifies them, by calling SolrServer.add(SolrInputDocument) with the updated document. My understanding is, that there is no other way of updating an existing document. However we also use a term query to a

Re: Term is duplicated when updating a document

. Regards Thomas This may be a bug if you did not change the field or the schema file but the terms count is changing. On Fri, Oct 15, 2010 at 9:14 AM, Thomas Kellerer wrote: Hi, we are updating our documents (that represent products in our shop) when a dealer modifies them, by calling

Re: Term is duplicated when updating a document

rebuild to rule out things like that. Then after startup, did a search, then updated the document and did a search again. Regards Thomas This may be a bug if you did not change the field or the schema file but the terms count is changing. On Fri, Oct 15, 2010 at 9:14 AM, Thomas Kellerer wr

Problem with replication

Hi all, we have implemented a Solr based search in our web application. We have one master server that maintains the index which is replicated to the slaves using the built-in Solr replication. This has been working fine so far, but suddenly the replication does not send the modified files to

Re: Problem with replication

Here is our configuration: true commit startup stopwords.txt,stopwords_de.txt,stopwords_en.txt,synonyms.txt Stevo Slavić, 20.01.2011 13:26: On which events did you configure master to perform replication? replicateAfter Regards, Stevo. On Thu, Jan 20, 2011 at 12:53 PM, Thomas

Re: Problem with replication

Thomas Kellerer, 20.01.2011 12:53: Hi all, we have implemented a Solr based search in our web application. We have one master server that maintains the index which is replicated to the slaves using the built-in Solr replication. This has been working fine so far, but suddenly the replication

Re: Problem with replication

Stevo Slavić, 20.01.2011 15:42: So if on startup index gets replicated, then commit probably isn't being called anywhere on master. No, the index is not replicated on startup (same behaviour: "no files to download") Is that index configured to autocommit on master, or do you commit from appl

Re: Problem with replication

ommit a change to index to master, then bring slave up, and wait for pollInterval to pass and replication to occur. Regards, Stevo. On Thu, Jan 20, 2011 at 4:16 PM, Thomas Kellerer wrote: Stevo Slavić, 20.01.2011 15:42: So if on startup index gets replicated, then commit probably isn't be