QueueTrigger Interface
Implements
public interface QueueTrigger implements java.lang.annotation.Annotation
Place this on a parameter whose value would come from a storage queue, and causing the method to run when a new item is pushed. The parameter type can be one of the following:
- Any native Java types such as int, String, byte[]
- Nullable values using Optional
- Any POJO type
The following example shows a Java function that polls the "myqueue-items" queue and writes a log each time a queue item is processed.
@FunctionName("queueMonitor")
public void logQueueItem(
@QueueTrigger(name = "msg", queueName = "myqueue-items", connection = "AzureWebJobsStorage")
String message,
final ExecutionContext context
) {
context.getLogger().info("Queue message processed: " + message);
}
Method Summary
Modifier and Type | Method and Description |
---|---|
abstract java.lang.String |
connection()
Defines the app setting name that contains the Azure Storage connection string. |
abstract java.lang.String |
dataType()
Defines how Functions runtime should treat the parameter value. |
abstract java.lang.String |
name()
The variable name used in function. |
abstract java.lang.String |
queueName()
Defines the name of the storage queue to which to bind. |
Method Details
connection
public abstract String connection()
Defines the app setting name that contains the Azure Storage connection string.
Returns:
dataType
public abstract String dataType()
Defines how Functions runtime should treat the parameter value. Possible values are:
- "": get the value as a string, and try to deserialize to actual parameter type like POJO
- string: always get the value as a string
- binary: get the value as a binary data, and try to deserialize to actual parameter type byte[]
Returns:
name
public abstract String name()
The variable name used in function.json.
Returns:
queueName
public abstract String queueName()
Defines the name of the storage queue to which to bind.
Returns:
Applies to
Azure SDK for Java
Commentaires
https://aka.ms/ContentUserFeedback.
Bientôt disponible : Tout au long de 2024, nous allons supprimer progressivement GitHub Issues comme mécanisme de commentaires pour le contenu et le remplacer par un nouveau système de commentaires. Pour plus d’informations, consultezEnvoyer et afficher des commentaires pour