-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] Top hits per entity--change to title to use recent, minor edits #89254
Conversation
Pinging @elastic/kibana-gis (Team:Geo) |
Pinging @elastic/kibana-docs (Team:Docs) |
💚 CLA has been signed |
Looks like my recommendation isn't a new change -- it reverts to the previous topic title (basically). |
@kmartastic Thanks for the changes. Please sign the contributor agreement. Your changes look good to me. |
docs/maps/maps-aggregations.asciidoc
Outdated
@@ -68,9 +68,9 @@ To enable a blended layer that dynamically shows clusters or documents: | |||
|
|||
[role="xpack"] | |||
[[maps-top-hits-aggregation]] | |||
=== Top hits per entity | |||
=== Display the most recent documents |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This title is not completely accurate. The top hits per entity is determined by the sort field and sort direction. Users can change either so that the top hits are not the most recent documents - but the most "relevent documents". Is this a concern that the title is too limiting?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point.
I had the title as Display the most recent and relevant documents, but that was too long. Most relevant is better. The concern is the title is ambiguous. The goal was to make it more use-case driven.
@nreese Propose to change to: Display the most relevant documents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the term "entity" needs to be in there somewhere. The big distinction with the top hits layer is that it grabs the top hits per entity instead of just grabbing the first 10000 matching documents.
I have signed it twice. :) What do I do now @gchaps? |
cla/check |
Hey @kmartastic, looks like your local git config setup is using the wrong email address for your commits. Looking at https://github.com/elastic/kibana/commit/a4d57f8da3e40d9489b259e38d39c36f911739a3.patch you can see that your commit is attributed to |
@kmartastic You can use the longer name on the page, and then use a shorter name in the navigation. For the shorter title, add code something like this:
|
@spalger I hit an error trying to change the email associated with git commits. I'm not sure how to proceed. |
Hmm, where is that error coming from? The instructions I linked tell you how to set your email address that the git CLI is using to author commits you create locally, and then you'll use the git CLI to rewrite your commits to use the correct email address. |
@spalger I was trying to follow these instructions: https://docs.github.com/en/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account Specifically -- just trying to add the email to my account. |
Under the |
@spalger I made the first changes -- but step 4. leads down the path to updating the profile to link contributions, which error'd. |
Ah, gotcha, that step isn't necessary when you use the |
Alright, looks like you merged the old commit back into your local branch, so the old commit is still in place and invalidating the CLA check. If you run the following it should fix it up:
|
5aa6c2b
to
0dfaa2d
Compare
Thanks @spalger. |
docs/maps/maps-aggregations.asciidoc
Outdated
@@ -68,9 +68,9 @@ To enable a blended layer that dynamically shows clusters or documents: | |||
|
|||
[role="xpack"] | |||
[[maps-top-hits-aggregation]] | |||
=== Top hits per entity | |||
=== Display the most relevant entities |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about "Display the most relevant documents per entities"? The layer is not displaying entities but the top documents per entity.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to come up with a more specific word for entity?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like Nathan's suggestion; I think we should use entity.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
++
@nreese please review. |
|
||
You can display the most relevant documents per entity, for example, the most recent GPS tracks per flight. | ||
Use *Top hits per entity* to display the most relevant documents per entity, for example, the most recent GPS tracks per flight route. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now title is repeat of this sentence. Is that a problem?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think @gchaps?
I don't think it's a problem, but it's obviously not normal practice.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does feel a little awkward to have"per entity" appear three times before the second sentence. What about removing that sentence and going with this:
Elasticsearch groups your data using a terms aggregation, and then accumulates the most relevant documents based on sort order for each entry using a top hits metric aggregation.
To view the top hits per entity:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't loss the example, "for example, the most recent GPS tracks per flight route." needs to be maintained
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Elasticsearch groups your data using a terms aggregation, and then accumulates the most relevant documents based on sort order for each entry using a top hits metric aggregation. This enables you to view metrics such as the most recent GPS tracks per flight route.
To view the top hits per entity:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't use the word "metric" because its not an aggregation. Unlike an aggregation, top hits is actually showing documents, just a very small number of documents per entity, where entity is an airplane or truck.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
metrics > top hits?
If that doesn't work, let's go with the original text.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the text is fine because Tops hits per entity is a UI command.
Use Top hits per entity to display the most relevant documents per entity, for example, the most recent GPS tracks per flight route.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@elasticmachine merge upstream |
* master: (244 commits) [maps] Top hits per entity--change to title to use recent, minor edits (elastic#89254) [DOCS] Update installation details (elastic#90354) RFC for automatically generated typescript API documentation for every plugins public services, types, and functionality (elastic#86704) Elastic Maps Server config is `host` not `hostname` (elastic#90234) Use doc link services in index pattern management (elastic#89937) [Fleet] Managed Agent Policy (elastic#88688) [Workplace Search] Fix Source Settings bug (elastic#90242) [Enterprise Search] Refactor MockRouter test helper to not store payload (elastic#90206) Use doc link service in more Stack Monitoring pages (elastic#89050) [App Search] Relevance Tuning logic - actions and selectors only, no listeners (elastic#89313) Remove UI filters from UI (elastic#89793) Use newfeed.service config for all newsfeeds (elastic#90252) skip flaky suite (elastic#85086) Add readme to geo containment alert covering test alert setup (elastic#89625) [APM] Enabling yesterday option when 24 hours is selected (elastic#90017) Test user for maps tests under import geoJSON tests (elastic#86015) [Lens] Hide column in table (elastic#88680) [Security Solution][Detections] Reduce detection engine reliance on _source (elastic#89371) [Discover] Minor cleanup (elastic#90260) [Search Session][Management] Rename "cancel" button and delete "Reload" button (elastic#90015) ...
elastic#89254) * [maps] Top hits per entity--change to title to use recent, minor edits * Updated TopHitsPerEntity title and description to use the term relevant * updating top hits per entity topic to new title Co-authored-by: Kent Marten <[email protected]> Co-authored-by: Kibana Machine <[email protected]>
elastic#89254) * [maps] Top hits per entity--change to title to use recent, minor edits * Updated TopHitsPerEntity title and description to use the term relevant * updating top hits per entity topic to new title Co-authored-by: Kent Marten <[email protected]> Co-authored-by: Kibana Machine <[email protected]>
#89254) (#90366) * [maps] Top hits per entity--change to title to use recent, minor edits * Updated TopHitsPerEntity title and description to use the term relevant * updating top hits per entity topic to new title Co-authored-by: Kent Marten <[email protected]> Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Kent Marten <[email protected]> Co-authored-by: Kibana Machine <[email protected]>
#89254) (#90367) * [maps] Top hits per entity--change to title to use recent, minor edits * Updated TopHitsPerEntity title and description to use the term relevant * updating top hits per entity topic to new title Co-authored-by: Kent Marten <[email protected]> Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Kent Marten <[email protected]> Co-authored-by: Kibana Machine <[email protected]>
Change title to use use-case centric language. Minor edits in topic.
Preview: https://kibana_89254.docs-preview.app.elstc.co/guide/en/kibana/master/maps-top-hits-aggregation.html