Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/17394
Hi, All.
I made a PR, https://github.com/apache/spark/pull/18203.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/17394
Thank you for advice. I'll make a PR soon.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17394
Sure, we can remove it. Feel free to submit a PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/17394
What I mean is to removing `# col_name data_type comment` in case of `DESC
t`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/17394
It's reported at https://issues.apache.org/jira/browse/SPARK-20954 .
If the current one is better, could you give some advice on that? :)
---
If your project is set up for it, you can
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/17394
Yep. That one.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17394
Add the following line when issuing `DESC t` on partitioned tables?
` # col_namedata_type comment`
---
If your project is set up for it, you can reply to this
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/17394
Hi, All .
This seems to be incompatible changes even in `DESC t` from 2.2.0.
Is it better to be compatible on `DESC t` which has no `EXTENDED|FORMATTED`?
---
If your project is set up
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17394
Thanks! Merging to master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75497/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17394
**[Test build #75497 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75497/testReport)**
for PR 17394 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17394
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17394
**[Test build #75497 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75497/testReport)**
for PR 17394 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75455/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17394
**[Test build #75455 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75455/testReport)**
for PR 17394 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17394
**[Test build #75455 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75455/testReport)**
for PR 17394 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75446/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17394
**[Test build #75446 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75446/testReport)**
for PR 17394 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17394
**[Test build #75446 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75446/testReport)**
for PR 17394 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75440/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17394
**[Test build #75440 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75440/testReport)**
for PR 17394 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17394
**[Test build #75440 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75440/testReport)**
for PR 17394 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75370/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17394
**[Test build #75370 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75370/testReport)**
for PR 17394 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17394
**[Test build #75370 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75370/testReport)**
for PR 17394 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17394
Hive DESC TABLE has different formats. We hit many error due to it. I think
we can disable it when comparing the results between Hive and Spark SQL.
---
If your project is set up for it, you
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75326/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17394
**[Test build #75326 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75326/testReport)**
for PR 17394 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17394
**[Test build #75326 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75326/testReport)**
for PR 17394 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17394
Yes. We do not need to keep the difference between `DESC EXTENDED` and
`DESC FORMATTED`
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75295/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17394
seems `DESC EXTENDED` is totally useless... How about we deprecate `DESC
EXTENDED` at parser and implement it with `DESC FORMATTED`?
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75294/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17394
**[Test build #75294 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75294/testReport)**
for PR 17394 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17394
**[Test build #75295 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75295/testReport)**
for PR 17394 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17394
After refactoring, I think `DESC FORMATTED` might be more useful for users.
`DESC FORMATTED` outputs the metadata in a more formatted way. Users can
query it using the key value (stored
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17394
**[Test build #75294 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75294/testReport)**
for PR 17394 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17394
after this PR, what's the difference between `DESC EXTENDED` and `DESC
FORMATTED`?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/17394
Please update the PR description too since you update the title.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75243/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17394
**[Test build #75243 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75243/testReport)**
for PR 17394 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17394
**[Test build #75243 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75243/testReport)**
for PR 17394 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75232/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17394
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17394
**[Test build #75232 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75232/testReport)**
for PR 17394 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17394
**[Test build #75232 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75232/testReport)**
for PR 17394 at commit
55 matches
Mail list logo
