>> The problem I am facing is how to read those data from hard disks which are
>> not HDFS
If you are planning to use a Map-Reduce job to do the indexing then the source
data will definitely have to be on HDFS.
The Map function can transform the source data to Solr documents and send them
to So
My understanding is the same that "{!join...}" does not work in SolrCloud (aka
distributed search)
based on:
1. https://issues.apache.org/jira/browse/LUCENE-3759
2. http://wiki.apache.org/solr/DistributedSearch
--- see "Limitations" section which refers to the JIRA above
-- James
-Original
Hi Henrik,
We did something related to this that I'll share. I'm rather new to Solr so
take this idea cautiously :-)
Our requirement was to show exact values but have case-insensitive sorting and
facet filtering (prefix filtering).
We created an index field (type="string") for creating facets
Are you using IE? If so, you might want to try using Firefox.
-Original Message-
From: sathish_ix [mailto:skandhasw...@inautix.co.in]
Sent: Wednesday, June 05, 2013 6:16 AM
To: solr-user@lucene.apache.org
Subject: Sole instance state is down in cloud mode
Hi,
When i start a core in sol
This may help:
http://docs.lucidworks.com/display/solr/Shards+and+Indexing+Data+in+SolrCloud
--- See "Document Routing" section.
-Original Message-
From: sathish_ix [mailto:skandhasw...@inautix.co.in]
Sent: Friday, June 07, 2013 5:27 AM
To: solr-user@lucene.apache.org
Subject: How to st
FWIW, the Solr included with Cloudera Search, by default, "ignores all but the
most recent document version" during merges.
The conflict resolution is configurable however. See the documentation for
details.
http://www.cloudera.com/content/support/en/documentation/cloudera-search/cloudera-search
This page has some good information on custom document routing:
http://docs.lucidworks.com/display/solr/Shards+and+Indexing+Data+in+SolrCloud
-Original Message-
From: Rishi Easwaran [mailto:rishi.easwa...@aol.com]
Sent: Wednesday, June 12, 2013 1:40 PM
To: solr-user@lucene.apache.org
S
Looks like the javadoc on this parameter could use a little tweaking.
>From looking at the 4.3 source code (hoping I get this right :-), it appears
>the ConcurrentUpdateSolrServer will begin sending documents (on a single
>thread) as soon as the first document is added.
New threads (up to thread
Seems to work fine for me on 4.3.0, maybe you can try a newer version.
4.3.1 is available.
-Original Message-
From: Elodie Sannier [mailto:elodie.sann...@kelkoo.fr]
Sent: Friday, June 21, 2013 8:54 AM
To: solr-user@lucene.apache.org >> "solr-user@lucene.apache.org"
Subject: SolrCloud: no
Hi,
Simple question, I hope.
Using the nightly build of 4.1 from yesterday (Jan 8, 2013), I started 6 Solr
nodes.
I issued the following command to create a collection with 3 shards, and a
replication factor=2. So a total of 6 shards.
curl
'http://localhost:11000/solr/admin/collections?a
view.
I see a new collection called consumer1 - all of it's nodes are green and the
collection consists of 3 shards. Each shard has 1 leader and 1 replica, each
hosted by a different Solr instance.
In other words, it seemed to work for me.
- Mark
On Jan 9, 2013, at 10:58 AM, Jam
Oops, small copy-paste error. Had my i's and j's backwards.
Should be:
--- slice1, rep2 (i=1,j=2) ==> chooses node[1]
--- slice2, rep1 (i=2,j=1) ==> chooses node[1]
-Original Message-----
From: James Thomas [mailto:jtho...@camstar.com]
Sent: Wednesday, January 09, 2013
12 matches
Mail list logo