firstly at shard_A and ignores it at shard_B. That means, that the
doc maybe would occur at page 10 in pagination, although it *should* occur
at page 1 or 2.
Kind regards,
- Mitch
--
View this message in context:
http://lucene.472066.n3.nabble.com/a-bug-of-solr-distributed-search
Hi. All.
Is there anyway to have time out support in distributed search. I searched
https://issues.apache.org/jira/browse/SOLR-502 but looks it is not in main
release of solr1.4
I have 70 cores, when I search, some response in 0-700ms. Some return in
about 2s. Some need very long time, more
On Jul 4, 2010, at 5:10 PM, Andrew Clegg wrote:
Mark Miller-3 wrote:
On 7/4/10 12:49 PM, Andrew Clegg wrote:
I thought so but thanks for clarifying. Maybe a wording change on
the
wiki
Sounds like a good idea - go ahead and make the change if you'd like.
That page seems to be marked
Hi,
I'm after a bit of clarification about the 'limitations' section of the
distributed search page on the wiki.
The first two limitations say:
* Documents must have a unique key and the unique key must be stored
(stored=true in schema.xml)
* When duplicate doc IDs are received, Solr chooses
On 7/4/10 11:41 AM, Andrew Clegg wrote:
Hi,
I'm after a bit of clarification about the 'limitations' section of the
distributed search page on the wiki.
The first two limitations say:
* Documents must have a unique key and the unique key must be stored
(stored=true in schema.xml
On 7/4/10 12:49 PM, Andrew Clegg wrote:
Mark Miller-3 wrote:
The 'doc ID' in the second point refers to the unique key in the first
point.
I thought so but thanks for clarifying. Maybe a wording change on the wiki
would be good?
Cheers,
Andrew.
Sounds like a good idea - go
:
http://lucene.472066.n3.nabble.com/Duplicate-items-in-distributed-search-tp942408p942984.html
Sent from the Solr - User mailing list archive at Nabble.com.
when use distributed search + dismax
Hi. All.
I was using distributed search over 30 solr instance, the
previous one
was using the standard query handler. And the result was
returned correctly.
each result has 2 fields. ID and type.
Today I want to use search withk dismax, I tried
was using distributed search over 30 solr instance, the previous one
was using the standard query handler. And the result was returned
correctly.
each result has 2 fields. ID and type.
Today I want to use search withk dismax, I tried search with each
instance with dismax. It works
Hi. All.
I found more about fields missing things.
I tried the default distributed search example which configured 2 instances,
one on 8983 and another on 7574.
When I try search with standard query handler, the result fields are all
right.
When I search with the deafult dismax, some fields
-user@lucene.apache.org
Sent: Tue, June 22, 2010 11:04:07 AM
Subject: Field missing when use distributed search + dismax
Hi. All.
I was using distributed search over 30 solr instance, the
previous one
was using the standard query handler. And the result was
returned correctly.
each result
Hi. All.
I was using distributed search over 30 solr instance, the previous one
was using the standard query handler. And the result was returned correctly.
each result has 2 fields. ID and type.
Today I want to use search withk dismax, I tried search with each
instance with dismax. It works
Hi. All.
I tried with the default solr example plus my own config/schema file. I
post test document into solr manually. Then test the distributed search and
it works. Then I switch to my existing l*ucene index, and it d*oesn't work.
So I am wondering is that the reason, when solr use lucene
Hi. All.
I am still testing. I think I am approaching the truth. Now confirmed:
the doc in my existing lucene indexes, when search with distributed search,
none of them are returned. But the docs inserted from solr post.jar are
returned successfully.
Don't know why. looks the lucene docs
did you send a commit after the last doc posted to solr?
-Ursprüngliche Nachricht-
Von: Scott Zhang [mailto:macromars...@gmail.com]
Gesendet: Dienstag, 8. Juni 2010 08:30
An: solr-user@lucene.apache.org
Betreff: Re: Distributed Search doesn't response the result set
Hi. All
.
When I created the index, I set id field as Stored but not indexed
because I don't see the reason to index the id.
Then in schema.xml, I found I have to set ID as indexed but actually it
is not.
Not sure how solr is implemented internally. But without set id as
indexed, the distributed search
...@gmail.com
Hi. All.
I am trying to use solr to search over 2 lucene indexes. I am following
the solr tutorial and test the distributed search example. It works.
Then I am using my own lucene indexes. Search in each solr instance works
and return the expected result. But when I do distributed
and test the distributed search example. It works.
Then I am using my own lucene indexes. Search in each solr instance
works
and return the expected result. But when I do distributed search using
shards. It only return the numFound=14. But the result contain
nothing.
Don't know why. Can
Scott Zhang macromars...@gmail.com
Hi. All.
I am trying to use solr to search over 2 lucene indexes. I am
following
the solr tutorial and test the distributed search example. It works.
Then I am using my own lucene indexes. Search in each solr instance
works
and return
Europa, 26. Ática 5. 3ª Planta
28224 Pozuelo de Alarcón
Tel.: 91 352 59 42
2010/6/7 Scott Zhang macromars...@gmail.com
Hi. All.
I am trying to use solr to search over 2 lucene indexes. I am
following
the solr tutorial and test the distributed search example
59 42
2010/6/7 Scott Zhang macromars...@gmail.com
Hi. All.
I am trying to use solr to search over 2 lucene indexes. I am
following
the solr tutorial and test the distributed search example. It works.
Then I am using my own lucene indexes. Search in each solr
Sent: Thu, April 15, 2010 1:30:22 PM
Subject: bug using distributed search, highlighting and q.alt
I have noticed when using q.alt even if hl=true highlights are not
returned.
When using distributed search, q.alt and hl,
HighlightComponent.java
finishStage expects the highlighting NamedList
I have noticed when using q.alt even if hl=true highlights are not returned.
When using distributed search, q.alt and hl, HighlightComponent.java
finishStage expects the highlighting NamedList of each shard (if hl=true)
but it will never be returned. It will end up with a NullPointerExcepion.
I
I have noticed when using q.alt even if hl=true highlights are not returned.
When using distributed search, q.alt and hl, HighlightComponent.java
finishStage expects the highlighting NamedList of each shard (if hl=true)
but it will never be returned. It will end up with a NullPointerExcepion.
I
On 03/09/2010 04:28 PM, Shawn Heisey wrote:
I attended the Webinar on March 4th. Many thanks to Yonik for
putting that on. That has led to some questions about the best way
to bring fault tolerance to our distributed search. High level
question: Should I go with SolrCloud, or stick
way to bring
fault tolerance to our distributed search. High level question:
Should I go with SolrCloud, or stick with 1.4 and use load balancing?
I hope the rest of this email isn't too disjointed for understanding.
We are using virtual machines on 8-core servers with 32GB of RAM to
house all
that on. That has led to some questions about the best way to bring
fault tolerance to our distributed search. High level question:
Should I go with SolrCloud, or stick with 1.4 and use load balancing?
I hope the rest of this email isn't too disjointed for understanding.
Now I got it, just forgot put qt=search in query.
By the way, in solr 1.3, I used shards.txt under conf directory and
distributed=true in query for distributed search. In that way,in my
java application, I can hard code solr query with distributed=true and
control the using of distributed
you can set a default shard parameter on the request handler doing
distributed search, you can set up two different request handlers one
with shards default and one without
On Thu, Feb 25, 2010 at 1:35 PM, Jeffrey Zhao
jeffrey.z...@metalogic-inc.com wrote:
Now I got it, just forgot put qt=search
How do define a new search handler with a shards parameter? I defined as
following way but it doesn't work. If I put the shards parameter in
default handler, it seems I got an infinite loop.
requestHandler name=standard class=solr.SearchHandler default=true
!-- default values for query
On 02/25/2010 03:32 PM, Jeffrey Zhao wrote:
How do define a new search handler with a shards parameter? I defined as
following way but it doesn't work. If I put the shards parameter in
default handler, it seems I got an infinite loop.
requestHandler name=standard class=solr.SearchHandler
PM
Subject:Re: Solr 1.4 distributed search configuration
On 02/25/2010 03:32 PM, Jeffrey Zhao wrote:
How do define a new search handler with a shards parameter? I defined
as
following way but it doesn't work. If I put the shards parameter in
default handler, it seems I got
strspellcheck/str
strdebug/str
/arr
/requestHandler
From: Mark Millermarkrmil...@gmail.com
To: solr-user@lucene.apache.org
Date: 25/02/2010 03:41 PM
Subject:Re: Solr 1.4 distributed search configuration
On 02/25/2010 03:32 PM, Jeffrey Zhao wrote:
How
/httpclient-3.x/
We used 'balance' at another project and did not have any problems.
On Tue, Feb 9, 2010 at 5:54 AM, Ian Connor ian.con...@gmail.com wrote:
I have been using distributed search with haproxy but noticed that I am
suffering a little from tcp connections building up waiting for the OS
the Apache Commons HTTP client library:
http://hc.apache.org/httpclient-3.x/
We used 'balance' at another project and did not have any problems.
On Tue, Feb 9, 2010 at 5:54 AM, Ian Connor ian.con...@gmail.com
wrote:
I have been using distributed search with haproxy but noticed that I
am
://hc.apache.org/httpclient-3.x/
We used 'balance' at another project and did not have any problems.
On Tue, Feb 9, 2010 at 5:54 AM, Ian Connor ian.con...@gmail.com wrote:
I have been using distributed search with haproxy but noticed that I am
suffering a little from tcp connections building
: I tried your suggestion, Hoss, but committing to the new coordinator
: core doesn't change the indexVersion and therefore the ETag value isn't
: changed.
Hmmm... so the empty commit doesn't change the indexVersion? ... i
didn't realize that.
Well, I suppose you could replace your empty
I have been using distributed search with haproxy but noticed that I am
suffering a little from tcp connections building up waiting for the OS level
closing/time out:
netstat -a
...
tcp6 1 0 10.0.16.170%34654:53789 10.0.16.181%363574:8893
CLOSE_WAIT
tcp6 1 0 10.0.16.170
Hostetter [mailto:hossman_luc...@fucit.org]
Sent: Thursday, February 04, 2010 2:16 PM
To: solr-user@lucene.apache.org
Subject: Re: HTTP caching and distributed search
:
http://localhost:8080/solr/core1/select/?q=googlestart=0rows=10shards
: =localhost:8080/solr/core1,localhost:8080/solr/core2
: You
This goes through the Apache Commons HTTP client library:
http://hc.apache.org/httpclient-3.x/
We used 'balance' at another project and did not have any problems.
On Tue, Feb 9, 2010 at 5:54 AM, Ian Connor ian.con...@gmail.com wrote:
I have been using distributed search with haproxy but noticed
will invalidate the cache, as it should. But
committing to core2 doesn't, so I get the cached version back, even
though core2 has changed and the cache is stale. I'm guessing this is
because the request is going against core1, hence using core1's cache
values, but in a distributed search, it seems like
: http://localhost:8080/solr/core1/select/?q=googlestart=0rows=10shards
: =localhost:8080/solr/core1,localhost:8080/solr/core2
: You are right, etag is calculated using the searcher on core1 only and it
: does not take other shards into account. Can you open a Jira issue?
...as a possible
My only suggestion is to put haproxy in front of two replicas and then have
haproxy do the failover. If a shard fails, the whole search will fail unless
you do something like this.
On Fri, Jan 29, 2010 at 3:31 PM, Joe Calderon calderon@gmail.comwrote:
hello *, in distributed search when
On Fri, Jan 29, 2010 at 3:31 PM, Joe Calderon calderon@gmail.com wrote:
hello *, in distributed search when a shard goes down, an error is
returned and the search fails, is there a way to avoid the error and
return the results from the shards that are still up?
The SolrCloud branch has
a shard has failed
On Wed, Feb 3, 2010 at 10:55 AM, Yonik Seeley
yo...@lucidimagination.com wrote:
On Fri, Jan 29, 2010 at 3:31 PM, Joe Calderon calderon@gmail.com wrote:
hello *, in distributed search when a shard goes down, an error is
returned and the search fails, is there a way to avoid
back, even
though core2 has changed and the cache is stale. I'm guessing this is
because the request is going against core1, hence using core1's cache
values, but in a distributed search, it seems like it should be using
cache values from all cores in the shards parameter. Is this a known
issue
hello *, in distributed search when a shard goes down, an error is
returned and the search fails, is there a way to avoid the error and
return the results from the shards that are still up?
thx much
--joe
Hi Yonik!
I've tried recreating the problem now to get some log-output and the problem
just doesn't seem to be there anymore... This puzzles me abit, as the
problem WAS definitely there before.
I've done one change and that is to optimize the index on one of the
servers. But should that impact
Hi everyone! I've posted a similar question earlier, but in a thread related
to facets in general, so I thought I'd repost it here as a separate thread.
I have a faceted search that is very fast when I executed the query on a
single solr server, but is significantly slower when executed in a
Something looks wrong... that type of slowdown is certainly not expected.
You should be able to see both the main query and a sub-query in the
logs... could you post an actual example?
-Yonik
http://www.lucidimagination.com
On Mon, Jan 4, 2010 at 4:15 AM, Aleksander Stensby
DS requires a bunch of shard names in the url. That's all. Note that a
ds does not use the data of the solr you call.
You can create an entry point for your distributed search by adding a
new requestHandler element in solrconfig.xml. You would add the
shard list parameter to the defaults list. Do
I've been looking through all the documentation. I've set up a single solr
instance, and one multicore instance. If someone would be willing to share
some configuration examples and/or advise for setting up solr for distributing
the search, I would really appreciate it. I've read that there
RJ,
You may want to take a simpler step - single Solr core (no solr.xml needed) per
machine. Then distributed search really only requires that you specify shard
URLs in the URL of the search requests. In practice/production you rarely
benefit from distributed search against multiple cores
-
From: Otis Gospodnetic [mailto:otis_gospodne...@yahoo.com]
Sent: Tuesday, November 10, 2009 6:02 PM
To: solr-user@lucene.apache.org
Subject: Re: Request assistance with distributed search multi shard/core setup
and configuration
RJ,
You may want to take a simpler step - single Solr core
@lucene.apache.org solr-user@lucene.apache.org
Sent: Tue, November 10, 2009 6:05:19 PM
Subject: RE: Request assistance with distributed search multi shard/core
setup and configuration
I've already done the single Solr, that's why my request. I read on some
site
that there is a way to setup
]
Sent: Tuesday, November 10, 2009 6:09 PM
To: solr-user@lucene.apache.org
Subject: Re: Request assistance with distributed search multi shard/core setup
and configuration
Right, that's http://wiki.apache.org/solr/DistributedSearch
Otis
--
Sematext is hiring -- http://sematext.com/about/jobs.html
Hm, I don't follow. You don't need to create a custom (request) handler to
make use of Solr's distributed search.
Otis
--
Sematext is hiring -- http://sematext.com/about/jobs.html?mls
Lucene, Solr, Nutch, Katta, Hadoop, HBase, UIMA, NLP, NER, IR
- Original Message
From: Turner
Hi All,
I am trying to get spell check suggestions in my distributed search query
using shards. I have 2 cores configured core0 and core1 both having spell
check component configured. On requesting search result using the following
query I don't get the spelling suggestions.
http://localhost
On Wed, Oct 7, 2009 at 2:14 PM, balaji.a reachbalaj...@gmail.com wrote:
Hi All,
I am trying to get spell check suggestions in my distributed search query
using shards.
SpellCheckComponent does not support distributed search yet. There is an
issue open with a patch. If you decide to use
-components
strspellcheck/str
/arr
/requestHandler
Shalin Shekhar Mangar wrote:
On Wed, Oct 7, 2009 at 2:14 PM, balaji.a reachbalaj...@gmail.com wrote:
Hi All,
I am trying to get spell check suggestions in my distributed search
query
using shards.
SpellCheckComponent does
wrote:
Hi All,
I am trying to get spell check suggestions in my distributed search
query
using shards.
SpellCheckComponent does not support distributed search yet. There is an
issue open with a patch. If you decide to use, do let us know your
feedback:
https://issues.apache.org/jira
On Thu, Aug 27, 2009 at 9:57 PM, GiriGG giri...@gmail.com wrote:
Hi All,
I need to build a Search system using Solr. I need to keep data of 30 days
which will be around 400GB.
I will be using Distributed Search with Master/Slaves (Data will be
published to each shard on round robin basis
Hi All,
I need to build a Search system using Solr. I need to keep data of 30 days
which will be around 400GB.
I will be using Distributed Search with Master/Slaves (Data will be
published to each shard on round robin basis). My challenge is I need to
delete older than 30 days data (around 12GB
the query for individual node, the facet works great. If I
run distributed search in two machine without facet, it also works. The
following is the error from two machine:
Is there some setting different in 1.3 and 1.4
Error in first machine:
INFO: [] webapp=/solr path=/select
params={facet=truefl
the query for individual node, the facet works great. If I
run distributed search in two machine without facet, it also works. The
following is the error from two machine:
Is there some setting different in 1.3 and 1.4
Error in first machine:
INFO: [] webapp=/solr path=/select
params={facet=truefl
On Jul 9, 2009, at 11:58 PM, Sumit Aggarwal wrote:
Hi,
1. Calls made to multiple shards are made in some concurrent fashion
or
serially?
Concurrent
2. Any idea of algorithm followed for merging data? I mean how
efficient it
is?
Not sure, but given that Yonik implemented it, I
Hi,
1. Calls made to multiple shards are made in some concurrent fashion or
serially?
2. Any idea of algorithm followed for merging data? I mean how efficient it
is?
3. Lucene provides payload concept. How can we make search using that in
solr. My application store payloads and use search using
In my project, I am trying to do a distributed search sorted by some field
using solr. The test code is
as follows:
SolrQuery query = new SolrQuery();
query.set(q, id:[1 TO *]);
query.setSortField(id,SolrQuery.ORDER.asc);
query.setParam(shards, localhost:8983/solr, localhost:7574/solr
Sorry, the error is as follows. I have read the solr wiki carefully and
google it, but I haven't founded
any related question or solution, any one can help me, thanks!
org.apache.solr.client.solrj.SolrServerException: Error executing query
at
On Wed, Jul 8, 2009 at 6:45 AM, shb suh...@gmail.com wrote:
Sorry, the error is as follows. I have read the solr wiki carefully and
google it, but I haven't founded
any related question or solution, any one can help me, thanks!
org.apache.solr.client.solrj.SolrServerException: Error
java.net.ConnectException: Connection refused
at
org.apache.solr.client.solrj.
impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:391)
The Connection refused error is caused becaused that the servers have been
stopped.
IAre you sure both servers are running properly? You can hit
Hi All,
I am trying to do a distributed search and getting the below error. Please
let me know if you know how to solve this issue.
18:20:28,200 ERROR [STDERR]
org.apache.solr.client.solrj.SolrServerException: Error executing query
18:20:28,200 ERROR [STDERR
Hi Mark,
i actually got this error coz i was using an old version of
java. now the problem is solved
Thanks anyways
Raakhi
On Tue, Jun 9, 2009 at 11:17 AM, Rakhi Khatwani rkhatw...@gmail.com wrote:
Hi Mark,
yea i would like to open a JIRA issue for it. how do i go
Thanks for bringing closure to this Raakhi.
- Mark
Rakhi Khatwani wrote:
Hi Mark,
i actually got this error coz i was using an old version of
java. now the problem is solved
Thanks anyways
Raakhi
On Tue, Jun 9, 2009 at 11:17 AM, Rakhi Khatwani rkhatw...@gmail.com wrote:
Hi,
I was executing a simple example which demonstrates DistributedSearch.
example provided in the following link:
http://wiki.apache.org/solr/DistributedSearch
however, when i startup the server in both port nos: 8983 and 7574, i get
the following exception:
SEVERE: Could not start
Hi Mark,
yea i would like to open a JIRA issue for it. how do i go about
that?
Regards,
Raakhi
On Mon, Jun 8, 2009 at 7:58 PM, Mark Miller markrmil...@gmail.com wrote:
That is a very odd cast exception to get. Do you want to open a JIRA issue
for this?
It looks like an odd
on client side and using
something like Multi-core (as discussed here
http://wiki.apache.org/solr/MultipleIndexes).
Date: Wed, 20 May 2009 13:47:20 -0400
Subject: RE: Creating a distributed search in a searchComponent
From: nicholas.bai...@rackspace.com
To: solr-user@lucene.apache.org
to
the StandardRequestHandler. Then hopefully I will be able to use this
component to build the shards parameter of the query and have the Handler
then treat the query as a distributed search. Anyone have any experience or
know if this is possible?
You can also add a ServletFilter before
of the query and have the Handler
then treat the query as a distributed search. Anyone have any experience or
know if this is possible?
You can also add a ServletFilter before SolrDispatchFilter and add the
parameters before Solr processes the query.
--
Regards,
Shalin Shekhar Mangar
: Creating a distributed search in a searchComponent
Hi,
I am wondering if it is possible to basically add the distributed portion of a
search query inside of a searchComponent.
I am hoping to build my own component and add it as a first-component to the
StandardRequestHandler. Then hopefully I
the shards parameter of the query and have the Handler then treat the
query as a distributed search. Anyone have any experience or know if this is
possible?
Thanks,
Nick
Hi,
Having all kinds of fun with distributed search using shards:-)
I have 30K documents indexed using DIH into an index. Another
index contain documents indexed using solr-cell. I am using shards
to search across both indexes.
I am trying to format the results returned from solr
of documents, size of a document, number of unique
terms, kind of queries, frequency of updates etc.
Is it good or bad to think about Distributed Search and dividing index in
earlier stage of development?
If your index can fit into a single box with acceptable response times
On Apr 15, 2009, at 11:18 AM, Fergus McMenemie wrote:
Hi,
Having all kinds of fun with distributed search using shards:-)
I have 30K documents indexed using DIH into an index. Another
index contain documents indexed using solr-cell. I am using shards
to search across both indexes.
I am
On Apr 15, 2009, at 11:18 AM, Fergus McMenemie wrote:
Hi,
Having all kinds of fun with distributed search using shards:-)
I have 30K documents indexed using DIH into an index. Another
index contain documents indexed using solr-cell. I am using shards
to search across both indexes.
I am
- Original Message
From: Fergus McMenemie fer...@twig.me.uk
To: solr-user@lucene.apache.org
Sent: Wednesday, April 15, 2009 11:18:21 AM
Subject: looking at the results of a distributed search using shards.
Hi,
Having all kinds of fun with distributed search using shards:-)
I have
Hi,
Can someone provide a practical advice of how large a Solr search index can
be? for a better performance for consumer facing media website?.
Is it good or bad to think about Distributed Search and dividing index in
earlier stage of development?
Thanks
Ram
--
View this message in context
On Fri, Apr 10, 2009 at 7:50 AM, vivek sar vivex...@gmail.com wrote:
Just an update. I changed the schema to store the unique id field, but
I still get the connection reset exception. I did notice that if there
is no data in the core then it returns the 0 result (no exception),
but if there
yes - it's all new indexes. I can search them individually, but adding
shards throws Connection Reset error. Is there any way I can debug
this or any other pointers?
-vivek
On Fri, Apr 10, 2009 at 4:49 AM, Shalin Shekhar Mangar
shalinman...@gmail.com wrote:
On Fri, Apr 10, 2009 at 7:50 AM,
Hi,
I've another thread on multi-core distributed search, but just
wanted to put a simple question here on distributed search to get some
response. I've a search query,
http://etsx19.co.com:8080/solr/20090409_9/select?q=usa -
returns with 10 result
now if I add shards parameter
(only indexed) - does it has to be stored for distributed search?
HTTP Status 500 - null java.lang.NullPointerException at
org.apache.solr.handler.component.QueryComponent.mergeIds(QueryComponent.java:432)
at
org.apache.solr.handler.component.QueryComponent.handleResponses(QueryComponent.java:276
(shardDoc.id.toString(), shardDoc);
looks like the doc unique id is returning null. I'm not sure how is it
possible as its a required field. Right my unique id is not stored
(only indexed) - does it has to be stored for distributed search?
HTTP Status 500 - null java.lang.NullPointerException
Hi,
I am trying distributed search and multicore but not able to fire a
query. I tried
http://localhost:8080/solr/select/?shards=localhost:8080/solr/core0,localhost:8080/solr/core1q=solr
I am getting following error: Missing solr core name in path.
Should I use particular core to fire
On Mon, Mar 9, 2009 at 2:32 PM, Gargate, Siddharth sgarg...@ptc.com wrote:
Hi,
I am trying distributed search and multicore but not able to fire a
query. I tried
http://localhost:8080/solr/select/?shards=localhost:8080/solr/core0,localhost:8080/solr/core1q=solr
I am getting following
Hi,
I have multi-core scenario where the schemas are different and I have to search
for these cores as per the use case. I am using distributed search approach
here for getting the search results for the query from these cores.
But there is an obstacle. I have used EmbbededSolrServer class
On Fri, Mar 6, 2009 at 11:04 AM, Sagar Khetkade
sagar.khetk...@hotmail.comwrote:
I have multi-core scenario where the schemas are different and I have to
search for these cores as per the use case. I am using distributed search
approach here for getting the search results for the query from
: Ok, so it wouldn't be possible to have a smaller, faster authoritative
: shard for near-real-time updates while keeping the entire dataset in a
: second shard which is updates less frequently?
I believe Otis's point is that many people use distributed search across
shards where some
Koji Sekiguchi wrote:
gwk wrote:
Hello,
The wiki states 'When duplicate doc IDs are received, Solr chooses
the first doc and discards subsequent ones', I was wondering whether
the first doc is the doc of the shard which responds first or the
doc in the first shard in the shards GET
Yes, that's the standard trick. :)
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: gwk g...@eyefi.nl
To: solr-user@lucene.apache.org
Sent: Wednesday, February 25, 2009 5:18:47 AM
Subject: Re: Distributed Search
Koji Sekiguchi wrote
Otis Gospodnetic wrote:
Yes, that's the standard trick. :)
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: gwk g...@eyefi.nl
To: solr-user@lucene.apache.org
Sent: Wednesday, February 25, 2009 5:18:47 AM
Subject: Re: Distributed Search
401 - 500 of 598 matches
Mail list logo
