[
https://issues.apache.org/jira/browse/OAK-11555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller updated OAK-11555:
---------------------------------
Description:
Right now properties such as "first.name" and functions such as
"upper([first.name])" are not supported.
There seems to be no proper documentation on the exact restrictions for field
names.
According to the Elasticsearch documentation, field names starting with "_" are
reserved:
https://discuss.elastic.co/t/field-names-starting-with-underscore-are-not-matched-with-wildcard/221254/2
"We are using indeed _ prefix for metadata fields like _index, _id ... So I'd
not use this prefix."
https://discuss.elastic.co/t/index-name-type-name-and-field-name-rules/133039/2
"I believe the only restriction on field names is that it can't be entirely
whitespace. Periods are allowed, but they are short-hand for objects. E.g."
was:
Right now properties such as "first.name" and functions such as
"upper([first.name])" are not supported.
According to the Elasticsearch documentation, field names starting with "_" are
reserved:
https://discuss.elastic.co/t/field-names-starting-with-underscore-are-not-matched-with-wildcard/221254/2
"We are using indeed _ prefix for metadata fields like _index, _id ... So I'd
not use this prefix."
> Elastic: support dot and other special characters in property and function
> names
> --------------------------------------------------------------------------------
>
> Key: OAK-11555
> URL: https://issues.apache.org/jira/browse/OAK-11555
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Major
>
> Right now properties such as "first.name" and functions such as
> "upper([first.name])" are not supported.
> There seems to be no proper documentation on the exact restrictions for field
> names.
> According to the Elasticsearch documentation, field names starting with "_"
> are reserved:
> https://discuss.elastic.co/t/field-names-starting-with-underscore-are-not-matched-with-wildcard/221254/2
> "We are using indeed _ prefix for metadata fields like _index, _id ... So
> I'd not use this prefix."
> https://discuss.elastic.co/t/index-name-type-name-and-field-name-rules/133039/2
> "I believe the only restriction on field names is that it can't be entirely
> whitespace. Periods are allowed, but they are short-hand for objects. E.g."
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
