Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18847
I see. Thanks!
---
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,
Github user dilipbiswal commented on the issue:
https://github.com/apache/spark/pull/18847
@gatorsmile Thanks !! To the best of my knowledge, we don't have the
problem of analyze table command failing with java.util.NoSuchElement exception
in 2.2. In 2.2, we used to add the column
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18847
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/18847
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80260/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18847
**[Test build #80260 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80260/testReport)**
for PR 18847 at commit
Github user dilipbiswal commented on the issue:
https://github.com/apache/spark/pull/18847
@gatorsmile I just created this PR for you take a look and decide if we
need to back port the above 3 PRs. The problem for SPARK-21599 does not exist
on 2.2 as it was introduced as part of
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18847
**[Test build #80260 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80260/testReport)**
for PR 18847 at commit
