Did adding a request handler to /update fix your issue?
I added some docs to:
http://wiki.apache.org/solr/Solrj
And a warning message to the deprecated SolrUpdateServlet:
http://svn.apache.org/viewvc?view=revrevision=612896
ryan
Keene, David wrote:
Running under tomcat 5.5.23
Sending the
Yes, that did it. I'm sorry about the trouble!
-Original Message-
From: Ryan McKinley [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 17, 2008 10:01 AM
To: solr-dev@lucene.apache.org
Subject: Re: solrj patch to COMMIT with xml
Did adding a request handler to /update fix your issue
INFO: {add=[QAQA12-QAQA1_CN-0001]} 0 5
-Original Message-
From: Ryan McKinley [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 15, 2008 3:22 PM
To: solr-dev@lucene.apache.org
Subject: Re: solrj patch to COMMIT with xml
, January 15, 2008 3:22 PM
To: solr-dev@lucene.apache.org
Subject: Re: solrj patch to COMMIT with xml
org.apache.solr.update.processor.LogUpdateProcessor finish
INFO: {add=[QAQA12-QAQA1_CN-0001]} 0 7
That is what you get when you call:
client.add( docs )
but what do you see when
: Ryan McKinley [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 16, 2008 10:45 AM
To: solr-dev@lucene.apache.org
Subject: Re: solrj patch to COMMIT with xml
what servlet container?
what happens when you call the URL directly (without solrj)? It should
log *something*
ryan
Keene, David wrote
: Wednesday, January 16, 2008 10:45 AM
To: solr-dev@lucene.apache.org
Subject: Re: solrj patch to COMMIT with xml
what servlet container?
what happens when you call the URL directly (without solrj)? It
should
log *something*
ryan
Keene, David wrote:
When I call client.commit() (with the svn
Are you hitting a 1.2 solr index? Using ?commit=true assumes you are
hitting a 1.3 index...
The reason for it is so you can optionally add docs and commit in one call.
ryan
Keene, David wrote:
Hey guys,
I'm not sure why, but the solrj client relies on commit=true on the
querystring
( docs );
UpdateResponse commitResponse = client.commit();
Is there a way to make the client.add(docs) connection add a commit?
-Original Message-
From: Ryan McKinley [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 15, 2008 12:54 PM
To: solr-dev@lucene.apache.org
Subject: Re: solrj patch
: Ryan McKinley [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 15, 2008 12:54 PM
To: solr-dev@lucene.apache.org
Subject: Re: solrj patch to COMMIT with xml
Are you hitting a 1.2 solr index? Using ?commit=true assumes you are
hitting a 1.3 index...
The reason for it is so you can optionally add
);
return req.process(this);
}
So there is no way to get at the action of that request.
-Original Message-
From: Ryan McKinley [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 15, 2008 1:19 PM
To: solr-dev@lucene.apache.org
Subject: Re: solrj patch to COMMIT with xml
hymm - with 1.3
:[EMAIL PROTECTED]
Sent: Tuesday, January 15, 2008 1:19 PM
To: solr-dev@lucene.apache.org
Subject: Re: solrj patch to COMMIT with xml
hymm - with 1.3, the standard solrj should work without issue. What do
the logs say when you call commit? What container are you running?I
have tested
Subject: Re: solrj patch to COMMIT with xml
right - there are two ways to work with solrj
1. use the standard functions available in SolrServer
2. make your own SolrRequest and call 'process'
http://wiki.apache.org/solr/Solrj
Calling client.add( docs ) is option 1, the example I sent is option 2
org.apache.solr.update.processor.LogUpdateProcessor finish
INFO: {add=[QAQA12-QAQA1_CN-0001]} 0 7
That is what you get when you call:
client.add( docs )
but what do you see when you call:
client.commit()?
It seems to me that if a user does option 1: client.add(docs) they
13 matches
Mail list logo
