On Mon, Nov 30, 2015 at 11:47 PM, <solr-user-digest-h...@lucene.apache.org> wrote:
> > I'd happy that it helps. You need to thank Varun who made [child]. There is > no performance impact for sure, it's a compromise or either nobody > considered it as an issue. You can raise a new JIRA and describe how it > should work in general and make everybody happy. On top of my head are > SOLR-8208 <https://issues.apache.org/jira/browse/SOLR-8208> and SOLR-7672 > <https://issues.apache.org/jira/browse/SOLR-7672> which may interfere with > it. So, report your vision. @Varun++ ! Thanks for ChildDocTransformerFactory. As for my vision, it is not ready. But a big part of it will be clear syntax in JSON format. Right now we have a mix of JSON, SQL-like ANDs and Ors, and 'corename/query/?q=foo&' query format. Thanks for mentioning the open issues. SOLR-7672 <https://issues.apache.org/jira/browse/SOLR-7672> : we will only use two-level nesting, parent and child (famous last words!). Yes, parameters should be implicit when they are required. SOLR-6700 <https://issues.apache.org/jira/browse/SOLR-6700> : this might just force me to do explicit deletes. The issue is stale, maybe fixed? I will be testing, certainly. SOLR-8208 <https://issues.apache.org/jira/browse/SOLR-8208> : I do not understand this. Will you be changing the syntax? cheers -- Rick
