[jira] [Comment Edited] (OAK-6201) Native Query syntax for rep:native unclear
[
https://issues.apache.org/jira/browse/OAK-6201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157472#comment-17157472
]
Konrad Windszus edited comment on OAK-6201 at 7/14/20, 3:56 PM:
A page for how JCR properties paths are translated to field names in Lucene and
Solr would be highly appreciated. [~teofili] Would you be able to come up with
something in the near future?
was (Author: kwin):
A page for how JCR properties are translated to field names in Lucene and Solr
would be highly appreciated. [~teofili] Would you be able to come up with
something in the near future?
> Native Query syntax for rep:native unclear
> --
>
> Key: OAK-6201
> URL: https://issues.apache.org/jira/browse/OAK-6201
> Project: Jackrabbit Oak
> Issue Type: Documentation
>Reporter: David Gonzalez
>Assignee: Tommaso Teofili
>Priority: Minor
>
> I was trying to perform a few test queries against an Oak 1.6.x repository
> using the XPath with the rep:native(..) function and but could not get any to
> work.
> I suspect my problem is with specifying the field, but i've tried a variety
> of permutations to no avail.
> For example, if tried to re-purpose the example XPath query to search over an
> asset's dc:title [1],
> Generally, i think the documentation [2] is lacking in that 1) unclear on the
> syntax 2) unclear if i need to do anything special to Oak indexes 3) if only
> the provided lucene index will service these requests (these are all from a
> lucene POV, rather than Solr, though assume all the same considerations apply)
> [1] Non-working: {code}
> //element(*, app:Asset)[(rep:native('lucene',
> 'jcr:contnet/metdata/dc:title:(Hello OR World)'))]
> {code}
> [2]
> http://jackrabbit.apache.org/oak/docs/query/query-engine.html#Native_Queries
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OAK-6201) Native Query syntax for rep:native unclear
[
https://issues.apache.org/jira/browse/OAK-6201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157472#comment-17157472
]
Konrad Windszus commented on OAK-6201:
--
A page for how JCR properties are translated to field names in Lucene and Solr
would be highly appreciated. [~teofili] Would you be able to come up with
something in the near future?
> Native Query syntax for rep:native unclear
> --
>
> Key: OAK-6201
> URL: https://issues.apache.org/jira/browse/OAK-6201
> Project: Jackrabbit Oak
> Issue Type: Documentation
>Reporter: David Gonzalez
>Assignee: Tommaso Teofili
>Priority: Minor
>
> I was trying to perform a few test queries against an Oak 1.6.x repository
> using the XPath with the rep:native(..) function and but could not get any to
> work.
> I suspect my problem is with specifying the field, but i've tried a variety
> of permutations to no avail.
> For example, if tried to re-purpose the example XPath query to search over an
> asset's dc:title [1],
> Generally, i think the documentation [2] is lacking in that 1) unclear on the
> syntax 2) unclear if i need to do anything special to Oak indexes 3) if only
> the provided lucene index will service these requests (these are all from a
> lucene POV, rather than Solr, though assume all the same considerations apply)
> [1] Non-working: {code}
> //element(*, app:Asset)[(rep:native('lucene',
> 'jcr:contnet/metdata/dc:title:(Hello OR World)'))]
> {code}
> [2]
> http://jackrabbit.apache.org/oak/docs/query/query-engine.html#Native_Queries
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OAK-9140) Don't use stored index definition in elastic indexes
[ https://issues.apache.org/jira/browse/OAK-9140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amrit Verma updated OAK-9140: - Description: Stored index definitions introduce additional complexities. Also, we are moving in a direction of avoiding index editing/re-indexing. New index definitions instead should be created instead. Re-indexing should be mostly done in case of corrupt indexes (which should not happen in elasticsearch). Hence we don't see a scenario in which indexed data would be incompatible with index definition, so we don't need stored index definitions for elastic indexes. > Don't use stored index definition in elastic indexes > > > Key: OAK-9140 > URL: https://issues.apache.org/jira/browse/OAK-9140 > Project: Jackrabbit Oak > Issue Type: Task > Components: indexing >Reporter: Amrit Verma >Priority: Major > > Stored index definitions introduce additional complexities. Also, we are > moving in a direction of avoiding index editing/re-indexing. New index > definitions instead should be created instead. Re-indexing should be mostly > done in case of corrupt indexes (which should not happen in elasticsearch). > Hence we don't see a scenario in which indexed data would be incompatible > with index definition, so we don't need stored index definitions for elastic > indexes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OAK-9140) Don
Amrit Verma created OAK-9140: Summary: Don Key: OAK-9140 URL: https://issues.apache.org/jira/browse/OAK-9140 Project: Jackrabbit Oak Issue Type: Task Reporter: Amrit Verma -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OAK-9140) Don't use stored index definition in elastic indexes
[ https://issues.apache.org/jira/browse/OAK-9140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amrit Verma updated OAK-9140: - Component/s: indexing > Don't use stored index definition in elastic indexes > > > Key: OAK-9140 > URL: https://issues.apache.org/jira/browse/OAK-9140 > Project: Jackrabbit Oak > Issue Type: Task > Components: indexing >Reporter: Amrit Verma >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OAK-9140) Don't use stored index definition in elastic indexes
[ https://issues.apache.org/jira/browse/OAK-9140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amrit Verma updated OAK-9140: - Summary: Don't use stored index definition in elastic indexes (was: Don) > Don't use stored index definition in elastic indexes > > > Key: OAK-9140 > URL: https://issues.apache.org/jira/browse/OAK-9140 > Project: Jackrabbit Oak > Issue Type: Task >Reporter: Amrit Verma >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
