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.

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

Lg rabbitmq retry #266

Merged
merged 6 commits into from
Jul 6, 2022
Merged

Lg rabbitmq retry #266

merged 6 commits into from
Jul 6, 2022

Conversation

guptalakshya92
Copy link
Collaborator

No description provided.

(:count (channel-retry-config topic-entity channel)))

(defn get-configured-retry-count []
Copy link
Contributor

Choose a reason for hiding this comment

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

This method should go inside ziggurat.config. Missed it while pairing

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

ziggurat.config is giving whole configuration and we are only fetching rabbit-mq retry count which is required for our use case. So i feel this file is the right place for this method as other similar methods are already there.

Copy link
Contributor

Choose a reason for hiding this comment

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

hmm. fine. since channel retry configuration is also coming from producer.clj, it seems fine. But, given that we're just fetching configuration and not doing anything produce specific, ziggurat.config would have been the right place even for getting channel retry count.

You can look at other helper methods in ziggurat.config

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Moved config as per suggestion, kindly check and merge.

@mjayprateek mjayprateek merged commit 1c46e9f into master Jul 6, 2022
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.

None yet

2 participants