This is an automated email from the ASF dual-hosted git repository.

acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git

commit 741c340ee251777fdd4e9b3579d835661a9ab9f6
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Tue Sep 8 18:07:02 2020 +0200

    Regen website docs
---
 docs/components/modules/ROOT/pages/nsq-component.adoc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docs/components/modules/ROOT/pages/nsq-component.adoc 
b/docs/components/modules/ROOT/pages/nsq-component.adoc
index 8137dd5..382e249 100644
--- a/docs/components/modules/ROOT/pages/nsq-component.adoc
+++ b/docs/components/modules/ROOT/pages/nsq-component.adoc
@@ -79,7 +79,7 @@ with the following path and query parameters:
 |===
 
 
-=== Query Parameters (18 parameters):
+=== Query Parameters (19 parameters):
 
 
 [width="100%",cols="2,5,^1,2",options="header"]
@@ -90,6 +90,7 @@ with the following path and query parameters:
 | *autoFinish* (consumer) | Automatically finish the NSQ Message when it is 
retrieved from the queue and before the Exchange is processed | true | Boolean
 | *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the 
Camel routing Error Handler, which mean any exceptions occurred while the 
consumer is trying to pickup incoming messages, or the likes, will now be 
processed as a message and handled by the routing Error Handler. By default the 
consumer will use the org.apache.camel.spi.ExceptionHandler to deal with 
exceptions, that will be logged at WARN or ERROR level and ignored. | false | 
boolean
 | *channel* (consumer) | The NSQ channel |  | String
+| *customNSQLookup* (consumer) | A Custom NSQ lookup implementation |  | 
NSQLookup
 | *lookupInterval* (consumer) | The lookup interval | 5000 | long
 | *lookupServerPort* (consumer) | The NSQ lookup server port | 4161 | int
 | *messageTimeout* (consumer) | The NSQ consumer timeout period for messages 
retrieved from the queue. A value of -1 is the server default | -1 | long

Reply via email to