-
Notifications
You must be signed in to change notification settings - Fork 319
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
[Improvement] Add how to develop Gravitino trino connector for new developers #1193
Labels
improvement
Improvements on everything
Comments
Hi, @yuqi1129. I had to compile the connector and then build a docker image for debugging. Is there any easier way to quickly start a development server? Can you share your experience about that? |
@xiacongling |
This was referenced Mar 6, 2024
@xiacongling |
yuqi1129
added a commit
that referenced
this issue
Mar 14, 2024
…connector locally. (#2446) ### What changes were proposed in this pull request? Add a document about how to debug develop and debug `trino-connector` locally. ### Why are the changes needed? To make users more knowledgeable about Gravitino trino connector. Fix: #1193 ### Does this PR introduce _any_ user-facing change? N/A. ### How was this patch tested? N/A.
yijhenlin
pushed a commit
to yijhenlin/gravitino
that referenced
this issue
Mar 14, 2024
…trino connector locally. (apache#2446) ### What changes were proposed in this pull request? Add a document about how to debug develop and debug `trino-connector` locally. ### Why are the changes needed? To make users more knowledgeable about Gravitino trino connector. Fix: apache#1193 ### Does this PR introduce _any_ user-facing change? N/A. ### How was this patch tested? N/A.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to be improved?
There seem to be no instructions on how to debug and develop the Gravitino Trino connector locally for new developers. We need to add some documents about it.
How should we improve?
No response
The text was updated successfully, but these errors were encountered: