[jira] Commented: (SOLR-324) solr can't perform sort by long field

[ https://issues.apache.org/jira/browse/SOLR-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559103#action_12559103 ] Otis Gospodnetic commented on SOLR-324: --- Grant, should this issue be closed? See

[jira] Commented: (SOLR-324) solr can't perform sort by long field

[ https://issues.apache.org/jira/browse/SOLR-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559111#action_12559111 ] Grant Ingersoll commented on SOLR-324: -- No, Solr needs to be able to leverage what is in

[jira] Commented: (SOLR-324) solr can't perform sort by long field

[ https://issues.apache.org/jira/browse/SOLR-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559123#action_12559123 ] Otis Gospodnetic commented on SOLR-324: --- Ah, this is in Solr-land, sorry, thought it

[jira] Commented: (SOLR-455) Better handling when index runs out of disk space

[ https://issues.apache.org/jira/browse/SOLR-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559161#action_12559161 ] Otis Gospodnetic commented on SOLR-455: --- My guess would be that this is really out of

[jira] Commented: (SOLR-455) Better handling when index runs out of disk space

[ https://issues.apache.org/jira/browse/SOLR-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559199#action_12559199 ] Hoss Man commented on SOLR-455: --- preventing corruption would definitely be on the Lucene-Java

[jira] Commented: (SOLR-356) pluggable functions (value sources)

[ https://issues.apache.org/jira/browse/SOLR-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559206#action_12559206 ] Hoss Man commented on SOLR-356: --- bq. Maybe I'm missing something from the recommendation

solrj patch to COMMIT with xml

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.

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 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

RE: solrj patch to COMMIT with xml

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 indexing so the commit is included with the add connction. Sample indexing code: UpdateResponse addResponse = client.add(

Having multiple (Solr)IndexSearchers per index

Hi, Summary: How about having more than 1 (Solr)IndexSearcher per index in order to avoid Lucene's synchronization bottlenecks? There are those few synchronized points in Lucene - the stuff around IndexInput and such. One in a while I hear from people who've done extensive benchmarking or

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 this extensivly with resin and jetty, but have not touched tomcat... To add and commit in one shot, try: UpdateRequest up = new

RE: solrj patch to COMMIT with xml

My problem is that the in the BaseSolrServer the add(Collection, Boolean) call does the req.process call inside of it.. so I can't add a setAction to the updateRequest before it processes. And the add method also creates a *new* update request inside of it, so I can't set the action beforehand

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. For anything custom or advanced, you

[jira] Commented: (SOLR-303) Distributed Search over HTTP

[ https://issues.apache.org/jira/browse/SOLR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559259#action_12559259 ] Dima Brodsky commented on SOLR-303: --- Hey, Quick question from a solr newbie. I'd love to

[jira] Created: (SOLR-457) A multi threaded implementation for solrJ

A multi threaded implementation for solrJ - Key: SOLR-457 URL: https://issues.apache.org/jira/browse/SOLR-457 Project: Solr Issue Type: New Feature Components: clients - java Affects

[jira] Updated: (SOLR-457) A multi threaded implementation for solrJ

[ https://issues.apache.org/jira/browse/SOLR-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] patrick o'leary updated SOLR-457: - Attachment: multithreaded-solrj.patch Provides a multi-threaded implementation of

[jira] Updated: (SOLR-303) Distributed Search over HTTP

[ https://issues.apache.org/jira/browse/SOLR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] patrick o'leary updated SOLR-303: - Attachment: distributed_pjaol.patch Hey Yonik Needed to make a couple of updates to ShardDoc as

RE: solrj patch to COMMIT with xml

Ok, I reverted and ran some index(docs).. My solr logs say: Jan 15, 2008 3:09:11 PM org.apache.solr.update.SolrIndexWriter getDirectory WARNING: No lockType configured for /m2/tomcat5.5-temp/solr_data/en/index assuming 'simple' Jan 15, 2008 3:09:11 PM

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 you call: client.commit()? It seems to me that if a user does option 1: client.add(docs) they