-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Send float fields as float values to Elasticsearch #2627
Conversation
I suggest we backport this to 5.0 as soon as the tests pass as I don't think this is a breaking change. As we discussed it does not prevent people from still loading the dashboard, but it is a nice fallback. |
49539f9
to
5b0b8c2
Compare
…g the mapping in advance
d4e4b08
to
38e7fae
Compare
@@ -134,7 +134,7 @@ def test_dropevent_with_complex_condition(self): | |||
output = self.read_output( | |||
required_fields=["@timestamp", "type"], | |||
) | |||
assert len(output) == 1 | |||
assert len(output) >= 1 |
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 this change somehow related to the changes above or just a flaky test?
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.
flaky test, as it's variable how many events are sent out.
LGTM |
…g the mapping in advance (elastic#2627)
…g the mapping in advance (elastic#2627) (elastic#2687)
This PR tries to remove the necessity to define the mapping before inserting the data into Elasticsearch, by making sure that float fields are always sent as float values even if they are not flows. For example
5
will be sent as5.00000
, so Elasticsearch defines it asfloat
.With this change, it's not needed to load the template in advance, before inserting the data into Elasticsearch.
NOTE: This also affects processors.