We are still planning to deliver this. Some preliminary work is underway, but we’ll wait to switch to the “Started” status until a few things are further along and we have a better sense of the timeline.
Thank you for taking the time to vote on this request. Work on this has commenced. We will email you once it is completed.
If you are interested in participating in the preview please email back.
Hi Magnus. This is currently unplanned by us for our road map. Some context and feedback for you on this.
First, to do the replication itself to the secondary region you need RU/s sufficient to support the request rates for the primary region itself. Replication and writing to the secondary region itself is not free so there needs to be sufficient throughput provisioned to do that.
Second, for the secondary region to be able to function as the primary should a fail over occur, the replica region itself needs sufficient throughput to function as the primary.
Thanks again for your suggestion. Will mark as unplanned for now in case circumstances ever do change.
24 votesunplanned · AdminAzure Stream Analytics Team on UserVoice (Product Manager, Microsoft Azure) responded
We are exploring the possibility of supporting CosmosDB change feed as ingress to Stream Analytics which will solve this scenario. For reference data, we already provide a mechanism to refresh reference data in Azure Blob storage using Azure Data Factory. More details about this here: https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-use-reference-data
We are listening and committed to making Stream Analytics even better! Keep your feedback coming.
181 votesunder review · 10 comments · Stream Analytics » Inputs and Outputs · Flag idea as inappropriate… · Admin →
An error occurred while saving the commentNick commented
Cosmos DB should be a source of reference data, but the Cosmos DB Change Feed should be valid input to a Stream Analytics job as well. Solve different use cases, both equally necessary.
Work for this feature is currently on our backlog and not in our current development cycle plan. We will continue to revisit this item in upcoming cycles and will update here if this item moves in plan.
Thank you for your suggestion and votes.
Moving to our backlog (unplanned). Will continue to visit this and update if this changes.
Update: The ETA for this has not been set. This is actively being worked on but cannot provide ETA.
Our apologies again. We are looking forward to shipping this feature.
Quick update. Apologies for the long time on this. We are looking to ship this in Spring 2020.
We have reviewed this and have elected to not include this on our road map for the time being. We may revisit this in the future so will leave as unplanned rather than declined or closed.
Thanks for your suggestion and comments.