Hello,
I have a little problem.
In Solr index I have a lot of nested documents. I figured out the query for
fetching the childrens which is the following:
Nested doc example:
1
I am the parent
PARENT
1.1
I am the 1st child
Eirck,
I meant having a replication factor of 1 in SolrCloud would not be
scalable, I ended up using a replication factor of 1 , because of the
disjoint replicas issue for replication factor greater than 1 , that I
mentioned previously in the other email thread.
Are you saying that a SolrCloud cl
I _strongly_ urge you to try it before assuming it won't work.
bq: It obviously seems will not be scalable due to the fact that the same core
will be indexed and queried at the same time as this is a long running
indexing task.
What evidence do you have for this? SolrCloud is designed for this sc
Resending this as I might have not been clear in my earlier query.
I want to use SolrCloud for everything except the replication , is it
possible to set up the master-slave configuration using different Solr
instances and still be able to use the sharding feature provided by
SolrCloud ?
On Thu,
That tutorial seems to be somewhat dodgy. You need at least one more
step of adding DIH library in solrconfig.xml:
https://github.com/apache/lucene-solr/blob/lucene_solr_4_10_2/solr/example/example-DIH/solr/db/conf/solrconfig.xml#L75
(I recommend using absolute path though).
Also, you should not n
Hi Alex,
> I thought the ""
> and the ending span were broken email thing but they seem to be in the
> solrconfig.xml file as well. I would start from removing those and
> leaving just the actual definition.
Thanks for your response!
OK so I tried your suggestion of removing those span tags li
Well,
I thought the ""
and the ending span were broken email thing but they seem to be in the
solrconfig.xml file as well. I would start from removing those and
leaving just the actual definition.
Regards,
Alex.
Personal: http://www.outerthoughts.com/ and @arafalov
Solr resources and newslette
Hey guys,
I'm real new at working with Solr. But I need to get up to speed and I
appreciate your bearing with me.
I've installed solr 4 and am running it under tomcat 7. The install went
perfectly fine and everything seems to work, up to a point. I've even
automated the installation with puppet
Hi Tomer,
What happens when you addto your chain?
Ahmet
On Sunday, November 2, 2014 1:22 PM, Tomer Levi wrote:
Hi,
I’m trying to make my “update” request handler ignore multivalue duplications
in updates.
To make my use case clear, let’s assume my index already contains a document
li
Yeah, that behavior is consistent with what I documented in my e-book for
Solr. The dot is kept only if between two digits or two letters.
-- Jack Krupansky
-Original Message-
From: Jorge Luis BetancourtGonzález
Sent: Sunday, November 2, 2014 4:34 PM
To: solr-user@lucene.apache.org
Su
Hi all:
>From the description of the StandardTokenizer, it should Recognizes Internet
>domain names and email addresses and preserves them as a single token, which
>works great, but I've detected that in cases like this:
socks25.domain.com it outputs 2 tokens: socks25 | domain.com
if the URL d
The upper limit for a filterCache entry is roughly
(size of fq clause) + (maxDoc/8)
You can get maxDoc from your admin/overview page.
the filterCache is just a map. The key is the fq clause
so the size there is just the string length + around 40.
The value is, at most, a bitset representing all
I have Solr server set up on CentOS that's being queried from a Flask app in
a very specific/controlled way. Basically, I just have a large (200 million)
amount of largely static name/address data (along with an internal record ID
field and a few integer fields). I'm running 50 threads that need to
Besides, if you follow my methodology with a pre-production test system,
sure, that test system may crash for some schema changes if you don't follow
all the details of my methodology, but Walter won't be able to actually
"see" that internal-only site "crash".
Further, the "crash" would more l
Well. You don't really think I HAVE a solr installation, do you Walter? ;-)
No you're right. The pattern I put out was general.
It depends on the schema change doesn't it?
-Original Message-
From: Walter Underwood [mailto:wun...@wunderwood.org]
Sent: Saturday, November 01, 2014 11:4
Hi,
I'm trying to make my "update" request handler ignore multivalue duplications
in updates.
To make my use case clear, let's assume my index already contains a document
like:
{
id:"100",
"myMultValueField": ["1","2","3"]
}
Later I would like to send an update like:
{
id:"100","
myMul
16 matches
Mail list logo