-
Notifications
You must be signed in to change notification settings - Fork 9.1k
check the buffer size #453
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
base: trunk
Are you sure you want to change the base?
Conversation
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
Fixes for Bugs - SAMZA-1571 Make Eventhubs system configs compatible with Samza standalone. - SAMZA-1624 EventHub system should prefix the configs with senstive for SasKey and SasToken - SAMZA-1625 EventHub systemAdmin is swallowing exceptions - SAMZA-1626 EventHub system admin is not returning the metadata for all the ssps requested for Description 1. Right now event hub doesn't follow the samza's config convention of naming the secrets as "sensitive" so that they are masked before they are logged. 2. Event hub configs uses the old system.<systemName>.streams.<streamName> which is blacklisted in Samza standalone. So moving these configs to newer <streams>.<streamid> 3. Wrapping the underlying exception properly in the SamzaException in EventHubSystemAdmin 4. Porting Bharat's fix to return the metadata for all the ssps requested for in EventHubSystemAdmin Author: Srinivasulu Punuru <spunuru@linkedin.com> Reviewers: Xinyu Liu <xinyuliu.us@gmail.com> Closes apache#453 from srinipunuru/eh.1
No description provided.