[
https://issues.apache.org/jira/browse/SOLR-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559349#action_12559349
]
patrick o'leary commented on SOLR-457:
--
In terms of reusing threads I used Executors.new
[
https://issues.apache.org/jira/browse/SOLR-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559340#action_12559340
]
Sean Timm commented on SOLR-457:
Currently with Solrj, if you want to take advantage of the c
[
https://issues.apache.org/jira/browse/SOLR-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559308#action_12559308
]
patrick o'leary commented on SOLR-457:
--
Not too concerned about which package it's in.
On 15-Jan-08, at 1:07 PM, Otis Gospodnetic wrote:
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
[
https://issues.apache.org/jira/browse/SOLR-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559282#action_12559282
]
Ryan McKinley commented on SOLR-457:
Is this something that is only used in the distribut
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
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
org.apache.solr.update.processor.LogUpdatePro
[
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 the
[
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 CommonsHttpSolrSe
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 Vers
[
https://issues.apache.org/jira/browse/SOLR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559259#action_12559259
]
Dima Brodsky commented on SOLR-303:
---
Hey,
Quick question from a solr newbie. I'd love to
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 will
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 eit
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 Upda
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 run
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( d
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 for
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
element to the posted xml so I could index using the solrj
client.
Did I
[
https://issues.apache.org/jira/browse/SOLR-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559206#action_12559206
]
Hoss Man commented on SOLR-356:
---
bq. Maybe I'm missing something from the recommendation though
[
https://issues.apache.org/jira/browse/SOLR-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559199#action_12559199
]
Hoss Man commented on SOLR-455:
---
preventing corruption would definitely be on the Lucene-Java s
[
https://issues.apache.org/jira/browse/SOLR-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559161#action_12559161
]
Otis Gospodnetic commented on SOLR-455:
---
My guess would be that this is really out of s
[
https://issues.apache.org/jira/browse/SOLR-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559123#action_12559123
]
Otis Gospodnetic commented on SOLR-324:
---
Ah, this is in Solr-land, sorry, thought it wa
[
https://issues.apache.org/jira/browse/SOLR-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559111#action_12559111
]
Grant Ingersoll commented on SOLR-324:
--
No, Solr needs to be able to leverage what is in
[
https://issues.apache.org/jira/browse/SOLR-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559103#action_12559103
]
Otis Gospodnetic commented on SOLR-324:
---
Grant, should this issue be closed? See LUCEN
[
https://issues.apache.org/jira/browse/SOLR-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559082#action_12559082
]
holograph edited comment on SOLR-453 at 1/15/08 7:36 AM:
---
Sorry for
[
https://issues.apache.org/jira/browse/SOLR-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559082#action_12559082
]
Tomer Gabel commented on SOLR-453:
--
Sorry for the delay, but I wanted to check this properly
[
https://issues.apache.org/jira/browse/SOLR-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559075#action_12559075
]
Doug Daniels commented on SOLR-356:
---
I found that thread at [http://marc.info/?l=lucene-dev
See http://lucene.zones.apache.org:8080/hudson/job/Solr-Nightly/320/changes
init-forrest-entities:
[mkdir] Created dir: /tmp/apache-solr-nightly/build
compile-common:
[mkdir] Created dir: /tmp/apache-solr-nightly/build/common
[javac] Compiling 31 source files to /tmp/apache-solr-nightly/build/common
[javac] Note: Some input files use unchecked or unsafe o
29 matches
Mail list logo
