-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-16004] [SQL] Correctly display "Last Access Time" of CatalogTable #13720
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
Closed
Closed
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
358ac0d
improve the disply of CatalogTable information
0fe835d
fix the tests failure
25510f5
Merge remote-tracking branch 'upstream/master' into SPARK-16004
26b9d79
Merge remote-tracking branch 'upstream/master' into SPARK-16004
8e7b271
Merge remote-tracking branch 'upstream/master' into SPARK-16004
90c3ff0
revert user name
da8b77c
Merge remote-tracking branch 'upstream/master' into SPARK-16004
4c9e295
revert comment to use null
e93b72a
remove space
a72800c
add test cases
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -265,6 +265,23 @@ class DDLSuite extends QueryTest with SharedSQLContext with BeforeAndAfterEach { | |
| } | ||
| } | ||
|
|
||
| test("Describe Table") { | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This test case does not verify the issue you fixed, I think |
||
| val tabName = "tab1" | ||
| withTable(tabName) { | ||
| sql(s"CREATE TABLE $tabName(a int comment 'test')") | ||
|
|
||
| assert(sql(s"DESC $tabName").collect().length == 1) | ||
|
|
||
| assert( | ||
| sql(s"DESC FORMATTED $tabName").collect() | ||
| .exists(_.getString(0) == "# Storage Information")) | ||
|
|
||
| assert( | ||
| sql(s"DESC EXTENDED $tabName").collect() | ||
| .exists(_.getString(0) == "# Detailed Table Information")) | ||
| } | ||
| } | ||
|
|
||
| test("Alter/Describe Database") { | ||
| withTempDir { tmpDir => | ||
| val path = tmpDir.toString | ||
|
|
||
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.
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.
I don't feel strongly about it, but seems like elsewhere an empty string is used for no values. This seems slightly preferable.
Uh oh!
There was an error while loading. Please reload this page.
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.
Here is the code from Hive (it is using 0 as initial last access value):
File: MetaDataFormatUtils.java
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.
Yes, but the rest of this code doesn't use that logic. It returns "" in code around this area.
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.
I prefer empty string here, cc @yhuai @liancheng what do you think?
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.
Empty string looks fine to me.
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.
Please follow this?