Hi Marc,
There are two concerns to consider:
- what you need to have in search results. If you need to have unique
files, nested is a way to go. If many versions of the same file appear
fine, so denormalize them. FieldCollapsing, Grouping and query time join
provides some flexibility but requires
Hi there,
I am working on a new Solr installation for our application. Here, wer
want to store file information in file documents and file versions in
fileversion documents. All file versions are related to file documents
therefore the question arises whether it would be a good idea to store
Hi,
Nested is a big nononno for modelling collections. It's either query time
join or field collapsing/grouping or just an aggregation or so.
On Wed, May 21, 2025 at 3:56 PM Yaşar Arabacı wrote:
> Hi,
>
> I am trying to figure out a schema for indexing documents that I will
> download from anoth
Hi,
I am trying to figure out a schema for indexing documents that I will
download from another document management system. In the original
source, documents are stored inside collections. Collections act like
folders with extra metadata (they cannot be nested though).
Each document must be part
ternal file and loads after each commit, instead of indexing into
> solr
> >> > for each change]
> >> >
> >> >
> >>
> https://solr.apache.org/guide/solr/latest/indexing-guide/external-files-processes.html
> >> > Observation:
> >>
>
>> > 2. POC on Inplace update: (Which helps in indexing fields which contains
>> > changes, but not entire document)
>> >
>> >
>> https://solr.apache.org/guide/solr/latest/indexing-guide/partial-document-updates.html#in-place-updates
>> > Observa
es, but not entire document)
> >
> >
> https://solr.apache.org/guide/solr/latest/indexing-guide/partial-document-updates.html#in-place-updates
> > Observation:
> > a. Works with only single values fields
> > b. Looks promising wrt indexing optimization but not suitable
gt; Observation:
> a. Works with only single values fields
> b. Looks promising wrt indexing optimization but not suitable wrt our
> schema (as we have more multivalued fields). so, dropped
>
>
> Then we moved for alternatives which is expected to help in optimizing
> respo
multivalued fields). so, dropped
Then we moved for alternatives which is expected to help in optimizing
response times
*To improve Solr Response time:*Nested Documents POC:
https://solr.apache.org/guide/solr/latest/indexing-guide/indexing-nested-documents.html
*wrt this statement:*
"In ter
u talk about grouping, have you considered field collapsing?
>
> According to my experience going with nested documents rarely justify the
> performance and functional overhead both at indexing and query time.
>
> But sometimes you need them.
>
> Also in place updates happen on very
What is your problem? Rather than asking about a solution you attempted is
usually better to start from the problem.
You talk about grouping, have you considered field collapsing?
According to my experience going with nested documents rarely justify the
performance and functional overhead both
25 at 8:05 AM Uday Kumar .invalid>
> wrote:
>
> > Hi all,
> > We are doing a POC on indexing nested documents in expectation of
> reducing
> > grouping overhead while querying time.
> >
> > On Prod Indexing, we are using the traditional approach of reindexing t
Changing one child rewrites the whole block period.
However in-place updating child docValues is promising in theory, although
I don't know how it works in practice.
On Thu, Feb 27, 2025 at 8:05 AM Uday Kumar
wrote:
> Hi all,
> We are doing a POC on indexing nested documents in exp
Hi all,
We are doing a POC on indexing nested documents in expectation of reducing
grouping overhead while querying time.
On Prod Indexing, we are using the traditional approach of reindexing the
entire document if there is any change in any of the fields. [we reindex
~2cr documents per day, FYI
Hi Alessandro,
Thank you for your detailed answer.
As I understand it, nested documents speed up searches on hierarchical
documents compared to Query Time Joins andc onsume fewer resources but
could create problems during reindexing.
Are there any studies to understand if there are limits to the
Hi Alessandro,
Thank you for your detailed answer.
As I understand it, nested documents speed up searches on hierarchical
documents compared to Query Time Joins andc onsume fewer resources but
could create problems during reindexing.
Are there any studies to understand if there are limits to the
Hi Isabella,
back in the day I wrote a blog post about nested documents, not strictly
related to pros and cons but can be useful:
https://sease.io/2019/06/apache-solr-childfilter-transformer.html
In terms of pros and cons, exploring the details of nested documents will
surely require a bit of
Hi,
We are studying a solution that takes advantage of nested documents and
therefore we are looking for information on the pros and cons and
limitations that this solution offers.
Furthermore, we wish to understand in which case is better to use nested
documents or query time joins.
Further Have
Hi Sergio,
in the block join, under the hood, nested docs are separate Lucene(Solr
documents).
Assuming you are retrieving parents after querying children (
https://solr.apache.org/guide/solr/latest/query-guide/block-join-query-parser.html#block-join-parent-query-parser)
that's all you got for rera
Hi,
I am trying to set up a list of features within LTR.
I have a collection *"person" *with a design of two levels. I have Person
documents with nested documetns classified as jobs.
Within the job level I have two fields describing if the job is current and
recency. I would like to incorporante
gt; On Tue, Apr 11, 2023 at 4:57 AM Charlie Hubbard >
> wrote:
>
> > Hi,
> >
> > I'm not sure what you mean by "naming children" exactly. I don't have a
> > stack trace, but this video discusses nested documents, and refers to
> > enhanced supp
(named
fields) at 6.6?
On Tue, Apr 11, 2023 at 4:57 AM Charlie Hubbard
wrote:
> Hi,
>
> I'm not sure what you mean by "naming children" exactly. I don't have a
> stack trace, but this video discusses nested documents, and refers to
> enhanced support in 6.x so I
Hi,
I'm not sure what you mean by "naming children" exactly. I don't have a
stack trace, but this video discusses nested documents, and refers to
enhanced support in 6.x so I know 6.x supports nested documents.
https://youtu.be/qV0fIg-LGBE?t=446
Here is what is
...
>},
>...
>]
> }
>
> It clearly doesn't like the field `pages` which isn't defined in the
> schema, but reading the various documents from Solr seems like it doesn't
> need to be? That Solr should recognize the nested documents
On 2023-04-10 12:47 PM, Charlie Hubbard wrote:
So I did try to add `_nest_path_` but I can't define it because the class `
solr.NestPathField`isn't available in Solr 6.6.6. I also have another
strange error message about atomic updates like so:
...
_root_ needs to be stored and/or docValues =t
So I did try to add `_nest_path_` but I can't define it because the class `
solr.NestPathField`isn't available in Solr 6.6.6. I also have another
strange error message about atomic updates like so:
some_document.pdf was rejected by the server for Error from server at
http://localhost:8983/solr/fu
On 2023-04-10 11:12 AM, Charlie Hubbard wrote:
Hi
I'm encountering the following error when indexing a parent and nested
children documents. I'm using managed schemas, Solr 6.6.6, and Solrj to
send the documents up to Solr for indexing. I have the default `_root_`
field defined in the schema,
_pageNumber: 1,
_type: "page",
content: "lorem ipsum dolor"
},
SolrInputDocument {
...
},
...
]
}
It clearly doesn't like the field `pages` which isn't defined in the
schema, but reading the various documen
t" in order to get the root document that contains
the children that match our conditions (in fq).
for example:
fq = {!parent which='doc_type:root'}(+doc_type=child_doc +doc_body:word)
fl=*.[child limit=-1].
We got the full document with the all nested documents in result, but th
Hi,
I want to use update Processor of solr, on nested fields,
for example:
Use UniqFieldsUpdateProcessorFactory, on field: "subject" in documents:
{
"id":"dsaewqhgfytr",
"lecturers":[
{
"id":"dsaewqhgfytr.dsadsa321321dsa",
"subject":"english"
},
{
"id":"dsaewqhgfytr.dsadsa321321ewq",
"subject":"mat
n improvement for [child] .
>>
>> Will try this out.
>>
>> On Sat, Oct 30, 2021 at 1:37 PM govind nitk
>> wrote:
>>
>>> Hi,
>>>
>>> I am using edismax parser for querying parent documents. With [child ]
>>> transformer, I am able
parser for querying parent documents. With [child ]
>> transformer, I am able to get the child/nested documents of matching
>> parents.
>>
>> But I am curious to know any way to user queryfields for child docs?
>>
>> For example, q= A B C
>> I am trying to g
o get the child/nested documents of matching
> parents.
>
> But I am curious to know any way to user queryfields for child docs?
>
> For example, q= A B C
> I am trying to get child documents matching these query words ( at least 1
> or all).
> How to get querying on child docs
Hi,
I am using edismax parser for querying parent documents. With [child ]
transformer, I am able to get the child/nested documents of matching
parents.
But I am curious to know any way to user queryfields for child docs?
For example, q= A B C
I am trying to get child documents matching these
ts welcome.
-Original Message-
From: Manoj Mokashi
Sent: Friday, June 18, 2021 4:17 PM
To: users@solr.apache.org
Subject: RE: Nested documents mixup with block join query parent mask
A similar problem is seen with the parents parser, children belonging to other
nodes sometimes appear as c
@solr.apache.org
Subject: Nested documents mixup with block join query parent mask
Hi,
I am using solr 8.6.2
I have the following doc types marked by a type attribute :
TR -> has child doc -> IN
PB -> has child doc -> AU
So the type IN docs exist only under TR and type AU only under PB
But when I
Hi,
I am using solr 8.6.2
I have the following doc types marked by a type attribute :
TR -> has child doc -> IN
PB -> has child doc -> AU
So the type IN docs exist only under TR and type AU only under PB
But when I run a query like type:IN AND {!child of='type:PB'}type:PB, I get a
subset of IN
Hi Adi,
I am having solr 8.8. I have implemented nested documents with _root_
stored=true and _nest_path_. Partial update is failing for me. It works once
when I restart solr and fails subsequent partial updates again till next
restart. It fails with Error 500: "msg":"Did not fi
Version: Solr 8.8.0
I have a core having nested documents. I am trying to do partial update on
parent document. It works for the first time and fails after that, and
needs restart to do partial update again.
(Note: Normal update works fine. Partial update works fine when I don't
have n
}
},
{
"match": {
"level2.field4": "mqnmnq"
}
}
]
}
Hello Alain,
If I was going to implement queries on deeply nested documents, I can see
quite a few examples here :
https://solr.apache.org/guide/8_8/searching-nested-documents.html#parent-query-parser
In a hierarchy like below the following query with a criteria on
_nest_path_ suppose to
d there is some Event where event.item1='..' and
> > event.item2='..' and there is some ActionPlan that has an Objective where
> > Objective.item3='..' and this Objective has an Action where
> > Action.item1='..' and Action.item2='..'
and
> event.item2='..' and there is some ActionPlan that has an Objective where
> Objective.item3='..' and this Objective has an Action where Action.item1='..'
> and Action.item2='..'
>
> This is fairly trivial in a relational DB. But is it achieva
re is some ActionPlan that has an Objective where
> > > Objective.item3='..' and this Objective has an Action where
> > > Action.item1='..' and Action.item2='..'
> > >
> > > This is fairly trivial in a relational DB.
t; Profile.item1='...' and there is some Event where event.item1='..' and
> > > event.item2='..' and there is some ActionPlan that has an Objective where
> > > Objective.item3='..' and this Objective has an Action where
> > > Action.item1=
.' and there is some ActionPlan that has an Objective where
> > Objective.item3='..' and this Objective has an Action where
> > Action.item1='..' and Action.item2='..'
> >
> > This is fairly trivial in a relational DB. But is it achieva
Hi,
Thanks, I knew about that one, but note the date : 2012. A lot has changed in
the meantime, specifically block joins and improved nested documents support.
But I wonder about what can be expressed, even if we leave performance issues
aside for another post. I can't find a comprehe
1='..' and
> event.item2='..' and there is some ActionPlan that has an Objective where
> Objective.item3='..' and this Objective has an Action where
> Action.item1='..' and Action.item2='..'
>
> This is fairly trivial in a relati
'
This is fairly trivial in a relational DB. But is it achievable in Solr ?
Needless to say, there is no way a flat schema can work here. So I have assumed
that nested documents were the only way to go. I have created a schema that
includes these prerequisites, where "docType" i
49 matches
Mail list logo
