AEM 6.1 + Solr OOTB indexing

[varshsr]

While using AEM 6.1 + Solr OOTB indexing , for a page or dam content 

The parent and child nodes are getting indexed as separate document with path_exact is document id

example as seen today on AEM 6.1

Solr doc1 - /content/sample/jcr:content

Solr doc2 - /content/sample/jcr;content/par

Solr doc3 - /content/dam/sample/test.pdf

Solr doc4 - /content/dam/sample/test.pdf/jcr:content

Solr doc4 - /content/dam/sample/test.pdf/jcr:content/metadata

This is not allowing direct SOLR web API queries to get the related the documents in 1 json and those contents which are only ACTIVATED (as this is in parent node)

Is there a possibility to index the SOLR document as like this ( with entire child node with a possible control over the child depth ) 

Solr doc- expected for content

 - /content/sample/jcr:content

       child  - /content/sample/jcr;content/par

Solr doc - expected for dam

 /content/dam/sample/test.pdf

   child - /content/dam/sample/test.pdf/jcr:content

   child -  /content/dam/sample/test.pdf/jcr:content/metadata

Any thoughts / pointers from AEM + SOLR team will help us

with regards

Sri

[smacdonald2008]

This week, a lot of the team is at Adobe Marketing summit. Take a look at this GEMs session to see if it helps you.  http://dev.day.com/content/ddc/en/gems/oak-lucene-indexes.html

[varshsr]

Thanks Scott , Is there similar available for SOLR index and i also wanted to know why Solr indexing is not a single document on remote SOLR with the required parent and child node properties?

As of now (AEM 6.1 + OOTB remote SOLR) all the child nodes are kept as individual SOLR document (path_exact key is unique)and with out any to association the parent node

Was expecting a possible dump of jcr:content tree with possible filters to the properties so that the entire content tree can be indexed accordingly while using SOLR web API query - http://localhost:8983/solr/oak/select?indent=on&q=*:*&wt=json to directly fetch the content from SOLR without any jcr queries

as an example seeing these 2 documents doc1 - {"path_exact":"/GeoSphere_Datasheet.pdf/jcr:content/metadata"}

doc2 - {"path_exact":"/GeoSphere_Datasheet.pdf/jcr:content/"}

instead expecting a single document of the entire update tree with parent child relationship

doc1 - { "path_exact":"/GeoSphere_Datasheet.pdf/jcr:content/",

                    {

                      "child":"/GeoSphere_Datasheet.pdf/jcr:content/metadata"

                   }

}

}