Hi,
I have read in one post in the Internet that the hash Solr Cloud
calculates over the key field to send each document to a different shard
is indexed. Is this true? If true, is there any way to show this hash for
each document?
Thanks,
David
Yes, it´s an XY problem :)
We are making the first tests to split our shard (Solr 5.1)
The problem we have is this: the number of documents indexed in the new
shards is lower than in the original one (19814 and 19653, vs 61100), and
always the same. We have no idea why Solr is doing this. A p
Hello,
We have problems with some queries. All of them include the tag NOT, and
in my opinion, the results don´t make any sense.
First problem:
This query " NOT Proc:ID01 " returns 95806 results, however this one "
NOT Proc:ID01 OR FileType:PDF_TEXT" returns 11484 results. But it's
imposs
Hi Shawn,
thank you for your quick response. I will read your links and make some
tests.
Regards,
David Dávila
DIT - 915828763
De: Shawn Heisey
Para: solr-user@lucene.apache.org,
Fecha: 25/02/2015 13:23
Asunto: Re: Problem with queries that includes NOT
On 2/25/2015 4:04 AM, dav
Hi,
I thought that we were using the edismax query parser, but it seems that
we had configured the dismax parser.
I have made some tests with the edismax parser and it works fine, so I'll
change it in our production Solr.
Regards,
David Dávila
DIT - 915828763
De: Alvaro Cabrerizo
Para
Hello,
I need to parse some complicated queries that only works properly with the
edismax query parser, in q and fq parameters. I am testing with
defType=edismax, but it seems that this clause only affects to the q
parameter. Is there any way to set edismax to the fq parameter?
Thank you very
Thank you!
David
De: Shawn Heisey
Para: solr-user@lucene.apache.org,
Fecha: 01/06/2015 18:53
Asunto: Re: fq and defType
On 6/1/2015 10:44 AM, david.dav...@correo.aeat.es wrote:
> I need to parse some complicated queries that only works properly with
the
> edismax query parser, in
Hello,
in our project we need to execute some big queries against Solr once a
day, with maybe more than 1000 results, in order to trigger a batch
proccess with the results. In the fl parameter we only are putting the ID
field, because we don't need large text fields.
This is our scenary:
- O
Hello,
we have a Solr Cloud 4.7, but this question is also related with other
versions, because we have tested this in several installations.
We have a very big index ( more than 400K docs) with big documents, but
in our queries we don't fetch the large fields in fl parameter. But, we
have s
Hi Miguel,
yes, but if I use enableLazyFieldLoading=trueand my queries only request
for very small fields like ID, DocumentCache shouldn't grow, although my
stored fields are very big. Am I wrong?
Best regards,
David Dávila Atienza
AEAT - Departamento de Informática Tributaria
Subdirección de
That could be an interesting test. Unfortunately now I don't have time to
do that, but maybe in future.
In order to avoid these memory consumptions we have reduced DocumentCache,
and we don't have any problems. Besides, big queries that can cause
problems are never made twice, so the DocumentCa
Hello,
we have a Solr Cloud 4.7 with 2 shards with 2 nodes each one.
Until now it was working fine, but since yesterday we have this error in
almost all the updates:
org.apache.solr.common.SolrException: Fallo en lectura de Conector
at
org.apache.solr.handler.loader.XMLLoader
Hi,
I have an index very big, with 337 G more or less. I am using Solr 4.2.
The problem we have is related with the size of segments: this is the size
of the biggest ones:
324 G, 3.7G, 3.6 G, 1.6 G, 1.6 G, 465 M ... We have
LogByteSizeMergePolicy with 10 as MergeFactor in our solrconfig.
Reall
Hello,
we have been using faceting for a long time, but now I have discovered a
problem that I can't understand:
the issue is that in a query with 2 results, in some facet values Solr is
answering that there are 4 results. But faceting only applies over the
result documents, therefore I think
Hi Alvaro,
this is the definition:
Para: "solr-user@lucene.apache.org" ,
Fecha: 06/02/2015 12:34
Asunto: Re: Problem with faceting
Hi Da
Hi,
that was the problem. I don't know why, but we have some documents
duplicated in the two shards, maybe we have had our config file wrong some
time.
Thank very much,
David Dávila Atienza
AEAT
De: Erick Erickson
Para: solr-user@lucene.apache.org,
Fecha: 08/02/2015 11:21
Asunto:
Hi,
I have encoutered a problem applying StopFilterFactory and
SynonimFilterFactory. The problem is that SynonymFilter removes the gaps
that were previously put by the StopFilterFactory. I'm applying filters in
query time, because users need to change synonym lists frequently.
This is my sche
Hi,
I am having a problem applying StopFilterFactory and
SynonimFilterFactory. The problem is that SynonymFilter removes the gaps
that were previously put by the StopFilterFactory. I'm applying filters in
query time, because users need to change synonym lists frequently.
This is my schema, a
Hi,
I have a question related with atomic update in Solr.
In our collection, documents have a lot of fields, most of them small.
However, there is one of them that includes the text of the document.
Sometimes, not many fortunatelly, this text is very long, more than 3 or 4
MB of plain text. W
Hi Erick,
Thank you for your answer.
Unfortunatelly our most important field is that text field, so, we need to
index it. We will have to assume that big documents takes a long time to
index.
Best,
David
David Dávila Atienza
AEAT - Departamento de Informática Tributaria
Subdirección de
20 matches
Mail list logo
