This is very helpful. Thanks a lot, Shaun and Dikchant!
So in default single-core situation, the index would live in data/index,
correct?
On Fri, Nov 30, 2012 at 11:02 PM, Shawn Heisey wrote:
> On 11/30/2012 10:11 PM, Joe Zhang wrote:
>
>> May I ask: how to set up multiple indexes, and specify
On 11/30/2012 10:11 PM, Joe Zhang wrote:
May I ask: how to set up multiple indexes, and specify which index to send
the docs to at indexing time, and later on, how to specify which index to
work with?
A related question: what is the storage location and structure of solr
indexes?
When you index
Multiple indexes can be setup using the multi core feature of Solr.
Below are the steps:
1. Add the core name and storage location of the core to
the $SOLR_HOME/solr.xml file.
**
**
2. Create the core-directories specified and following sub-directories in
it:
- conf: Contains th
your data is being used to build an inverted index rather than being
stored as a set of records. de-normalising is fine in most cases. what
is your use case which requires a normalised set of indices ?
2011/6/18 François Schiettecatte :
> You would need to run two independent searches and then 'jo
You would need to run two independent searches and then 'join' the results.
It is best not to apply a 'sql' mindset to SOLR when it comes to
(de)normalization, whereas you strive for normalization in sql, that is usually
counter-productive in SOLR. For example, I am working on a project with 30+
Il 18 giugno 2011 20:27, François Schiettecatte
ha scritto:
> Sure.
So I can have some searches similar to JOIN on MySQL?
The problem is that I need at least two tables in which search data..
Sure.
François
On Jun 18, 2011, at 2:25 PM, shacky wrote:
> 2011/6/15 Edoardo Tosca :
>> Try to use multiple cores:
>> http://wiki.apache.org/solr/CoreAdmin
>
> Can I do concurrent searches on multiple cores?
2011/6/15 Edoardo Tosca :
> Try to use multiple cores:
> http://wiki.apache.org/solr/CoreAdmin
Can I do concurrent searches on multiple cores?
> > (for example if you need separate TFs for each document type).
>
> I wonder if in this precise case it wouldn't be pertinent to
> have a single index with the various document types each
> having each their own fields set. Isn't TF calculated field by field ?
Oh, you are right :)
So i will
> I think there are reasons to use seperate indexes for each document type
> but do combined searches on these indexes
> (for example if you need separate TFs for each document type).
I wonder if in this precise case it wouldn't be pertinent to have a single
index with the various document types
o: solr-user@lucene.apache.org
> Subject: Re: Multiple indexes
>
> Next, however, I predict you're going to ask how you do a 'join' or
> otherwise query accross both these cores at once though. You can't do
> that in Solr.
>
> On 6/15/2011 1:00 PM, Fran
Next, however, I predict you're going to ask how you do a 'join' or
otherwise query accross both these cores at once though. You can't do
that in Solr.
On 6/15/2011 1:00 PM, Frank Wesemann wrote:
You'll configure multiple cores:
http://wiki.apache.org/solr/CoreAdmin
Hi.
How to have multiple
You'll configure multiple cores:
http://wiki.apache.org/solr/CoreAdmin
Hi.
How to have multiple indexes in SOLR, with different fields and
different types of data?
Thank you very much!
Bye.
--
mit freundlichem Gruß,
Frank Wesemann
Fotofinder GmbH USt-IdNr. DE812854514
Software En
Try to use multiple cores:
http://wiki.apache.org/solr/CoreAdmin
On Wed, Jun 15, 2011 at 5:55 PM, shacky wrote:
> Hi.
>
> How to have multiple indexes in SOLR, with different fields and
> different types of data?
>
> Thank you very much!
> Bye.
>
--
Edoardo Tosca
Sourcesense - making sense o
Here's the Jira issue for the distributed search issue.
https://issues.apache.org/jira/browse/SOLR-1632
I tried applying this patch but, get the same error that is posted in the
discussion section for that issue. I will be glad to help too on this one.
On Sat, Oct 23, 2010 at 2:35 PM, Erick Erick
Ah, I should have read more carefully...
I remember this being discussed on the dev list, and I thought there might
be
a Jira attached but I sure can't find it.
If you're willing to work on it, you might hop over to the solr dev list and
start
a discussion, maybe ask for a place to start. I'm sur
Thanks Erick. The problem with multiple cores is that the documents are scored
independently in each core. I would like to be able to search across both
cores and have the scores 'normalized' in a way that's similar to what Lucene's
MultiSearcher would do. As far a I understand, multiple core
It seems to me that multiple cores are along the lines you
need, a single instance of Solr that can search across multiple
sub-indexes that do not necessarily share schemas, and are
independently maintainable..
This might be a good place to start: http://wiki.apache.org/solr/CoreAdmin
HTH
Eri
The score of a document has no scale: it only has meaning against other
score in the same query.
Solr does not rank these documents correctly. Without sharing the TF/DF
information across the shards, it cannot.
If the shards each have "a lot" of the same kind of document, this
problem averag
ould be hitting. With this approach your can have separate
>> schema.xml & solrconfig.xml for each of the cores & obviously separate
>> index in each core.
>>
>> -Raghu
>>
>> -Original Message-
>> From: anshuljohri [mailto:[EMAIL PROTECTE
; solrconfig.xml for each of the cores & obviously separate
> index in each core.
>
> -Raghu
>
> -Original Message-
> From: anshuljohri [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 07, 2008 5:19 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Multipl
ach core.
-Raghu
-Original Message-
From: anshuljohri [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2008 5:19 PM
To: solr-user@lucene.apache.org
Subject: Re: Multiple Indexes
Both the cases are there. As i said i need to index 3 indexes. So 2
indexes
have same schema but other
Alexander Ramos Jardim wrote:
Oh,
Sorry!
Can you be a little more specific? Do these indexes have different schemas,
or do they represent the same data model?
If they have different schemas, MultiCore support is definitely worth
looking at (again, requires 1.3-ish Solr code, as it was adde
Both the cases are there. As i said i need to index 3 indexes. So 2 indexes
have same schema but other one has different. More specification is like
this --
I have 3 indexes. In which 2 indexes have same data model but the way these
are indexed is different. So i need to fire query from backend o
Oh,
Sorry!
Can you be a little more specific? Do these indexes have different schemas,
or do they represent the same data model?
2008/8/7 anshuljohri <[EMAIL PROTECTED]>
>
> Thanks zayhen for such a quick response but am not talking about sharding.
> I
> have requirement of indexing 3 indexes.
Thanks zayhen for such a quick response but am not talking about sharding. I
have requirement of indexing 3 indexes. Need to do query on diff indexes
based on input.
-Anshul
zayhen wrote:
>
> 2008/8/7 anshuljohri <[EMAIL PROTECTED]>
>
>>
>> Hi everybody!
>>
>> I need to create multiple indexes
2008/8/7 anshuljohri <[EMAIL PROTECTED]>
>
> Hi everybody!
>
> I need to create multiple indexes lets say 3 due to project requirement.
> And
> the query will be fired from backend on different indexes based on input. I
> can't do it in one index with the help of "fq" parameter. As i have already
I have built the master solr instance and indexed some files. Once I run
snapshotter, i complains the error.. - snapshooter -d data/index (in
solr/bin directory)
Did I missed something?
++ date '+%Y/%m/%d %H:%M:%S'
+ echo 2007/11/12 12:38:40 taking snapshot
/solr/master/solr/data/index/snapshot.2
just use the standard collection distribution stuff. That is what it is
made for! http://wiki.apache.org/solr/CollectionDistribution
Alternatively, open up two indexes using the same config/dir -- do your
indexing on one and the searching on the other. when indexing is done
(or finishes a
Here is my situation.
I have 6 millions articles indexed and adding about 10k articles everyday.
If I maintain only one index, whenever the daily feeding is running, it
consumes the heap area and causes FGC.
I am thinking the way to have multiple indexes - one is for ongoing querying
service and o
The advantages of a multi-core setup are configuration flexibility and
dynamically changing available options (without a full restart).
For high-performance production solr servers, I don't think there is
much reason for it. You may want to split the two indexes on to two
machines. You may w
Hello,
Until now, i've used two instance of solr, one for each of my collections ; it
works fine, but i wonder
if there is an advantage to use multiple indexes in one instance over several
instances with one index each ?
Note that the two indexes have different schema.xml.
Thanks.
PL
> Date:
I've had good luck with MultiCore, but you have to sync trunk from svn
and apply the most recent patch in SOLR-350.
https://issues.apache.org/jira/browse/SOLR-350
-jrr
Jae Joo wrote:
Hi,
I am looking for the way to utilize the multiple indexes for signle sole
instance.
I saw that there is th
OK...I see...thk u ,mike.
2007/8/31, Mike Klaas <[EMAIL PROTECTED]>:
>
>
> On 29-Aug-07, at 10:21 PM, James liu wrote:
>
> > Does it affect with doc size？
> >
> > for example 2 billion docs, 10k doc2 billion docs, but doc size
> > is 10m.
>
> There might be other places that have 2G limit (see
Subject: Re: Multiple indexes
On 29-Aug-07, at 10:21 PM, James liu wrote:
Does it affect with doc size？
for example 2 billion docs, 10k doc2 billion docs, but doc size
is 10m.
There might be other places that have 2G limit (see lucene index
format docs), but many things are vints and can
Klaas [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 30, 2007 11:44 AM
To: solr-user@lucene.apache.org
Subject: Re: Multiple indexes
On 29-Aug-07, at 10:21 PM, James liu wrote:
> Does it affect with doc size？
>
> for example 2 billion docs, 10k doc2 billion docs, but doc size
On 29-Aug-07, at 10:21 PM, James liu wrote:
Does it affect with doc size？
for example 2 billion docs, 10k doc2 billion docs, but doc size
is 10m.
There might be other places that have 2G limit (see lucene index
format docs), but many things are vints and can grow larger.
Of course
Does it affect with doc size？
for example 2 billion docs, 10k doc2 billion docs, but doc size is 10m.
2007/8/30, Mike Klaas <[EMAIL PROTECTED]>:
>
> 2 billion docs (signed int).
>
> On 29-Aug-07, at 6:24 PM, James liu wrote:
>
> > what is the limits for Lucene and Solr.
> >
> > 100m, 1000m,
2 billion docs (signed int).
On 29-Aug-07, at 6:24 PM, James liu wrote:
what is the limits for Lucene and Solr.
100m, 1000m, 5000m or other number docs?
2007/8/24, Walter Underwood <[EMAIL PROTECTED]>:
It should work fine to index them and search them. 13 million docs is
not even close to t
what is the limits for Lucene and Solr.
100m, 1000m, 5000m or other number docs?
2007/8/24, Walter Underwood <[EMAIL PROTECTED]>:
>
> It should work fine to index them and search them. 13 million docs is
> not even close to the limits for Lucene and Solr. Have you had problems?
>
> wunder
>
> On
The potential problem is performance. I have tested with 1.3 Millions and it
returns fast enough.
Jae
On 8/23/07, Walter Underwood <[EMAIL PROTECTED]> wrote:
>
> It should work fine to index them and search them. 13 million docs is
> not even close to the limits for Lucene and Solr. Have you had
It should work fine to index them and search them. 13 million docs is
not even close to the limits for Lucene and Solr. Have you had problems?
wunder
On 8/23/07 7:30 AM, "Jae Joo" <[EMAIL PROTECTED]> wrote:
> Is there any solution to handle 13 millions document shown as below?
> Each document is
As this question comes up so often, i put a new page on the wiki:
http://wiki.apache.org/solr/MultipleIndexes
We should fill in more details and link it to the front page.
Chris Hostetter wrote:
: So if you're looking for some shoes:
: (size:8 AND color:'blue') AND object_type:'shoe'
: Or i
: So if you're looking for some shoes:
: (size:8 AND color:'blue') AND object_type:'shoe'
: Or if you're searching on brands
: (genre:'skater' AND brand_desc:'skater boy') AND object_type:'brand'
a slight improvement on this: put your object_type restriction in a
filter query (&fq=object_type:foo
Ah. That makes sense then. I wasn't sure if that was the best way to
go about things or not. I didn't want to end up with a bunch of
fields that were not being used all the time if it would cause a
degradation in search quality.
++
|
Matthew,
All that is meant by "object_types" is an additional stored/indexed
field in the Solr schema that gets added to every document providing
context of which type it is (shoes or brands). Then you can limit
searches to a particular area by just filtering on type:shoes, for
example.
I'll actually be doing this in Perl..
any ideas on perl? heh
++
| Matthew Runo
| Zappos Development
| [EMAIL PROTECTED]
| 702-943-7833
++
On Apr 19, 2007, at 11:59 AM, Cody Caugh
If you're doing this in Ruby, there is an "acts_as_solr" plugin for
Rails which takes exactly this approach to store all different kinds
of Model objects in the same index...I just "took" the idea from
there...
/Cody
On 4/19/07, Matthew Runo <[EMAIL PROTECTED]> wrote:
Ah hah! This appears to be
Ah hah! This appears to be what I'm interested in doing.
I'll have to read up on object_types.
++
| Matthew Runo
| Zappos Development
| [EMAIL PROTECTED]
| 702-943-7833
++
On Apr
You can not have more than one Solr core per application (to be precise, per
class-loader since there are a few statics).
One way is thus to have 2 webapps - when & if indexes do not have the same
lifetime/radically different schema/etc.
However, the common wisdom is that you usually dont really n
Why not just store an additional "object_type" field which
differentiates between the actual type of data you are looking for?
So if you're looking for some shoes:
(size:8 AND color:'blue') AND object_type:'shoe'
Or if you're searching on brands
(genre:'skater' AND brand_desc:'skater boy') AND
he server down at all (because of the efficient indexes
that solr builds)
"Mike Klaas" <[EMAIL PROTECTED]>
22/03/2007 19:15
Please respond to
solr-user@lucene.apache.org
To
solr-user@lucene.apache.org
cc
Subject
Re: multiple indexes
On 3/22/07, Kevin Osborn <[EMAIL
: Why not create a multivalued field that stores the customer perms?
: add has_access:cust1 has_access:cust2, etc to the document at index
: time, and turn this into a filter query at query time?
this can be a particularly effective solution when the permissions don't
change at all .. the ideal s
On 3/22/07, Kevin Osborn <[EMAIL PROTECTED]> wrote:
Here is an issue that I am trying to resolve. We have a large catalog of
documents, but our customers (several hundred) can only see a subset of those
documents. And the subsets vary in size greatly. And some of these customers
will be creati
This is good information, thanks Chris. My preference was to keep things
separate, just needed some external info from others to back me up.
thanks,
jeff
On 1/7/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
I don't know if there really are any general purpose best practices ... it
really de
I don't know if there really are any general purpose best practices ... it
really depends on use cases -- the main motivation for allowing JNDI
context specification of the solr.home location so that multiple instances
of SOlr can run in a single instace of a servlet container was so that if
you *
While it may be easier from a management perspective, there are also
disadvantages
with runnning multiple indices within a single appserver port:
- they are sharing the memory of a single JVM so the size of the cache has to
be smaller then running a singler instance per appserver instance
- a si
: I guess the updates can also be done the same way then. So, I just have
: to create multiple context paths with different schema.xml files in each ?
: Thanks.
you wouldn't even need idffernet schema.xml files ... they could all be
symlinks to the same schema.xml, only the data directories would
the wiki shows how to configure everything. see "Multiple Solr Webapps" on:
http://wiki.apache.org/solr/SolrTomcat
http://wiki.apache.org/solr/SolrJetty
http://wiki.apache.org/solr/SolrResin
On 12/21/06, escher2k <[EMAIL PROTECTED]> wrote:
I guess the updates can also be done the same way
I guess the updates can also be done the same way then. So, I just have
to create multiple context paths with different schema.xml files in each ?
Thanks.
ryan mckinley wrote:
>
> You can run multiple webapps on a single app server (running on a single
> port). Just give each index a seperate
You can run multiple webapps on a single app server (running on a single
port). Just give each index a seperate context path. for example, you
could have:
http://xyz:8765/index1/select/?q=xxx
http://xyz:8765/index2/select/?q=xxx
http://xyz:8765/index3/select/?q=xxx
On 12/21/06, escher2k <[E
There would have to be only one app server running on a single port and
adding new indexes
is pretty easy. Currently we have four separate indexes which we run off of
Lucene using Jakarta
and the index to use is read from a config file. This definitely seems
easier from a management perspective.
What is the advantage to running multiple indexes from a single Solr
instance over multiple Solr instances each serving a single index?
Erik
On Dec 21, 2006, at 3:26 PM, escher2k wrote:
I looked at the forums and found that it is not possible to have
multiple
indexes associated w
63 matches
Mail list logo
