Merge pull request #224151 from an-emma/patch-11

Update

Author: prmerger-automator[bot]

articles/stream-analytics/stream-analytics-troubleshoot-input.md

@@ -1,11 +1,11 @@
 ---
 title: Troubleshooting Inputs for Azure Stream Analytics
 description: This article describes techniques to troubleshoot your input connections in Azure Stream Analytics jobs.
-author: ajetasin
-ms.author: ajetasi
+author: an-emma
+ms.author: raan
 ms.service: stream-analytics
 ms.topic: troubleshooting
-ms.date: 04/08/2022
+ms.date: 01/17/2023
 ms.custom: seodec18
 ---
 
@@ -47,6 +47,12 @@ Other common reasons that result in input deserialization errors are:
 3. Using Event Hub capture blob in Avro format as input in your job.
 4. Having two columns in a single input event that differ only in case. Example: *column1* and *COLUMN1*.
 
+## Partition count changes
+Partition count of Event Hub can be changed. The Stream Analytics job needs to be stopped and started again if the partition count of Event Hub is changed. 
+
+The following errors are shown when the partition count of Event Hub is changed when the job is running.
+Microsoft.Streaming.Diagnostics.Exceptions.InputPartitioningChangedException
+
 ## Job exceeds maximum Event Hub receivers
 
 A best practice for using Event Hubs is to use multiple consumer groups for job scalability. The number of readers in the Stream Analytics job for a specific input affects the number of readers in a single consumer group. The precise number of receivers is based on internal implementation details for the scale-out topology logic and is not exposed externally. The number of readers can change when a job is started or during job upgrades.