?
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 following command (productId is my document primary key):
When I call client.commit() (with the svn trunk head) I see nothing in
the solr logs (I think because there is no data in the post?). The solr
server seems to ignore the commit=true parameter completely.
My solr server is running a build from svn from a couple days ago, I'm
sure I'm on 1.3.. is
: 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
Hey guys,
I'm not sure why, but the solrj client relies on commit=true on the
querystring for committing an index() call. But with the latest svn
trunk, my index() calls were not committing. I made a patch to add a
COMMIT/ element to the posted xml so I could index using the solrj
client.
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 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
();
up.add( docs );
up.setAction( ACTION.COMMIT, true, false );
up.process( client );
ryan
Keene, David wrote:
Nope, I'm using 1.3 (synced 2 days ago). I'm indexing using using
code
similar to below, and it creates 2 connections when doing so. Perhaps
there is a better way to do my
.
For anything custom or advanced, you will need option 2.
-
I'm still wondering what your logs say when you try to send a commit
(with the unmodified code)
ryan
Keene, David wrote:
My problem is that the in the BaseSolrServer the add(Collection,
Boolean) call does the req.process call
