Change node event hub cardinality

Azure · Apr 14, 2017 · 591cf9b · 591cf9b
1 parent 24149c4
commit 591cf9b
Show file tree

Hide file tree

Showing 5 changed files with 1,191 additions and 1,156 deletions.
diff --git a/Bindings/bindings.json b/Bindings/bindings.json
@@ -113,6 +113,24 @@
                     "label": "$eventHubTrigger_connection_label",
                     "help": "$eventHubTrigger_connection_help",
                     "placeholder": "[variables('selectConnection')]"
+                },
+                {
+                    "name": "cardinality",
+                    "value": "enum",
+                    "required": false,
+                    "defaultValue": "many",
+                    "enum": [
+                        {
+                            "value": "one",
+                            "display": "One"
+                        },
+                        {
+                            "value": "many",
+                            "display": "Many"
+                        }
+                    ],
+                    "label": "$eventHubTrigger_cardinality_label",
+                    "help": "$eventHubTrigger_cardinality_help"
                 }
             ]
         },

diff --git a/Documentation/eventHubTrigger.md b/Documentation/eventHubTrigger.md
@@ -7,6 +7,7 @@ The settings for an Azure Event Hub trigger specifies the following properties:
 - `direction` : Must be set to *in*. 
 - `path` : The name of the event hub.
 - `connection` : The name of an app setting that contains the connection string to the namespace that the event hub resides in. Copy this connection string by clicking the **Connection Information** button for the namespace, not the event hub itself.  This connection string must have at least read permissions to activate the trigger.
+- `cardinality` : Cardinality of the trigger input. Choose 'One' if the input is a single message or 'Many' if the input is an array of messages. 'One' is the default if unspecified.
 
 #### Azure Event Hub trigger C# example
 
@@ -18,8 +19,13 @@ The settings for an Azure Event Hub trigger specifies the following properties:
 	}
 
 #### Azure Event Hub trigger JavaScript example
-
-	module.exports = function (context, myEventHubMessage) {
-	    context.log('JavaScript eventhub trigger function processed work item', myEventHubMessage);	
-	    context.done();
+
+	module.exports = function (context, eventHubMessages) {
+		context.log(`JavaScript eventhub trigger function called for message array ${eventHubMessages}`);
+		
+		eventHubMessages.forEach(message => {
+			context.log(`Processed message ${message}`);
+		});
+
+		context.done();
 	};