[Google Workspace ] Fix order of processes in ingest pipeline #5300
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Fixes the order of
processesin ingest-pipeline. Thefingerprintprocess had colliding documents becauserenameprocess ran first and changed the value ofjson.events.namewhich potentially could create same fingerprint for documents with different name but other matching fields.Found this bug as part of system testing in https://github.com/elastic/security-team/issues/5869
Checklist
changelog.ymlfile.How to test this PR locally
make buildgoogle_workspacepackageassert: hit_count : 22toadmindata_stream's System test configRelated issues