Re: Why is nt:resource referencable?

2016-07-20 Thread Chetan Mehrotra
On Wed, Jul 20, 2016 at 2:49 PM, Bertrand Delacretaz wrote: > but the JCR spec (JSR 283 10 August 2009) only has > > [nt:resource] > mix:mimeType, mix:lastModified > primaryitem jcr:data > - jcr:data (BINARY) mandatory Thats interesting. Did not knew its not

Re: Why is nt:resource referencable?

2016-07-20 Thread Marcel Reutegger
Hi, On 20/07/16 12:53, Chetan Mehrotra wrote: What if we do not add any mixin and just have jcr:uuid property present. The node would anyway be indexed so search would still work. that only works to some degree. there would be no property definition for the jcr:uuid property and should be

Re: Why is nt:resource referencable?

2016-07-20 Thread Marcel Reutegger
Hi, On 20/07/16 11:41, Chetan Mehrotra wrote: @Marcel - I did not understood JCR-2170 properly. But any chance we can switch to newer version of nt:resource and do not modify existing nodes and let the new definition effect/enforced only on new node. node types are not versioned, which means

Re: Why is nt:resource referencable?

2016-07-20 Thread Chetan Mehrotra
On Wed, Jul 20, 2016 at 4:04 PM, Marcel Reutegger wrote: > Maybe we would keep the jcr:uuid property on the referenceable node and add > the mixin? What if we do not add any mixin and just have jcr:uuid property present. The node would anyway be indexed so search would still

Re: Why is nt:resource referencable?

2016-07-20 Thread Angela Schreiber
Hi Bertrand It used to be mix:referenceable in JSR170 (i.e. JCR 1.0) and we kept it for backwards compatibility: https://docs.adobe.com/content/docs/en/spec/jcr/1.0/6.7.22.9_nt_resource.ht ml So, adding oak:Resource sounds the right thing to do here. Kind regards Angela On 20/07/16 11:19,

OAK SOLR re-index via index manager UI

2016-07-20 Thread sri vaths
Hi,We are not able to see the solr index for an re-index trigger via AEM 6.1 tools UI OAK index manager /libs/granite/operations/content/diagnosis/tool.html/_granite_oakindexmanager will the above UI only pick the direct index configuration under the /oak:index root node. We have placed the

Re: Internals of Apache Jackrabbit OAK repository & OOTB SOLR indexing

2016-07-20 Thread sri vaths
Thanks Michael for the slide share links will look into it. On Wednesday, 20 July 2016 12:33 PM, sri vaths wrote: Hi All, Please share details on how OAK repository triggers node updates to SOLR for indexing, guessing it based on the OAK NodeState model but not

Re: OAK SOLR re-index via index manager UI

2016-07-20 Thread Tommaso Teofili
Hi Sri, Index Manager is not part of Apache Jackrabbit Oak, so this is not the proper channel to get answers on that topic. Regards, Tommaso Il giorno mer 20 lug 2016 alle ore 11:54 sri vaths ha scritto: > Hi,We are not able to see the solr index for an re-index

Re: Why is nt:resource referencable?

2016-07-20 Thread Angela Schreiber
Hi Chetan I would not do that even if it was possible as it will break every single application that relies on nt:resource to extend from mix:referenceable... these applications would need to change their code adding the mixin manually which may lead to follow up issues, because adding a mixin by

Re: Internals of Apache Jackrabbit OAK repository & OOTB SOLR indexing

2016-07-20 Thread Michael Marth
Hi, Are you aware of this docu: http://jackrabbit.apache.org/oak/docs/query/solr.html ? It points to some of the relevant classes. Cheers Michael On 20/07/16 09:03, "sri vaths" wrote: >Hi All, >Please share details on how OAK repository triggers node updates

Re: Oak 1.5.6 release plan

2016-07-20 Thread Davide Giannella
On 19/07/2016 11:45, Davide Giannella wrote: > Hello team, > > I'm planning to cut Oak 1.5.6 today in the afternoon british time. > > I've been trying quite long but the upload process always fails on various module with HTTP timeout. Probably a network issue on my side. Should have already

Why is nt:resource referencable?

2016-07-20 Thread Bertrand Delacretaz
Hi, OAK-4567 introduces a new oak:Resource nodetype as an alternative to nt:resource which has mix:referenceable. I understand the idea of making that node non-referencable for performance reasons, but why is nt:resource referenceable in the first place? builtin_nodetypes.cnd [1] has this

Re: Internals of Apache Jackrabbit OAK repository & OOTB SOLR indexing

2016-07-20 Thread Michael Marth
Some presentations that might also be of interest in this context: http://de.slideshare.net/teofili/oak-solr-integration http://de.slideshare.net/teofili/scaling-search-in-oak-with-solr http://de.slideshare.net/teofili/flexible-search-oakmin Cheers Michael On 20/07/16 09:55, "Michael Marth"

Internals of Apache Jackrabbit OAK repository & OOTB SOLR indexing

2016-07-20 Thread sri vaths
Hi All, Please share details on how OAK repository triggers node updates to SOLR for indexing, guessing it based on the OAK NodeState model but not sure how the flow happens.http://jackrabbit.apache.org/oak/docs/architecture/nodestate.html  And also want to know the list of node states the index

Re: Why is nt:resource referencable?

2016-07-20 Thread Angela Schreiber
Hi Chetan That would be really troublesome for multiple reasons. First of all nt:resource doesn't allow for residual properties as it comes with defined set of property definitions. So, any attempt to write a jcr:uuid property to such a node will fail. Second, for other nodes that allow for