Skip to content

Conversation

@rpuch
Copy link
Contributor

@rpuch rpuch commented Dec 5, 2022

* Thrown when consistent ID cannot be resolved to a {@link ClusterNode} instance (i.e. when
* there is no node with such consistent ID in the physical topology).
*/
public class ConsistentIdNotResolvedException extends IgniteException {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should create proper error group and id for new exceptions that we create, otherwise we'll never migrate anything

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added a group and error code, wired it in the exception constructor

@ibessonov ibessonov merged commit 9548206 into apache:main Dec 6, 2022
@ibessonov ibessonov deleted the ignite-18319 branch December 6, 2022 12:03
lowka pushed a commit to gridgain/apache-ignite-3 that referenced this pull request Mar 18, 2023
lowka pushed a commit to gridgain/apache-ignite-3 that referenced this pull request Apr 19, 2023
isapego pushed a commit to isapego/ignite-3 that referenced this pull request Dec 26, 2024
Add `ignite.error.handling.policy` config property with values: 
* `LOG_ONLY` - log and continue (default)
* `STOP_TASK` - throw exception to Kafka, which can stop the task when `errors.tolerance` is `none`
* `DEAD_LETTER_QUEUE` - pass failed items to `errantRecordReporter`, which sends them to the configured dead letter queue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants