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
In the lab, the role of the function named "StreamProcessing" is to trigger when items are sent to IOT hub and write it to Cosmos DB "telemetry" collection. The name "StreamProcessing" is confusing here, because in the diagram, it is named "Event Processing," so it is hard to find on the diagram.
It is also easy to confuse, because there is another function called "CosmosDB," which is triggered off "telemetry" collection to send data to Event Hub, which is an input for Stream Analytics. The naming of "StreamProcessing" function makes it seem like it's a function that is directly connected to Stream Analytics, which it is not.
In addition, the function called "CosmosDB" is called "Trip Processing" in the diagram.
Suggestions: Rename the functions to be consistent with the diagram, or add a note in the lab explaining the mapping of how the name appears in Visual Studio to the diagram.
The text was updated successfully, but these errors were encountered:
In the lab, the role of the function named "StreamProcessing" is to trigger when items are sent to IOT hub and write it to Cosmos DB "telemetry" collection. The name "StreamProcessing" is confusing here, because in the diagram, it is named "Event Processing," so it is hard to find on the diagram.
It is also easy to confuse, because there is another function called "CosmosDB," which is triggered off "telemetry" collection to send data to Event Hub, which is an input for Stream Analytics. The naming of "StreamProcessing" function makes it seem like it's a function that is directly connected to Stream Analytics, which it is not.
In addition, the function called "CosmosDB" is called "Trip Processing" in the diagram.
![image](https://user-images.githubusercontent.com/1221629/67154681-9a1a7500-f34c-11e9-99c6-1c88fc080f23.png)
Suggestions: Rename the functions to be consistent with the diagram, or add a note in the lab explaining the mapping of how the name appears in Visual Studio to the diagram.
The text was updated successfully, but these errors were encountered: