Skip to content

TopologyBuilder methods return the builder to allow methods to be chained together.#32

Merged
ymatsuda merged 2 commits into
confluentinc:streamingfrom
rhauch:streaming-topology-builder-improvement
Sep 4, 2015
Merged

TopologyBuilder methods return the builder to allow methods to be chained together.#32
ymatsuda merged 2 commits into
confluentinc:streamingfrom
rhauch:streaming-topology-builder-improvement

Conversation

@rhauch

Copy link
Copy Markdown

Since the methods returned void before, this change has no impact on existing code.

@ymatsuda

ymatsuda commented Sep 4, 2015

Copy link
Copy Markdown

Randall Hauch (@rhauch) Thank you for the pull request. There seems to be a conflict. Would you resolve it so that I can merge?

…ined together. Since the methods returned void before, this has no other impact on existing code.
@rhauch Randall Hauch (rhauch) force-pushed the streaming-topology-builder-improvement branch from c30b286 to 88474e6 Compare September 4, 2015 14:45
@rhauch

Copy link
Copy Markdown
Author

ymatsuda, I've rebased upon the latest upstream branch, and also added JavaDoc for the public methods in TopologyBuilder. Let me know if there are more problems.

@rhauch Randall Hauch (rhauch) force-pushed the streaming-topology-builder-improvement branch 3 times, most recently from 11784aa to a3f11eb Compare September 4, 2015 14:49
@rhauch Randall Hauch (rhauch) force-pushed the streaming-topology-builder-improvement branch from a3f11eb to 1a1bf8f Compare September 4, 2015 14:50
@ymatsuda

ymatsuda commented Sep 4, 2015

Copy link
Copy Markdown

Thanks!

ymatsuda added a commit that referenced this pull request Sep 4, 2015
…ment

TopologyBuilder methods return the builder to allow methods to be chained together.
@ymatsuda ymatsuda merged commit 5165f3e into confluentinc:streaming Sep 4, 2015
José Armando García Sancio (jsancio) pushed a commit that referenced this pull request Sep 13, 2019
…ction (#32)

When the broker interceptor fails a request because it couldn't be transformed (e.g. invalid resource name or invalid principal that couldn't be prefixed), the interceptor throws an InvalidRequestException, which is propagated to the Processor processing the incoming receive. Processor treats this like any other invalid request/schema exception and closes the connection. For incoming requests which were successfully parsed but failed by the interceptor, this PR improves error handling by returning a response to the user with an INVALID_REQUEST error with the reason why the request was rejected.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants