[ 
https://issues.apache.org/jira/browse/SOLR-12630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572689#comment-16572689
 ] 

mosh commented on SOLR-12630:
-----------------------------

{quote} Perhaps you mean to convey this idea: it'd be nice if the query method 
could work consistently using either "block" style doc addition or standalone 
docs (+ metadata to express relationships).  Internally somehow it should 
detect which mechanism is most efficient (use BlockJoin if possible).  This 
sounds hard; I'm not sure if this is even what you mean though. {quote}
This is actually exactly what I was going for, except perhaps we could let the 
user decide, or even have this set in the schema. Perhaps if the user has 
nested updates, this well be a lot more performant then indexing the whole 
block. Perhaps using the nested update URP we could add the needed metadata 
field(_ROOT_, _nest_path, _nest_parent) and index the doc in the same shard as 
the other children.
Would a nested field in schema with a type of block or shard make this simpler?
We could use the field type to determine which query or atomic update ought to 
be used in each scenario.
Again, just a thought.

> Query children without using block join
> ---------------------------------------
>
>                 Key: SOLR-12630
>                 URL: https://issues.apache.org/jira/browse/SOLR-12630
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: mosh
>            Priority: Major
>
> Currently work is being put into Solr to support nested document hierarchies, 
> keeping the original relation between parent and child docs 
> ([SOLR-12298|https://issues.apache.org/jira/browse/SOLR-12298], 
> [SOLR-12441|https://issues.apache.org/jira/browse/SOLR-12441]). Currently the 
> only way to query child documents is using BlockJoin. I was thinking perhaps 
> we could introduce a way to query documents that are not indexed in the same 
> block with a different transformer, or perhaps add this feature to the 
> ChildDocTransformer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to