You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Azure Event Hubs is a highly scalable publish-subscribe service that can ingest millions of events per second and stream them to multiple consumers. This lets you process and analyze the massive amounts of data produced by your connected devices and applications.
This issue tracks the work we have planned for this package for the duration of January - June 2021
New features:
Provide custom hostname support for users who run their applications in a private network that lacks access to public endpoints and require the ability to specify a custom host name to ensure they route through the proper intermediary for the connection to be made.
Connection string parser so that users can parse the namespace and event hub name from the connection string in case they chose to use the constructor overload that supports AAD
Idempotent Producer to support the feature of server side deduplication
Receiver redirect to support the service side redirects where the main benefit is that it allows a more direct connection to the host which should reduce latency.
Support for SharedKeyCredential and SASCredential to allow rotation of Shared keys and SAS tokens which is not possible when using connection strings
Support reading the underlying AMQP message on an Event Data.
Support the use of BinaryData in EventData
General improvements:
Fix incoming customer reported issues
Build Trouble Shooting Guides
Testing improvements:
Add perf tests that are run before every update to catch regressions
Fix flaky tests if any
Try out rhea to set up a mock server that can emulate Event Hubs in our tests. The JS team will be trying this out first.
Enable azure-powershell CI for all management RPs (Azure#18771)
* Enable azure-powershell for all manage RPs
* Change integrationRepository to Azure/azure-powershell-pr
* Change azure-powershell in api-spec repo
* Change azure-powershell in api-spec repo
* Remove azure-powershell from some deprecated RPs
Co-authored-by: v-yuzhichen@microsoft.com <v-yuzhichen@microsoft.com>
azure-sdk
pushed a commit
to azure-sdk/azure-sdk-for-net
that referenced
this issue
Apr 22, 2022
Enable azure-powershell CI for all management RPs (Azure#18771)
* Enable azure-powershell for all manage RPs
* Change integrationRepository to Azure/azure-powershell-pr
* Change azure-powershell in api-spec repo
* Change azure-powershell in api-spec repo
* Remove azure-powershell from some deprecated RPs
Co-authored-by: v-yuzhichen@microsoft.com <v-yuzhichen@microsoft.com>
azure-sdk
pushed a commit
to azure-sdk/azure-sdk-for-net
that referenced
this issue
Apr 22, 2022
Enable azure-powershell CI for all management RPs (Azure#18771)
* Enable azure-powershell for all manage RPs
* Change integrationRepository to Azure/azure-powershell-pr
* Change azure-powershell in api-spec repo
* Change azure-powershell in api-spec repo
* Remove azure-powershell from some deprecated RPs
Co-authored-by: v-yuzhichen@microsoft.com <v-yuzhichen@microsoft.com>
Azure Event Hubs is a highly scalable publish-subscribe service that can ingest millions of events per second and stream them to multiple consumers. This lets you process and analyze the massive amounts of data produced by your connected devices and applications.
The Azure.Messaging.EventHubs & Azure.Messaging.EventHubs.Processor packages provides the SDK for .Net developers to write applications that use Azure Event Hubs. Version 5 of this package follows the latest guidelines for writing C# .Net SDKs for Azure services with the goal of being a client library that is developer-friendly, idiomatic to the .Net ecosystem, and as consistent across different languages and platforms as possible.
This issue tracks the work we have planned for this package for the duration of January - June 2021
New features:
General improvements:
Testing improvements:
Documentation
The text was updated successfully, but these errors were encountered: