-
Notifications
You must be signed in to change notification settings - Fork 4.8k
HIVE-29296: Remove getPrimaryKeys codes from beeline module #6157
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
base: master
Are you sure you want to change the base?
Conversation
| if (row.isMeta) { | ||
| v = beeLine.getColorBuffer().center(row.values[i], row.sizes[i]); | ||
| if (beeLine.getOpts().getColor() && rows.isPrimaryKeyCol(i)) { | ||
| buf.cyan(v.getMono()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Retrieving the primary key in Beeline is just for coloring the output. Removing this code blocks is safe.
|
|
why not simply revert JIRA that introduced PK fetching? |
The code for PK in Beeline was introduced during the implementation of HS2, rather than being implemented through a separate JIRA. See 96083e7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
|
According to my memory, removing this part of the code means the coloring output only means that the header has different font type than the result set data. |
As I mentioned, this part of the code relates to the primary key and has never taken effect in Hive beeline, so I'm not very clear about the color or font of its output display.
Regarding whether to remove the entire coloring functionality code, I'm not entirely sure if there are real-world users who actually use the color option. However, through a Google search for the keyword |



What changes were proposed in this pull request?
Why are the changes needed?
Please see HIVE-29213 & and HIVE-29296 to check the details.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Local Beeline test.