docs: add guidelines for choosing Java vs Python API #449
+254
−1
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.
This PR adds documentation to help users decide between the Java and Python APIs by
clearly outlining their respective strengths, limitations, and recommended use cases.
The documentation includes:
This aims to improve clarity for new users and reduce ambiguity when selecting an API
for real-world projects.
Addresses #437
Issue Link-: #437
This PR only updates documentation and does not modify Python or runtime code.
The failing it-python checks appear unrelated and likely due to CI flakiness.
Requesting a rerun of the failing jobs.
Documentation Impact