[jira] [Updated] (OAK-6792) rep:facet not supported in xpath
[
https://issues.apache.org/jira/browse/OAK-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Saurabh updated OAK-6792:
---
Labels: (was: candidate_oak_1_4)
> rep:facet not supported in xpath
>
>
> Key: OAK-6792
> URL: https://issues.apache.org/jira/browse/OAK-6792
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Fix For: 1.8, 1.4.19, 1.7.10, 1.6.7
>
>
> Parsing
> {noformat}
> //element(*, app:Asset)/(rep:facet(jcr:createdBy))
> {noformat}
> gives following exception.
> {noformat}
> Caused by: java.text.ParseException: Query:
> /jcr_root//element(*, app:Asset)/rep:facet(jcr:createdBy(*))
> {noformat}
> /cc [~tmueller]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6750) Lucene facets don't work with relative properties
[
https://issues.apache.org/jira/browse/OAK-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Saurabh updated OAK-6750:
---
Fix Version/s: 1.4.19
> Lucene facets don't work with relative properties
> -
>
> Key: OAK-6750
> URL: https://issues.apache.org/jira/browse/OAK-6750
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Fix For: 1.8, 1.7.9, 1.4.19, 1.6.7
>
> Attachments: OAK-6750-testCase.patch
>
>
> Facets currently work only when faceted dimension is direct property of
> selected node e.g.
> {noformat}
> select \[jcr:path], \[rep:facet(jc/text)] from \[nt:base] where ...
> {noformat}
> doesn't work but
> {noformat}
> select \[jcr:path], \[rep:facet(text)] from \[nt:base] where ...
> {noformat}
> works (assume correct index defs).
> The issue is that {{ast/SelectorImpl#currentOakProperty}} check if
> {{rep:facet(jc/text)}} is a relative path or not and incorrectly 'feels' that
> it indeed is - it then proceeds ahead to traverse down a tree with elements
> \[{{rep:facet(jc}}, {{text)}}\] which makes no sense.
> /cc [~teofili], [~tmueller]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6792) rep:facet not supported in xpath
[
https://issues.apache.org/jira/browse/OAK-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Saurabh updated OAK-6792:
---
Fix Version/s: 1.4.19
> rep:facet not supported in xpath
>
>
> Key: OAK-6792
> URL: https://issues.apache.org/jira/browse/OAK-6792
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Fix For: 1.8, 1.4.19, 1.7.10, 1.6.7
>
>
> Parsing
> {noformat}
> //element(*, app:Asset)/(rep:facet(jcr:createdBy))
> {noformat}
> gives following exception.
> {noformat}
> Caused by: java.text.ParseException: Query:
> /jcr_root//element(*, app:Asset)/rep:facet(jcr:createdBy(*))
> {noformat}
> /cc [~tmueller]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6750) Lucene facets don't work with relative properties
[
https://issues.apache.org/jira/browse/OAK-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Saurabh updated OAK-6750:
---
Labels: (was: candidate_oak_1_4)
> Lucene facets don't work with relative properties
> -
>
> Key: OAK-6750
> URL: https://issues.apache.org/jira/browse/OAK-6750
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Fix For: 1.8, 1.7.9, 1.4.19, 1.6.7
>
> Attachments: OAK-6750-testCase.patch
>
>
> Facets currently work only when faceted dimension is direct property of
> selected node e.g.
> {noformat}
> select \[jcr:path], \[rep:facet(jc/text)] from \[nt:base] where ...
> {noformat}
> doesn't work but
> {noformat}
> select \[jcr:path], \[rep:facet(text)] from \[nt:base] where ...
> {noformat}
> works (assume correct index defs).
> The issue is that {{ast/SelectorImpl#currentOakProperty}} check if
> {{rep:facet(jc/text)}} is a relative path or not and incorrectly 'feels' that
> it indeed is - it then proceeds ahead to traverse down a tree with elements
> \[{{rep:facet(jc}}, {{text)}}\] which makes no sense.
> /cc [~teofili], [~tmueller]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6792) rep:facet not supported in xpath
[
https://issues.apache.org/jira/browse/OAK-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16239374#comment-16239374
]
Vikas Saurabh commented on OAK-6792:
Backported to 1.4 at [r1814334|https://svn.apache.org/r1814334].
> rep:facet not supported in xpath
>
>
> Key: OAK-6792
> URL: https://issues.apache.org/jira/browse/OAK-6792
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Labels: candidate_oak_1_4
> Fix For: 1.8, 1.4.19, 1.7.10, 1.6.7
>
>
> Parsing
> {noformat}
> //element(*, app:Asset)/(rep:facet(jcr:createdBy))
> {noformat}
> gives following exception.
> {noformat}
> Caused by: java.text.ParseException: Query:
> /jcr_root//element(*, app:Asset)/rep:facet(jcr:createdBy(*))
> {noformat}
> /cc [~tmueller]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (OAK-6750) Lucene facets don't work with relative properties
[
https://issues.apache.org/jira/browse/OAK-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16235281#comment-16235281
]
Vikas Saurabh edited comment on OAK-6750 at 11/5/17 3:46 AM:
-
Backported to 1.6 at [r1814034|https://svn.apache.org/r1814034] and to 1.4 at
[r1814334|https://svn.apache.org/r1814334].
was (Author: catholicon):
Backported to 1.6 at [r1814034|https://svn.apache.org/r1814034].
> Lucene facets don't work with relative properties
> -
>
> Key: OAK-6750
> URL: https://issues.apache.org/jira/browse/OAK-6750
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Labels: candidate_oak_1_4
> Fix For: 1.8, 1.7.9, 1.6.7
>
> Attachments: OAK-6750-testCase.patch
>
>
> Facets currently work only when faceted dimension is direct property of
> selected node e.g.
> {noformat}
> select \[jcr:path], \[rep:facet(jc/text)] from \[nt:base] where ...
> {noformat}
> doesn't work but
> {noformat}
> select \[jcr:path], \[rep:facet(text)] from \[nt:base] where ...
> {noformat}
> works (assume correct index defs).
> The issue is that {{ast/SelectorImpl#currentOakProperty}} check if
> {{rep:facet(jc/text)}} is a relative path or not and incorrectly 'feels' that
> it indeed is - it then proceeds ahead to traverse down a tree with elements
> \[{{rep:facet(jc}}, {{text)}}\] which makes no sense.
> /cc [~teofili], [~tmueller]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6900) Build Jackrabbit Oak #940 failed
[ https://issues.apache.org/jira/browse/OAK-6900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16239367#comment-16239367 ] Hudson commented on OAK-6900: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #946|https://builds.apache.org/job/Jackrabbit%20Oak/946/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/946/console] > Build Jackrabbit Oak #940 failed > > > Key: OAK-6900 > URL: https://issues.apache.org/jira/browse/OAK-6900 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Trivial > > No description is provided > The build Jackrabbit Oak #940 has failed. > First failed run: [Jackrabbit Oak > #940|https://builds.apache.org/job/Jackrabbit%20Oak/940/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/940/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OAK-6792) rep:facet not supported in xpath
[
https://issues.apache.org/jira/browse/OAK-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16239349#comment-16239349
]
Vikas Saurabh edited comment on OAK-6792 at 11/5/17 2:37 AM:
-
Updated fix on trunk at [r1814332|https://svn.apache.org/r1814332] and on 1.6
at [r1814333|https://svn.apache.org/r1814333].
was (Author: catholicon):
Updated fix on trunk at [r1814332|https://svn.apache.org/r1814332].
> rep:facet not supported in xpath
>
>
> Key: OAK-6792
> URL: https://issues.apache.org/jira/browse/OAK-6792
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Labels: candidate_oak_1_4
> Fix For: 1.8, 1.7.10, 1.6.7
>
>
> Parsing
> {noformat}
> //element(*, app:Asset)/(rep:facet(jcr:createdBy))
> {noformat}
> gives following exception.
> {noformat}
> Caused by: java.text.ParseException: Query:
> /jcr_root//element(*, app:Asset)/rep:facet(jcr:createdBy(*))
> {noformat}
> /cc [~tmueller]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6792) rep:facet not supported in xpath
[
https://issues.apache.org/jira/browse/OAK-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16239349#comment-16239349
]
Vikas Saurabh commented on OAK-6792:
Updated fix on trunk at [r1814332|https://svn.apache.org/r1814332].
> rep:facet not supported in xpath
>
>
> Key: OAK-6792
> URL: https://issues.apache.org/jira/browse/OAK-6792
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Labels: candidate_oak_1_4
> Fix For: 1.8, 1.7.10, 1.6.7
>
>
> Parsing
> {noformat}
> //element(*, app:Asset)/(rep:facet(jcr:createdBy))
> {noformat}
> gives following exception.
> {noformat}
> Caused by: java.text.ParseException: Query:
> /jcr_root//element(*, app:Asset)/rep:facet(jcr:createdBy(*))
> {noformat}
> /cc [~tmueller]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6792) rep:facet not supported in xpath
[
https://issues.apache.org/jira/browse/OAK-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16239346#comment-16239346
]
Vikas Saurabh commented on OAK-6792:
Talked to [~tmueller] offline, and the patch above (which works on 1.4) is
preferable. I would hence apply it on trunk and on 1.6 too (i.e. undo the
previous change and put this one in).
> rep:facet not supported in xpath
>
>
> Key: OAK-6792
> URL: https://issues.apache.org/jira/browse/OAK-6792
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
> Labels: candidate_oak_1_4
> Fix For: 1.8, 1.7.10, 1.6.7
>
>
> Parsing
> {noformat}
> //element(*, app:Asset)/(rep:facet(jcr:createdBy))
> {noformat}
> gives following exception.
> {noformat}
> Caused by: java.text.ParseException: Query:
> /jcr_root//element(*, app:Asset)/rep:facet(jcr:createdBy(*))
> {noformat}
> /cc [~tmueller]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OAK-6905) Query enging: support coalesce function as in-built method
Vikas Saurabh created OAK-6905:
--
Summary: Query enging: support coalesce function as in-built method
Key: OAK-6905
URL: https://issues.apache.org/jira/browse/OAK-6905
Project: Jackrabbit Oak
Issue Type: Improvement
Components: core, lucene, query
Reporter: Vikas Saurabh
Assignee: Vikas Saurabh
Priority: Normal
Fix For: 1.8
Sometimes the content structure stores semantically similar properties at
different locations (due to content evolution or different locations genuinely
represent different values).
e.g. say a content represent a real world image as
{{/file1.jpg/jcr:content/file}}. Where {{jcr:content/metadata/exif:title}}
could be title of image from exif data, {{jcr:content/jcr:title}} could be
title explicitly set by user.
While displaying a title, it probably makes sense to show {{jcr:title}} first
and fallback to {{exif:title}} and then probaly to node name if nothing else
works out.
it'd would be useful to have such overlaying be conveyed to query engine too
for lookup, ordering (and, of course, indexing). As a method name, sql colesce
is exactly what should serve this purpose.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
