You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2014/10/31 08:06:33 UTC
[jira] [Resolved] (OAK-2240) Support for indexing relative
properties
[ https://issues.apache.org/jira/browse/OAK-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chetan Mehrotra resolved OAK-2240.
----------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.2)
1.1.2
Merged to 1.0 branch in http://svn.apache.org/r1635708
> Support for indexing relative properties
> ----------------------------------------
>
> Key: OAK-2240
> URL: https://issues.apache.org/jira/browse/OAK-2240
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: oak-lucene
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: 1.0.8, 1.1.2
>
> Attachments: LuceneIndexEditor.java.patch, OAK-2240-test-rm.patch, OAK-2240.patch
>
>
> Lucene property index needs to support following queries which make use of relative properties
> {noformat}
> select [jcr:path], [jcr:score], * from [dam:Asset] as a
> where [jcr:content/jcr:lastModified] > cast('2014-10-01T00:00:00.000+02:00' as date)
> {noformat}
> Possible Approach
> # Have the index definition define a property like foo/bar
> # LuceneIndexEditor would also index child property foo/bar as part of parent node if present
> # On update in child the child node can indicate the parent to make the document again
> # On query side the property restriction can be used listerall i.e. foo/bar and stuff should work fine
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)