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

Support for semantic version data type in index patterns, aggregations, and Lens #93248

Closed
wylieconlon opened this issue Mar 2, 2021 · 6 comments · Fixed by #123739
Closed
Labels
enhancement New value added to drive a business result Feature:Aggregations Aggregation infrastructure (AggConfig, esaggs, ...) Feature:Data Views Data Views code and UI - index patterns before 8.0 Feature:Lens impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort NeededFor:VisEditors Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@wylieconlon
Copy link
Contributor

Kibana should have full support for the new semantic versioning data type, which was introduced in Elasticsearch 7.10 but is not supported in Kibana. Because it's a type of Keyword field, we should be able to map this as a string everywhere in Kibana.

@wylieconlon wylieconlon added Feature:Aggregations Aggregation infrastructure (AggConfig, esaggs, ...) enhancement New value added to drive a business result Feature:Data Views Data Views code and UI - index patterns before 8.0 Team:AppServices Feature:Lens labels Mar 2, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServices)

@flash1293
Copy link
Contributor

Side note for Lens - we should pick this up in the sorting logic for the table

@wylieconlon
Copy link
Contributor Author

Unlike regular keyword fields, you can use a range query on semantic version fields.

@flash1293 flash1293 added the Team:Visualizations Visualization editors, elastic-charts and infrastructure label Mar 11, 2021
@bczifra
Copy link
Member

bczifra commented May 17, 2021

ECS is adopting the version field type: elastic/ecs#887

@bczifra
Copy link
Member

bczifra commented May 17, 2021

It looks like the index templates editor already supports version fields: #78206

@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort labels Jun 21, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:medium Medium Level of Effort and removed loe:small Small Level of Effort labels Oct 6, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:small Small Level of Effort and removed loe:medium Medium Level of Effort labels Nov 19, 2021
@Dosant
Copy link
Contributor

Dosant commented Jan 6, 2022

Basic support was added in #104870

I tested that :

  • Data view editor identifies version field as version
  • You can use range filter for version field in query editor (KQL) and in filter manager. (filter manager using custom filter)
  • Sorting is discover works properly based on semantic version rules
  • Sorting in visualize table is correct

Potential improvements:

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:Aggregations Aggregation infrastructure (AggConfig, esaggs, ...) Feature:Data Views Data Views code and UI - index patterns before 8.0 Feature:Lens impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort NeededFor:VisEditors Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants