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

Map new Elasticsearch unsigned long to a number in Kibana #81075

Closed
LeeDr opened this issue Oct 19, 2020 · 1 comment · Fixed by #81115
Closed

Map new Elasticsearch unsigned long to a number in Kibana #81075

LeeDr opened this issue Oct 19, 2020 · 1 comment · Fixed by #81115
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Data Views Data Views code and UI - index patterns before 8.0 Feature:elasticsearch

Comments

@LeeDr
Copy link
Contributor

LeeDr commented Oct 19, 2020

Describe the feature: Elasticsearch has added 64 bit unsigned long data type. It isn't currently mapped to a number type in Kibana but should be.

#40183

Describe a specific use case for the feature:

/cc @timroes

Otherwise the field is not usable.

I'm also finding that I can't sort on this field in Discover.
my_int shows sorting buttons;
image

But the unsigned long doesn't;
image

The field doesn't appear in the auto-complete field list in Discover;
image

Or in the field list to add a filter;
image

Also doesn't appear in the field list in Lens.

@LeeDr LeeDr added bug Fixes for quality problems that affect the customer experience Feature:elasticsearch Feature:Data Views Data Views code and UI - index patterns before 8.0 Team:AppArch labels Oct 19, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-arch (Team:AppArch)

@timroes timroes self-assigned this Oct 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Data Views Data Views code and UI - index patterns before 8.0 Feature:elasticsearch
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants