-
Notifications
You must be signed in to change notification settings - Fork 4.8k
HIVE-25495: Upgrade JLine to version 3 #3069
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
Conversation
|
I created it partially based on pull request 2617. |
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
|
I just found this one, is there a chance that we can reopen, rebase @LA-Toth? |
|
I had one and only one issue: I was unable to run the tests to have a usable result. These are unstable even in @kgyrtkirk's docker image that is behind the jenkins AFAIK. So I was unable to decide if the current PR woks or not. |
|
I still can't run the tests: latest kgyrtkirk/hive-dev-box:executor docker image and |
|
with this change: diff --git a/beeline/src/test/org/apache/hive/beeline/cli/TestHiveCli.java b/beeline/src/test/org/apache/hive/beeline/cli/TestHiveCli.java
private void redirectOutputStream() { |
|
@LA-Toth I have re-opened this to get some reviews. Seems like there is a conflict. Any chance we could have this rebased? seems like there is a conflict. |
|
Rebase itself seems to be relatively easy, the tests are still broken, at least: The first conflict during the rebase: After two years I don't remember too much, it was just a regular change for me. And I haven't used Java for a while. Please feel free to improve my changes. |
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
What changes were proposed in this pull request?
Why are the changes needed?
It's a step required to use JDK 17
Does this PR introduce any user-facing change?
No.
How was this patch tested?
By existing tests.