You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2021/08/25 11:40:28 UTC

[GitHub] [camel-kamelets] wingerx opened a new issue #467: How does many options design when use camel components in kamelets

wingerx opened a new issue #467:
URL: https://github.com/apache/camel-kamelets/issues/467


   Hey,
   Could anyone help me?
   I created Kameletbinding for DBZ component by kamelets developer guide.But i want to configure only the required options, and the optional options are filled in as needed in kamelets binding yaml file. There are so many options for DBZ, and it is not conducive to subsequent expansion if all are defined. 
   There is an [additionalProperties](https://camel.apache.org/components/latest/debezium-mysql-component.html#_component_options) option in DBZ components, but I don’t know how to configure it in yaml and make it take effect.
   
   Any ideas?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [camel-kamelets] oscerd commented on issue #467: How does many optional options design when use camel components in kamelets

Posted by GitBox <gi...@apache.org>.
oscerd commented on issue #467:
URL: https://github.com/apache/camel-kamelets/issues/467#issuecomment-908239618


   In camel component you have multiple parameters to tune your route and set everything. A Kamelet needs to define just a subset of the options to perform a pre-defined operation. So in a Kamelet you'll never see all the possible options listed and configurabile, because in terms of Kamelets this is conceptually wrong.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [camel-kamelets] oscerd closed issue #467: How does many optional options design when use camel components in kamelets

Posted by GitBox <gi...@apache.org>.
oscerd closed issue #467:
URL: https://github.com/apache/camel-kamelets/issues/467


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [camel-kamelets] oscerd edited a comment on issue #467: How does many optional options design when use camel components in kamelets

Posted by GitBox <gi...@apache.org>.
oscerd edited a comment on issue #467:
URL: https://github.com/apache/camel-kamelets/issues/467#issuecomment-906912981


   You need to think to Kamelets as pre-baked actions, so there are no means in having all the possibile options available as parameters in the kamelet.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [camel-kamelets] oscerd closed issue #467: How does many optional options design when use camel components in kamelets

Posted by GitBox <gi...@apache.org>.
oscerd closed issue #467:
URL: https://github.com/apache/camel-kamelets/issues/467


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [camel-kamelets] wingerx commented on issue #467: How does many optional options design when use camel components in kamelets

Posted by GitBox <gi...@apache.org>.
wingerx commented on issue #467:
URL: https://github.com/apache/camel-kamelets/issues/467#issuecomment-908818945


   ok, I see.
   Thanks a lot. @oscerd 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [camel-kamelets] wingerx commented on issue #467: How does many optional options design when use camel components in kamelets

Posted by GitBox <gi...@apache.org>.
wingerx commented on issue #467:
URL: https://github.com/apache/camel-kamelets/issues/467#issuecomment-908238309


   I'm sorry,i don't understand.
   Can you explain this for me please?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [camel-kamelets] oscerd closed issue #467: How does many optional options design when use camel components in kamelets

Posted by GitBox <gi...@apache.org>.
oscerd closed issue #467:
URL: https://github.com/apache/camel-kamelets/issues/467


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [camel-kamelets] wingerx commented on issue #467: How does many optional options design when use camel components in kamelets

Posted by GitBox <gi...@apache.org>.
wingerx commented on issue #467:
URL: https://github.com/apache/camel-kamelets/issues/467#issuecomment-908818945


   ok, I see.
   Thanks a lot. @oscerd 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [camel-kamelets] oscerd commented on issue #467: How does many optional options design when use camel components in kamelets

Posted by GitBox <gi...@apache.org>.
oscerd commented on issue #467:
URL: https://github.com/apache/camel-kamelets/issues/467#issuecomment-906912981


   You need to think to Kamelets as pre-baked actions, so there is no means in having all the possibile options available as parameters in the kamelet.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org