-
Notifications
You must be signed in to change notification settings - Fork 439
Allow sending & reading headers via Kafka Message object. #880
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
Closed
Closed
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
1b3b91a
Allow sending & reading headers via Kafka Message object.
Steveb-p 3e930a1
Allow sending & reading headers via Kafka Message object.
Steveb-p 735e67f
Allow sending & reading headers via Kafka Message object.
Steveb-p c837eac
Fix Code style
Steveb-p 4b99dee
Fix comment
Steveb-p 15634f0
Fix code style
Steveb-p fd45d2e
Move getLibrdkafka method to Context & make it static
Steveb-p c809e80
Revert phpdoc change
Steveb-p File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
This probably also should contain a check against phprdkafka version & librdkafka 1.0.0, since there is a possible segfault here.
EDIT: Well, as a matter of fact, the PR that fixes the
producev
call for librdkafka 1.0.0 is not yet included in a release, so it will probably have to remain as a TODO once it does.Related PR:
arnaud-lb/php-rdkafka#222
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.
Added version check. I've tried it with local build from master and
which is the version that you will get if you build from master branch of phprdkafka.
I'm considering whether or not this check is worthwile, however otherwise it will result in hard to debug segfault.
@makasim what are you thought on this? Should it be dropped? Should it emit a warning (like here) or "drop down" to calling
produce
?