Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Mappings editor] Add UI form for constant keyword datatype #69751

Closed
cjcenizal opened this issue Jun 23, 2020 · 1 comment · Fixed by #76564
Closed

[Mappings editor] Add UI form for constant keyword datatype #69751

cjcenizal opened this issue Jun 23, 2020 · 1 comment · Fixed by #76564
Labels
enhancement New value added to drive a business result Feature:Index Management Index and index templates UI Feature:Mappings Editor Index mappings editor UI Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more

Comments

@cjcenizal
Copy link
Contributor

Currently, the mappings editor does not have a UI form for the constant_keyword datatype (https://www.elastic.co/guide/en/elasticsearch/reference/master/constant-keyword.html).

We need to add this type to the type dropdown select and also create a form to support editing the parameters of this field.

@cjcenizal cjcenizal added enhancement New value added to drive a business result Feature:Index Management Index and index templates UI Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more Feature:Mappings Editor Index mappings editor UI labels Jun 23, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/es-ui (Team:Elasticsearch UI)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:Index Management Index and index templates UI Feature:Mappings Editor Index mappings editor UI Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants