Hi Roi,
I don’t know the details about your test, but trying to assume how it looks
like and explain observed. With your flat test you are denormalising data,
meaning creating data duplication so the resulting document set is larger. That
means more fields/text for Solr/Lucene to analyse and to
Dear All,
Nobody is able to tell me if this structure can be querying with whole parents ?
Sorry for this second message,
Sincerely,
Bruno
-Message d'origine-
De : Bruno Mannina [mailto:bmann...@matheo-software.com]
Envoyé : mercredi 5 décembre 2018 11:33
À : solr-user@lucene.apache.or
Thank you Erick.
That was my instinct as well.
On Tue, Mar 6, 2018 at 10:05 AM, Erick Erickson
wrote:
> Flattening the nested documents is usually preferred if at all
> possible. Nested documents to, indeed, have a series of restrictions
> that often make them harder to work with than flatten
Flattening the nested documents is usually preferred if at all
possible. Nested documents to, indeed, have a series of restrictions
that often make them harder to work with than flattened docs.
Best,
Erick
On Tue, Mar 6, 2018 at 6:48 AM, Dc Tech wrote:
> We are evaluating using nested documents
I can get this to:
"q":"(+${parent_match} +${condition_match}) {!child
of=${parent_match}}${condition_match}",
"parent_match":"type:release",
"condition_match":"release_name:\"6.1.0\"",
But I am not sure that's "smarter".
Regards,
Alex.
Newsletter and resources for Solr beginners and
Right.
But how do I structure the query to say to match all root values that
correspond to the parent entries selected by query.
Maybe I am just blanking here but how do I form the query:
q=_root_:[set of id values from query (+type:release +release_name:"6.1.0")]
Regards,
Alex.
Newslet
Hello Alex,
Internally, _root_ field is assigned across whole block. You can use it in
deleteByQuery. The value for this field is equal to parent's uniqueKey.
On Sun, Sep 4, 2016 at 5:51 AM, Alexandre Rafalovitch
wrote:
> Hello,
>
> If I am correct, deleting parent document still keeps the child
Please check [child] [subquery] document transformers.
23 июня 2016 г. 10:57 пользователь "Anil" написал:
> HI,
>
> I understand child and parent documents are individual documents in nested
> document indexing.
>
> is there any way to get the parent documents with query of AND of two child
> con
The new Parallell SQL feature of 6.0? Also query-time on top of streaming,
don’t know performance...
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
> 1. feb. 2016 kl. 07.37 skrev Sathyakumar Seshachalam
> :
>
> Thanks, query time joins are not an option for me, beca
Thanks, query time joins are not an option for me, because of the size of
the index and hence the join performance,
I will look at Siren.
On 29/01/16, 10:16 PM, "Alessandro Benedetti"
wrote:
>Probably if you are interested in a many-to-many relation, you could be
>interested in the query time
Hello,
This implies that an indexing extracts cliques of bipartite graph. Then,
every clique goes as a single block with a sentinel parent document. And
this parent document can carry incidence matrix as, let's say, binary
docvalues. Then, a bunch of custom components can to handle this model.
On
Probably if you are interested in a many-to-many relation, you could be
interested in the query time join.
it has been the first type of join integrated in Solr.
It allow you to avoid redundancies.
It's slower than block join, but it doesn't force you to any specific
indexing approach.
It became le
If you wish to change, add, or delete a child or change the parent you must
do an add of the entire block again with both the parent and all children.
This is because the efficiency of Block Join comes from the documents being
adjacent in Lucene and segments are immutable in Lucene, so the entire
b
Hello Aurélien,
There are a lot of materials about this problem. Start from this one:
https://www.youtube.com/watch?v=YCkkOyZ-zkM
On Wed, Oct 22, 2014 at 6:08 PM, wrote:
> Hi Ramzi,
>
> Thank you but I am not sure to understand well your answer. In your
> example, I suppose that the indexed doc
Hi Ramzi,
Thank you but I am not sure to understand well your answer. In your
example, I suppose that the indexed docs are flattened. If I want an AND
query instead of an OR query (let say, for example 'chapter_title:Lucene
AND chapter_content:fun'), how can I be sure that the terms "Lucene" a
I think if I have your question right, You can use multiple custom query
syntax. You explicitly specify an alternative query parser such as DisMax or
eDisMax, you're using the standard Lucene query parser by default.
In your case, I think I can solve it by using this query
chapter_title:Introducti
On Sun, Mar 16, 2014 at 2:47 PM, danny teichthal wrote:
>
> To make things short, I would like to use block joins, but to be able to
> index each document on the block separately.
>
> Is it possible?
>
no way. use query time {!join} or denormalize then, field collapsing.
--
Sincerely yours
Mi
he entire block, and maybe some way to delete individual child documents
> as well.
>
> -- Jack Krupansky
>
> -Original Message- From: danny teichthal
> Sent: Tuesday, March 18, 2014 3:58 AM
> To: solr-user@lucene.apache.org
> Subject: Re: Nested documents, block join
nts as well as the parent document can be updated with one rewrite of
the entire block, and maybe some way to delete individual child documents as
well.
-- Jack Krupansky
-Original Message-
From: danny teichthal
Sent: Tuesday, March 18, 2014 3:58 AM
To: solr-user@lucene.apache.org
Subj
Thanks Jack,
I understand that updating a single document on a block is currently not
supported.
But, atomic update to a single document does not have to be in conflict
with block joins.
If I got it right from the documentation:
Currently, If a document is atomically updated, SOLR finds the stor
You stumbled upon the whole point of block join – that the documents are and
must be managed as a block and not individually.
-- Jack Krupansky
From: danny teichthal
Sent: Sunday, March 16, 2014 6:47 AM
To: solr-user@lucene.apache.org
Subject: Nested documents, block join - re-indexing a singl
To support this, we also need to implement indexing block of documents in Solr.
Basically the UpdateHandler should also use this method:
IndexWriter#addDocuments(Collection documents)
On 12 September 2011 01:01, Michael McCandless
wrote:
> Even if it applies, this is for Lucene. I don't think we
Even if it applies, this is for Lucene. I don't think we've added
Solr support for this yet... we should!
Mike McCandless
http://blog.mikemccandless.com
On Sun, Sep 11, 2011 at 12:16 PM, Erick Erickson
wrote:
> Does this JIRA apply?
>
> https://issues.apache.org/jira/browse/LUCENE-3171
>
> Bes
Does this JIRA apply?
https://issues.apache.org/jira/browse/LUCENE-3171
Best
Erick
On Sat, Sep 10, 2011 at 8:32 PM, Andy wrote:
> Hi,
>
> Does Solr support nested documents? If not is there any plan to add such a
> feature?
>
> Thanks.
24 matches
Mail list logo
