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

[Maps] Support most recent document by entity to be numeric field #46882

Closed
Alex3k opened this issue Sep 28, 2019 · 3 comments · Fixed by #47361
Closed

[Maps] Support most recent document by entity to be numeric field #46882

Alex3k opened this issue Sep 28, 2019 · 3 comments · Fixed by #47361
Assignees
Labels
[Deprecated-Use Team:Presentation]Team:Geo Former Team Label for Geo Team. Now use Team:Presentation enhancement New value added to drive a business result

Comments

@Alex3k
Copy link
Contributor

Alex3k commented Sep 28, 2019

Describe the feature:
The "Show most recent document by entity" feature within the maps app currently only takes a datetime field. It would be really valuable to support a numeric field also. For example the largest or smallest (configurable) value in Field A.

Describe a specific use case for the feature:
To get maximum value from drilling (oil and gas) data, I am encouraging companies to ingest all the raw numeric (time & depth series) data into Elasticsearch. This way they can leverage the power of our aggregations and visualisations to easily get value without much effort. A single wellbore can have 250,000 documents, sometimes more. Many organizations have 100k well bores. This data is indexed by depth (float value).

As we only plot the first N documents on a map, this often leads to a map only having one wellbore present. The "Show most recent document by entity" is almost perfect. If it supported the above request, we could only show only one wellbore for all of the documents without much effort at all. Currently, I am suggesting to use transforms (previously known as data frames) to summarise all the wells as they enter Elasticsearch.

@Alex3k Alex3k added [Deprecated-Use Team:Presentation]Team:Geo Former Team Label for Geo Team. Now use Team:Presentation enhancement New value added to drive a business result labels Sep 28, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-gis

@bcamper
Copy link

bcamper commented Oct 1, 2019

I think this would be a great addition. But I also wanted to point out that this specific case (and others like it) are likely to also run into the 10k aggregations limit (since the "per entity" is implemented as a terms aggregation), e.g. if the "group by" (100k wells) is over 10k. I've run into this with other datasets.

@nreese do you know if we have an issue logged for addressing that limit? If not I'll add one.

@nickpeihl
Copy link
Member

I believe this issue addresses the 10k aggregation limit. #27606

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Deprecated-Use Team:Presentation]Team:Geo Former Team Label for Geo Team. Now use Team:Presentation enhancement New value added to drive a business result
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants