check out the videos on this website TROO.TUBE don't be such a
sheep/zombie/loser/NPC. Much love!
https://troo.tube/videos/watch/aaa64864-52ee-4201-922f-41300032f219
On Tue, May 5, 2020 at 8:32 PM mmb1234 wrote:
>
> I am running into a exception where creating child docs fails unless
I am running into a exception where creating child docs fails unless the
field already exists in the schema (stacktrace is at the bottom of this
post). My solr is v8.5.1 running in standard/non-cloud mode.
$> curl -X POST -H 'Content-Type: application/json'
'http://localhos
Hello, John.
The choice is guided by the form of search results. You need to ask what
you need to paginate, count numFound. You need to index as top level docs
what you need to find.
On Thu, Mar 7, 2019 at 9:08 PM John Blythe wrote:
> hi all!
>
> curious about how child docs and pe
sted docs have quite a number of “gotchas”.
>
> If you really need nested docs, your first option would require the entire
> “platonic” parent and all child docs to be re-indexed every time, so I’d go
> with 2 for that reason alone.
>
> Best,
> Erick
>
> > O
tchas”.
If you really need nested docs, your first option would require the entire
“platonic” parent and all child docs to be re-indexed every time, so I’d go
with 2 for that reason alone.
Best,
Erick
> On Mar 7, 2019, at 10:08 AM, John Blythe wrote:
>
> hi all!
>
> curious abou
hi all!
curious about how child docs and performance interact.
i'll have a bunch of transactions coming in from various entities. i'm
debating nesting them all under a single, 'master' parent entity or to have
the parent and children be entity specific.
so either:
[platon
Mikhail,
Actually, your suggestion worked! I was making a typo on the field name. Thank
you very much!
TK
p.s. I have found a mention of _query_ "magic field" in the Solr Reference Guide
On 7/8/18 11:04 AM, TK Solr wrote:
Thank you.
This is more promising because I see the second clause i
Thank you.
This is more promising because I see the second clause in parsedquery. But it is
hitting zero document.
The debug query output looks like this. explain is empty:
rawquerystring":"_query_:{!parent which=\"isParent:true\" v='attrname:genre AND
attrvalue:drama'} AND _query_:{!parent
agh... It's my pet peeve.
what about
q= {!parent which="isParent:true" v='attrname:genre AND attrvalue:drama'}
AND {!parent which="isParent:true" v='attrname:country AND attrvalue:USA'}
^leading space
q=_query_:{!parent which="isParent:true" v='attrname:genre AND
attrvalue:drama'} AND _query_:{!pa
Thank you, Mikhail. But this didn't work. The first {!parent which='...'
v='...'} alone works. But the second {!parent ...} clause is completely ignored.
In fact, if I turn on debugQuery, rawquerystring and querystring have the second
query but parsedquery and parsedquery_toString only have the f
Hello,
q={!parent which="isParent:true" v='attrname:genre AND attrvalue:drama'} AND
{!parent which="isParent:true" v='attrname:country AND attrvalue:USA'}
On Tue, Jul 3, 2018 at 3:35 PM TK Solr wrote:
> I have a document with child documents like:
>
>
> maindoc_121
> true
> c
I have a document with child documents like:
maindoc_121
true
child_121_1
genre
drama
child_121_2
country
USA
The child documents have the same set of fields.
I can write a query that has a child which has attrname=genre and
to fq makes query return child docs instead of parent
docs
On 6/26/2018 7:22 AM, Florian Fankhauser wrote:
> Now for some reason I want to exclude the above filter-query from a
> facet-query. Therefore I need to add a tag to the filter-query:
>
> q={!tag=datefilter}{!parent which=doc
On 6/26/2018 7:22 AM, Florian Fankhauser wrote:
Now for some reason I want to exclude the above filter-query from a
facet-query. Therefore I need to add a tag to the filter-query:
q={!tag=datefilter}{!parent which=doc_type_s:book} acquisition_date_i:20180626
According to the documentati
Hello,
given the following document structure (books as parent, libraries having these
books as children) in a Solr 7.3.1 server:
book
1000
Mr. Mercedes
Stephen King
library
1000/100
ath__str":["p.1"]}]}]
>}
> ]}
>
> And I made a query similar to what you did: _query_:"{!parent
> which=_level_:0}size:M" AND _query_:"{!parent which=_level_:0}size:M"
>
> This document would match. So I'm asking for a different scena
ersion_":1591607734461005824,
"_path__str":["p.1"]}]}]
}
]}
And I made a query similar to what you did: _query_:"{!parent
which=_level_:0}size:M" AND _query_:"{!parent which=_level_:0}size:M"
This document would match. So I'm aski
q=+{!parent .. v=$m} +{!parent .. v=$l}&m=size:(+M -L)&l=size:(+L -M)
On Sun, Feb 4, 2018 at 10:56 PM, SuperMattio86
wrote:
> Hello.
>
> As a toy example, let's assume I have documents that looks like this:
>
> {
> "id": "1",
> "_childDocuments_": [
> {
> "id": "1_2",
>
Hello.
As a toy example, let's assume I have documents that looks like this:
{
"id": "1",
"_childDocuments_": [
{
"id": "1_2",
"_path_": "p.1",
"size": "M",
"color": "red"
},
{
"id": "23lk4d23lkj",
"_path_": "p.2",
"si
context:
http://lucene.472066.n3.nabble.com/Search-across-nested-child-docs-tp4304956p4305105.html
Sent from the Solr - User mailing list archive at Nabble.com.
Giving 'across two child docs', I think you are looking for
fq={!parent which=PARENT_DOC_TYPE:PARENT}childA_field_1:432&fq={!parent
which=PARENT_DOC_TYPE:PARENT}childA_field_2:6
On Mon, Nov 7, 2016 at 9:45 PM, Vinod Singh wrote:
> I have nested documents indexed in SOLR 6.
I have nested documents indexed in SOLR 6.2. The block join query works well
on both parent and child documents. My use case has a scenario where a
condition needs to be fulfilled across two child docs as shown below -
fq={!parent which=PARENT_DOC_TYPE:PARENT}(childA_field_1:432 AND
Now I'm trying to sort the children by normal field and not by function
values.
Is there any way to do so?
Thanks,
Dor
--
View this message in context:
http://lucene.472066.n3.nabble.com/Sorting-documents-by-nested-child-docs-with-FunctionQueries-tp4209940p4216169.html
Sent from the
t; 20
> parent
> Nike
>
> 21
> Red
> M
>
>
> 22
> Blue
> XL
> XXL
>
>
>
> 30
> parent
> Puma
>
> 31
31
Red
XL
32
Blue
M
On Mon, Jun 22, 2015 at 2:04 PM, Maya G wrote:
> I've tried your solution and encountered a problem.
>
> My child document has a multi-valued field.
>
> When I query the doc by its' guid, all of the field's values are returned.
> When I use the join block query only one value is returned for the
> multi-value field.
>
> Do you have any suggestions?
> Thank you,
> Maya
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Sorting-documents-by-nested-child-docs-with-FunctionQueries-tp4209940p4213242.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
--
Sincerely yours
Mikhail Khludnev
Principal Engineer,
Grid Dynamics
<http://www.griddynamics.com>
gestions?
Thank you,
Maya
--
View this message in context:
http://lucene.472066.n3.nabble.com/Sorting-documents-by-nested-child-docs-with-FunctionQueries-tp4209940p4213242.html
Sent from the Solr - User mailing list archive at Nabble.com.
> >> *
> >> * This is just an example, the schema and the data aren't real.*
> >>
> >> I want to analyze & run an algorithm on the comments text, then sort the
> >> parent documents by it - *This would work with FunctionQuery, if I had
> >> one
> >> c
uot;id": "CommentGuid2",
>> "content_type": "comment",
>> "text": "CommentText"
>> }
>> ]
>> }
>> *
>> * This is just an example, the schema and the data aren't real.*
>>
>>
comments text, then sort the
> parent documents by it - *This would work with FunctionQuery, if I had one
> comment for each article and didn't use child documents*.
> I tried to use the LeafReadContext to get the children, but with no luck.
>
> Is there any way to reach the chi
thm on the comments text, then sort the
parent documents by it - *This would work with FunctionQuery, if I had one
comment for each article and didn't use child documents*.
I tried to use the LeafReadContext to get the children, but with no luck.
Is there any way to reach the children through
30 matches
Mail list logo
