Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Verify ConnectionUnvailable exception usage in Sink Implementation #1474

Closed
mohanvive opened this issue Aug 29, 2019 · 7 comments
Closed

Verify ConnectionUnvailable exception usage in Sink Implementation #1474

mohanvive opened this issue Aug 29, 2019 · 7 comments
Assignees
@mohanvive
Labels
priority/high type/task

Comments

@mohanvive
Copy link
Contributor

Description:
With the latest changes [1] in Siddhi, retry flow will get activated only when ConnectionUnavailableException thrown by the sink implementation. Then we need to verify this for all the existing sink extensions.

[1] #1473
@mohanvive mohanvive mentioned this issue Sep 13, 2019
Merged
@mohanvive
Copy link
Contributor Author

Completed for NATS, Kafka & RabbitMQ

@mohanvive mohanvive self-assigned this Oct 2, 2019
@mohanvive
Copy link
Contributor Author

mohanvive commented Oct 2, 2019 •
edited
Loading

Handled already in email sink.

@mohanvive
Copy link
Contributor Author

Handled already in tcp sink.

@mohanvive
Copy link
Contributor Author

Handled already in Prometheus sink...

@mohanvive
Copy link
Contributor Author

mohanvive commented Oct 2, 2019 •
edited
Loading

Not fixed in googlepubsub yet..

@mohanvive
Copy link
Contributor Author

In gRpc, call-sink looks good. But default gRpc has the issue.

This was referenced Oct 3, 2019
Open
Open
@mohanvive
Copy link
Contributor Author

Respective issues are created for both gRpc and googlepubsub ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mohanvive mohanvive

Labels
priority/high type/task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mohanvive