-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Enable grok processor to support long, double and boolean #27896
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
Enable grok processor to support long, double and boolean #27896
Conversation
|
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? |
|
@elasticmachine test this please |
|
thanks @kiawin, Looks good! |
* es/master: (45 commits) Adapt scroll rest test after backport. relates #27842 Move early termination based on index sort to TopDocs collector (#27666) Upgrade beats templates that we use for bwc testing. (#27929) ingest: upgraded ingest geoip's geoip2's dependencies. [TEST] logging for update by query test #27820 Add elasticsearch-nio jar for base nio classes (#27801) Use full profile on JDK 10 builds Require Gradle 4.3 Enable grok processor to support long, double and boolean (#27896) Add unreleased v6.1.2 version TEST: reduce blob size #testExecuteMultipartUpload Check index under the store metadata lock (#27768) Fixes DocStats to not report index size < -1 (#27863) Fixed test to be up to date with the new database files. Upgrade to Lucene 7.2.0. (#27910) Disable TestZenDiscovery in cloud providers integrations test Use `_refresh` to shrink the version map on inactivity (#27918) Make KeyedLock reentrant (#27920) ingest: Upgraded the geolite2 databases. [Test] Fix IndicesClientDocumentationIT (#27899) ...
|
This is pending a backport to |
These tests can run on master only. See #27896
|
@talevy Is the backport pending label still relevant? |
|
:shame: I did not do a good job following up on this. It would be a simple backport to 6.7, but I waited @jakelandis what do you think? Would you think this should go into 6.x? |
|
@talevy - I think it is good to go back to 6.x. Logstash grok uses |
|
thanks @jakelandis. I'll go ahead and backport to 6.x! and thanks again @jpountz for bouncing this back up! |
|
I opened #38000 as a copy-paste job from this PR |
Adds support for long,double,boolean coercion in grok expression. backport of #27896. note: the original commit contents was changed to the point that cherry-picking/merging was more complicated than the commit itself due to directory structure changes. this represents the work that @kiawin did in the original PR
It would be useful to allow grok processor to support long, double, and boolean type.