[libbeat] kafka message support headers feature#29940
Conversation
|
💚 CLA has been signed |
|
This pull request does not have a backport label. Could you fix it @herbxu? 🙏
NOTE: |
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
|
This pull request is now in conflicts. Could you fix it? 🙏 |
rdner
left a comment
There was a problem hiding this comment.
Thank you for your contribution, @herbxu!
In order to merge this PR, we would need a test confirming the new functionality works (see https://github.com/elastic/beats/blob/main/libbeat/outputs/kafka/kafka_integration_test.go). Once it's there, I'm happy to merge the PR.
I have added the integration test for this feature, thanks ! |
rdner
left a comment
There was a problem hiding this comment.
Thank you for addressing the comments and adding the test case. I noticed another small improvement that you might want to apply.
It looks like you have not signed the CLA https://www.elastic.co/contributor-agreement
Since you use the privacy feature on GitHub and your commits have a different email address, the automation is not able to detect the CLA signature. However, I checked manually in our contributor database and I could find neither your nickname herbxu nor your email address xiangwei.xxw@alibaba-inc.com
After the CLA is signed I'll run the CI pipeline and we can merge this PR.
Accepted this pre-allocate memory for kafka headers buffer Co-authored-by: Denis Rechkunov <denis@rdner.de>
I have signed with the email xiangwei.xxw@alibaba-inc.com, thanks for your suggestion. |
|
jenkins run tests |
|
/test |
…into feature/use-with-kind-k8s-env * 'feature/use-with-kind-k8s-env' of github.com:v1v/beats: (52 commits) ci: home is declared within withBeatsEnv ci: use withKindEnv step ci: use getBranchesFromAliases and support next-patch-8 (elastic#30400) Update fields.yml (elastic#29609) Heartbeat: fix browser metrics and trace mappings (elastic#30258) Apply light edits to 8.0 changelog (elastic#30351) packetbeat/beater: make sure Npcap installation runs before interfaces are needed (elastic#30396) Add a ring-buffer reporter to libbeat (elastic#28750) Osquerybeat: Add install verification for osquerybeat (elastic#30388) update windows matrix support (elastic#30373) Refactor of metricbeat process-gathering metrics and system/process (elastic#30076) adjust next changelog wording (elastic#30371) [Metricbeat] azure: move event report into loop validDim loop (elastic#29945) fix: report GitHub Check before the cache (elastic#30372) Add support for non-unique keys in Kafka output headers (elastic#30369) ci: 6 major branch reached EOL (elastic#30357) reduce Elastic Agent shut down time by stopping processes concurrently (elastic#29650) [Filebeat] Add message to register encode/decode debug logs (elastic#30271) [libbeat] kafka message header support (elastic#29940) Heartbeat: set duration to zero for syntax errors (elastic#30227) ...
What does this PR do?
kafka message support headers feature
Why is it important?
Kafka Message Header lets consumers process message metadata without having to deserialize the message value/payload. This could be useful in the routing of message use case.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
xiangwei.xxw@alibaba-inc.com
How to test this PR locally
Related issues
Use cases
Screenshots
Logs