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/01/22 14:49:56 UTC
[GitHub] [camel-k] lburgazzoli opened a new issue #1941: kamelet-binding : suport for error handling
lburgazzoli opened a new issue #1941:
URL: https://github.com/apache/camel-k/issues/1941
```yaml
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
name: telegram-text-source-to-kafka
spec:
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1alpha1
name: telegram-text-source
properties:
botToken: the-token-here
sink:
ref:
kind: KafkaTopic
apiVersion: kafka.strimzi.io/v1beta1
name: my-topic
error-handler:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1alpha1
name: retry-handler
properties:
...
```
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #1941: kamelet-binding : suport for error handling
Posted by GitBox <gi...@apache.org>.
squakez commented on issue #1941:
URL: https://github.com/apache/camel-k/issues/1941#issuecomment-801921852
Not sure about the underlying details of Camel, but we may think of giving the user the possibility to chose what to do based on the specific exception caught. Maybe the same [try-catch](https://camel.apache.org/manual/latest/try-catch-finally.html) could work out of the box if used in the `steps`. However I think it defeats the concept of hiding the complexity behind the scene as the user must know the java exception type that may be thrown. We may consider come back to this as advanced feature in a future refinement.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] heiko-braun edited a comment on issue #1941: kamelet-binding : suport for error handling
Posted by GitBox <gi...@apache.org>.
heiko-braun edited a comment on issue #1941:
URL: https://github.com/apache/camel-k/issues/1941#issuecomment-800947951
Is there wat to distinguish types of errors that might trigger an error handler in the first place? Thinking about something like this:
- Failure: External behavior is incorrect
- Fault: Discrepancy in code that causes a failure.
- Error: Human mistake that caused fault
Some examples that come to my mind to further illustrate this:
- Failure: Cannot connect to thirdparty system (i.e. transport level)
- Fault: Exception raised within the Camel DSL execution (i.e. syntax error)
- Error: Wrong credentials lead to authentication exceptions
If we could tell the difference between types of errors, we could supply more tailored error handling strategies (i.e. multiple error handlers)
Food for thought.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] heiko-braun edited a comment on issue #1941: kamelet-binding : suport for error handling
Posted by GitBox <gi...@apache.org>.
heiko-braun edited a comment on issue #1941:
URL: https://github.com/apache/camel-k/issues/1941#issuecomment-800947951
Is there wat to distinguish types of errors that might trigger an error handler in the first place?
Thinking about something like this:
- Failure: External behavior is incorrect
- Fault: Discrepancy in code that causes a failure.
- Error: Human mistake that caused fault
Some examples that come to my mind to further illustrate this:
- Failure: Cannot connect to thirdparty system (i.e. transport level)
- Fault: Exception raised within the Camel DSL execution (i.e. syntax error)
- Error: Wrong credentials lead to authentication exceptions
If we could tell the difference between types of errors, we could supply more tailored error handling strategies (i.e. multiple error handlers)
Food for thought.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] nicolaferraro closed issue #1941: kamelet-binding : suport for error handling
Posted by GitBox <gi...@apache.org>.
nicolaferraro closed issue #1941:
URL: https://github.com/apache/camel-k/issues/1941
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #1941: kamelet-binding : suport for error handling
Posted by GitBox <gi...@apache.org>.
squakez commented on issue #1941:
URL: https://github.com/apache/camel-k/issues/1941#issuecomment-799280861
I am having a look at it
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] heiko-braun commented on issue #1941: kamelet-binding : suport for error handling
Posted by GitBox <gi...@apache.org>.
heiko-braun commented on issue #1941:
URL: https://github.com/apache/camel-k/issues/1941#issuecomment-800947951
Is there wat to distinguish types of errors that might trigger an error handler in the first place? Thinking about something like this:
- Failure: External behavior is incorrect
- Fault: Discrepancy in code that causes a failure.
- Error: Human mistake that caused fault
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] lburgazzoli commented on issue #1941: kamelet-binding : suport for error handling
Posted by GitBox <gi...@apache.org>.
lburgazzoli commented on issue #1941:
URL: https://github.com/apache/camel-k/issues/1941#issuecomment-765457605
/cc @nicolaferraro
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org