[ 
https://issues.apache.org/jira/browse/OAK-9808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Angela Fabregues updated OAK-9808:
----------------------------------
    Description: 
The allProps and any other property accepting regex in the name would require 
the definition of the field in the index at ingestion time. The field cannot be 
defined at index creation because its name is unknown.

Elasticsearch supports the definition of customised dynamic fields. Using 
dynamic templates, we can avoid the Elasticsearch type guessing and take 
advantage of knowing the field type and its properties at ingestion time.

This task consists on supporting allProps and other regex.

*Acceptance Criteria*

All tests are passed, tests working with allProps are added and passed.

  was:
The allProps and any other property accepting regex in the name would require 
the definition of the field in the index at ingestion time. The field cannot be 
defined at index creation because its name is unknown.

Elasticsearch supports the definition of customised dynamic fields. Using 
dynamic templates, we can avoid the Elasticsearch type guessing and take 
advantage of knowing the field type and its properties at ingestion time.

The solution is described in the wiki: 
[https://wiki.corp.adobe.com/display/WEM/OAK+Search+Elastic+index+mapping,]

This task consists on supporting allProps and other regex.

*Acceptance Criteria*

All tests are passed, tests working with allProps are added and passed.


> oak-search-elastic: supporting allProps
> ---------------------------------------
>
>                 Key: OAK-9808
>                 URL: https://issues.apache.org/jira/browse/OAK-9808
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>            Reporter: Angela Fabregues
>            Priority: Major
>
> The allProps and any other property accepting regex in the name would require 
> the definition of the field in the index at ingestion time. The field cannot 
> be defined at index creation because its name is unknown.
> Elasticsearch supports the definition of customised dynamic fields. Using 
> dynamic templates, we can avoid the Elasticsearch type guessing and take 
> advantage of knowing the field type and its properties at ingestion time.
> This task consists on supporting allProps and other regex.
> *Acceptance Criteria*
> All tests are passed, tests working with allProps are added and passed.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to