Github user viirya commented on the issue:
https://github.com/apache/spark/pull/17424
I am not sure if it helps review by dumping the output of `DESC EXTENDED
FUNCTION` to the test. We may not frequently change the output as I see. IMHO,
It is hard to tell which is "correct" output
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17424
@viirya That is not only for document generator. It can help us
review/correct the output of `DESC FUNCTIONS EXTENDED`. You can find many
inconsistent parts we should correct when reading
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/17424
To document the functions available sounds good. But I am not sure if we
want to put this into test. Sounds like we use the test as document generator.
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17424
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75222/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17424
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/17424
**[Test build #75222 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75222/testReport)**
for PR 17424 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17424
**[Test build #75222 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75222/testReport)**
for PR 17424 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17424
retest this please
---
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/17424
@rxin Yes! After we add it to SQLQueryTestSuite, we can copy and paste the
contents to the document in
http://spark.apache.org/docs/latest/sql-programming-guide.html So far, our
Spark SQL users
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/17424
Hm - so this would require us to update the test suite every time there is
an update to the docs?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17424
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75201/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17424
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/17424
**[Test build #75201 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75201/testReport)**
for PR 17424 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17424
**[Test build #75201 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75201/testReport)**
for PR 17424 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17424
retest this please
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17424
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75194/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17424
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/17424
**[Test build #75194 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75194/testReport)**
for PR 17424 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17424
**[Test build #75194 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75194/testReport)**
for PR 17424 at commit
19 matches
Mail list logo
