-
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
Add type murmur3 into the lens fields list #129029
Conversation
To fix #129007 , naive approach.
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
This is super unlucky timing, but 8.3 just got branched off and there's no snapshot builds yet for the elasticsearch plugins https://artifacts-api.elastic.co/v1/search/8.3.0-SNAPSHOT They should become available soon, I will check daily and once they are built I will give it a test-run to see whether something breaks unexpectedly. |
@elasticmachine merge upstream |
This looks pretty good already! Some rough edges I noticed: "Top values" don't really make any sense for murmur3 - we should opt out of fetching a field summary for this field type like we do for ranges:
The file icon is not exactly pretty, but I'm not sure which one to use, maybe
Please do not add translations, there's a separate process for that, it will be handled outside of this PR. |
We are using this fix on prod for 3 days now (we are using kibana v7.17.1), very happy with it! I will squash commits when this is ready for review, thanks you. |
@elasticmachine merge upstream |
Buildkite, test this |
Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors) |
Given what we have available in our EUI tokens, I agree that |
@ebuildy Could you adapt the icon for murmur3 in here?
Also there seems to be a small issue with the linting. Apart from that I think we can get this PR ready to merge, thank you so much for your contribution 💚
No need to do that, Github will take care of it on merge. |
lint issue seem have been fixed / committed automatically |
@elasticmachine merge upstream |
@@ -460,7 +460,7 @@ function FieldItemPopoverContents(props: State & FieldItemProps) { | |||
|
|||
if (props.isLoading) { | |||
return <EuiLoadingSpinner />; | |||
} else if (field.type.includes('range')) { | |||
} else if (field.type.includes('range') || field.type === 'murmur3') { | |||
return ( | |||
<> | |||
<EuiPopoverTitle>{panelHeader}</EuiPopoverTitle> |
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.
The message specifically calls out "range type fields" which doesn't match the murmur3 case. Could you add a separate branch for this case with a new i18n phrase Summary information is not available for murmur3 fields
?
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.
Just went ahead and pushed this change
One last thing I noticed, otherwise this looks great! #129029 (comment) |
Buildkite, test this. |
@elasticmachine merge upstream |
Buildkite, test this |
@elasticmachine run elasticsearch-ci/docs |
@elasticmachine merge upstream |
Buildkite, test this |
@elasticmachine run elasticsearch-ci/docs |
💚 Build SucceededMetrics [docs]Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: cc @flash1293 |
Apologies for taking this over a bit @ebuildy . Merging now as this looks fine, thanks for your contribution 💚 |
@flash1293 I see kibana is a really big project ^^ no worries, I am very happy about this feature. |
Summary
Related to issue #129007 (Fields of type murmur3 dont appear in the lens fields list).
This PR add field of type murmur3 in the fields listing for lens visualization.
Checklist
Delete any items that are not applicable to this PR.
Risk Matrix
For maintainers