.
To: solr-user@lucene.apache.org
Subject: Re: Multiple cores versus a "source" field.
One more opinion on source field vs separate collections for multiple corpora.
Index statistics don’t really settle down until at least 100k documents. Below
that, idf is pretty noisy. With Ultraseek, we
December 2017 4:11 p.m.
> To: solr-user
> Subject: Re: Multiple cores versus a "source" field.
>
> That's the unpleasant part of semi-structued documents (PDF, Word, whatever).
> You never know the relationship between raw size and indexable text.
>
> Basically a
with that now.
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Tuesday, 5 December 2017 4:11 p.m.
To: solr-user
Subject: Re: Multiple cores versus a "source" field.
That's the unpleasant part of semi-structued documents (PDF, Word, whate
That's the unpleasant part of semi-structued documents (PDF, Word,
whatever). You never know the relationship between raw size and
indexable text.
Basically anything that you don't care to contribute to _scoring_ is
often better in an fq clause. You can also use {!cache=false} to
bypass actually u
>You'll have a few economies of scale I think with a single core, but frankly I
>don't know if they'd be enough to measure. You say the docs are "quite large"
>though, >are you talking books? Magazine articles? is 20K large or are the 20M?
Technical reports. Sometimes up to 200MB pdfs, but that
At that scale, whatever you find administratively most convenient.
You'll have a few economies of scale I think with a single core, but
frankly I don't know if they'd be enough to measure. You say the docs
are "quite large" though, are you talking books? Magazine articles? is
20K large or are the 2
On Feb 8, 2012, at 10:14 PM, Jamie Johnson wrote:
> Thanks Mark, in regards to failover I completely agree, I am wondering more
> about performance and memory usage if the indexes are large and wondering
> if the separate Java instances under heavy load would more or less
> performant. Currently
Thanks Mark, in regards to failover I completely agree, I am wondering more
about performance and memory usage if the indexes are large and wondering
if the separate Java instances under heavy load would more or less
performant. Currently we deploy a single core per instance but deploy
multiple in
On Feb 8, 2012, at 9:52 PM, Jamie Johnson wrote:
> In solr cloud what is a better approach / use of resources having multiple
> cores on a single instance or multiple instances with a single core? What
> are the benefits and drawbacks of each?
It depends I suppose. If you are talking about on a
> tables. Others are suggesting 2 separate indexes on 2 different machines and
> using SOLRs capacity to combine cores and generate a third index that
> denormalizes the tables for us.
What capability is that, exaclty? I think you may be imagining it.
Solr does have some capability to distribut
"Betamax VCR"? really ? :-)
On Tue, Aug 9, 2011 at 3:38 PM, Chris Hostetter wrote:
>
> : A quick question - is it possible to have 2 cores in Solr on two
> different
> : machines?
>
> your question is a little vague ... like asking "is it possible to have to
> have two betamax VCRs in two diffe
Chris, sorry for not being clear when I asked the question.
We are still experimenting with Solr. We have 2 tables in Postgres that we
want to migrate to Solr for faster query results. One index is of static
data and the other related index would be of data that changes once or twice
a month. Some
: A quick question - is it possible to have 2 cores in Solr on two different
: machines?
your question is a little vague ... like asking "is it possible to have to
have two betamax VCRs in two different rooms of my house" ... sure, if you
want ... but why are you asking the question? are you e
On 8/8/2011 11:51 PM, Satish Talim wrote:
> A quick question - is it possible to have 2 cores in Solr on two different
> machines?
Yes
I would say it all depends on what you are trying to do. Unlike a
relational database, in Solr the data does not need to be normalised, you
need to put everything into an index so that you can achieve whatever
feature it is that you want. For example, you may search on customer and
want a facette
On Mon, Jun 20, 2011 at 10:08 AM, jboy79 wrote:
> Hi, I am new to SOLR and would like to know if multiple cores is the best way
> to deal with having a product and customer index.
If the indexes are going to have very different fields, it is probably
the case that
you want to go with multiple Sol
jel...@openindex.io]
> Sent: Friday, March 25, 2011 1:23 PM
> To: solr-user@lucene.apache.org
> Cc: Upayavira
> Subject: Re: Multiple Cores with Solr Cell for indexing documents
>
> You can only set properties for a lib dir that must be used in solrconfig.xml.
> You can use sharedLi
__
From: Markus Jelsma [markus.jel...@openindex.io]
Sent: Friday, March 25, 2011 1:23 PM
To: solr-user@lucene.apache.org
Cc: Upayavira
Subject: Re: Multiple Cores with Solr Cell for indexing documents
You can only set properties for a lib dir that must be used in solrconfig.xml.
You can use shared
solr.xml file is > > sharedLib="lib">. That is housed in .../example/solr/. So, does it
> > > look in .../example/lib or .../example/solr/lib?
> > >
> > > ~Brandon Waterloo
> > > ____
> > > From: Markus Jelsma [markus.jel...@openindex.io]
> > &g
n my solr.xml file is > sharedLib="lib">. That is housed in .../example/solr/. So, does it look
> > in .../example/lib or .../example/solr/lib?
> >
> > ~Brandon Waterloo
> >
> > From: Markus Jelsma [markus.
_
> From: Markus Jelsma [markus.jel...@openindex.io]
> Sent: Thursday, March 24, 2011 11:29 AM
> To: solr-user@lucene.apache.org
> Cc: Brandon Waterloo
> Subject: Re: Multiple Cores with Solr Cell for indexing documents
>
> Sounds like the Tika jar is not on the class pat
Markus Jelsma [markus.jel...@openindex.io]
Sent: Thursday, March 24, 2011 11:29 AM
To: solr-user@lucene.apache.org
Cc: Brandon Waterloo
Subject: Re: Multiple Cores with Solr Cell for indexing documents
Sounds like the Tika jar is not on the class path. Add it to a directory where
Solr's looking f
Sounds like the Tika jar is not on the class path. Add it to a directory where
Solr's looking for libs.
On Thursday 24 March 2011 16:24:17 Brandon Waterloo wrote:
> Hello everyone,
>
> I've been trying for several hours now to set up Solr with multiple cores
> with Solr Cell working on each core
On 10/21/2010 2:14 PM, didier deshommes wrote:
I use this configuration too but doesn't this assume that solr.xml is
the same in master and slave? what happens when master creates a new
core?
That's a very good question, one that I can't answer. I don't
dynamically create new cores. If you c
On Thu, Oct 21, 2010 at 3:00 PM, Shawn Heisey wrote:
> On 10/21/2010 1:42 PM, didier deshommes wrote:
>>
>> I noticed that the java-based replication does not make replication of
>> multiple core automatic. For example, if I have a master with 7
>> cores, any slave I set up has to explicitly know
On 10/21/2010 1:42 PM, didier deshommes wrote:
I noticed that the java-based replication does not make replication of
multiple core automatic. For example, if I have a master with 7
cores, any slave I set up has to explicitly know about each of the 7
cores to be able to replicate them. This infor
Hope this info helps.
Regards,
Ravi
From: Otis Gospodnetic
To: solr-user@lucene.apache.org
Sent: Thu, July 15, 2010 4:56:24 AM
Subject: Re: Multiple cores or not?
Hello there,
I'm guessing the sites will be searched separately. In that case I'd r
Hello there,
I'm guessing the sites will be searched separately. In that case I'd recommend
a core for each site.
Otis
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
Lucene ecosystem search :: http://search-lucene.com/
- Original Message
> From: "scr...@asia.com"
>
Thanks for all the help guys. I now have it up and running.
Jon Baer wrote:
I would not use this layout, you are putting important Solr config files
outside onto the docroot (presuming we are looking @ the webapps folder) ...
here is my current Tomcat project (if it helps):
[507][jonbaer.MBP
I would not use this layout, you are putting important Solr config files
outside onto the docroot (presuming we are looking @ the webapps folder) ...
here is my current Tomcat project (if it helps):
[507][jonbaer.MBP: tomcat]$ pwd
/Users/jonbaer/WORKAREA/SVN_HOME/my-project/tomcat
[508][jonbaer
Here's how I've got things set up. It's a different directory structure
than yous, and I run it under jetty, but hopefully it gives you the
basic idea. The dataDir setting is relative to the instanceDir
setting. I run jetty with -Dsolr.solr.home=/index/solr so it can find
solr.xml.
[r...@i
> My SOLR directory structure is:
>
> solr
> admin
> home
> bin
> conf
> data
> solr.xml
> multicore
> core0
> data
> conf
> core1
> data
> conf
> META-IN
Thanks a lot everybody for the responses ... I am going to do some
practical/empirical testing and will report
matt
--- On Wed, 1/27/10, Tom Hill wrote:
From: Tom Hill
Subject: Re: Multiple Cores Vs. Single Core for the following use case
To: solr-user@lucene.apache.org
Date: Wednesday
arch for "Paris"
> ?
> > matt
> >
> > --- On Wed, 1/27/10, didier deshommes wrote:
> >
> > From: didier deshommes
> > Subject: Re: Multiple Cores Vs. Single Core for the following use case
> > To: solr-user@lucene.apache.org
> > Date: Wed
fast as if I would getCore(userId)
> -- provided that the core is already open -- and then search for "Paris" ?
> matt
>
> --- On Wed, 1/27/10, didier deshommes wrote:
>
> From: didier deshommes
> Subject: Re: Multiple Cores Vs. Single Core for the following use
Thanks Didier for your response
And in your opinion, this should be as fast as if I would getCore(userId) --
provided that the core is already open -- and then search for "Paris" ?
matt
--- On Wed, 1/27/10, didier deshommes wrote:
From: didier deshommes
Subject: Re: Multiple Cores
Paris" for
userId="123", is lucene going to first search for all Paris
documents and then apply a filter on the userId ? If this is the
case, then I am better off having a specific index for the
user="123" because this will be faster
--- On Wed, 1/27/10, Marc
s will
filter by userid first then search for "Paris".
didier
>
>
>
>
>
> --- On Wed, 1/27/10, Marc Sturlese wrote:
>
> From: Marc Sturlese
> Subject: Re: Multiple Cores Vs. Single Core for the following use case
> To: solr-user@lucene.apache.org
> Dat
If this is the case, then I am better off having a specific index for the
user="123" because this will be faster
--- On Wed, 1/27/10, Marc Sturlese wrote:
From: Marc Sturlese
Subject: Re: Multiple Cores Vs. Single Core for the following use case
To: solr-user@lucene.apache.o
In case you are going to use core per user take a look to this patch:
http://wiki.apache.org/solr/LotsOfCores
Trey-13 wrote:
>
> Hi Matt,
>
> In most cases you are going to be better off going with the userid method
> unless you have a very small number of users and a very large number of
> doc
Hi Matt,
In most cases you are going to be better off going with the userid method
unless you have a very small number of users and a very large number of
docs/user. The userid method will likely be much easier to manage, as you
won't have to spin up a new core every time you add a new user. I wo
use the dataDir attribute in the tag to specify the data
directory. The property is not required
On Fri, Aug 28, 2009 at 11:56 PM, Paul Tomblin wrote:
> I'm trying to instantiate multiple cores. Since nothing is different
> between the two cores except the schema and the data dir, I was hoping
>
42 matches
Mail list logo
