AMBARI-26310: Refactor zoo.cfg.j2 to Align with Python3 Migration #3944
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hello @arshadmohammad @JiaLiangC @prabhjyotsingh Could you please review this.? thanks |
guluo2016
approved these changes
Feb 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This Proposed minor changee aims to refactor zoo.cfg.j2 to follow Python 3.x conventions.
More details are added at AMBARI-26310
How was this patch tested?
the current implementation is functional, and this refactoring is a proactive step to modernize the codebase, and it worked on local deplotments seamlessly as it was earlier..
Please review Ambari Contributing Guide before opening a pull request.