Github user gatorsmile closed the pull request at:
https://github.com/apache/spark/pull/12992
---
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 feature is
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12992#issuecomment-217970821
Ok, let me close it. 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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12992#issuecomment-217952985
No - I don't think this should go in the public API. This is hardly
relevant to end users.
---
If your project is set up for it, you can reply to this email and hav
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12992#issuecomment-217864072
uh,,, I see. Should we move it to the DataSet public API?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/12992#issuecomment-217788397
@gatorsmile we already have such API, see:
https://github.com/apache/spark/blob/8dc3987d095ae01ad80c89b8f052f231e0807990/sql/core/src/main/scala/org/apache/spark
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12992#issuecomment-217750373
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12992#issuecomment-217750374
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12992#issuecomment-217750329
**[Test build #58111 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58111/consoleFull)**
for PR 12992 at commit
[`f716b10`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12992#issuecomment-217746435
**[Test build #58111 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58111/consoleFull)**
for PR 12992 at commit
[`f716b10`](https://gi
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12992#issuecomment-217746275
cc @rxin Let me know if this PR is valid. 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
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/12992
[SPARK-15216] [SQL] Add a new Dataset API explainCodegen
What changes were proposed in this pull request?
Reading codegen output is important for developers to debug. So far,
outputting
11 matches
Mail list logo