Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/3870
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/3870#issuecomment-70791040
Since this issue has been fixed by #3990, we can close it.
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/3870#issuecomment-70791044
close this issue
---
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/3870#issuecomment-69479152
Thanks for figuring this out and proposing a solution! I guess our test
cases missed this since they always perform later column reordering.
I'm a little
Github user rahulaggarwalguavus commented on the pull request:
https://github.com/apache/spark/pull/3870#issuecomment-69485404
Thanks for reviewing. Yes, the approach you took in #3990 avoids this
performance penalty.
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3870#issuecomment-68632040
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3870#issuecomment-68632038
[Test build #25031 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/25031/consoleFull)
for PR 3870 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3870#issuecomment-68630113
[Test build #25031 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/25031/consoleFull)
for PR 3870 at commit
GitHub user rahulaggarwalguavus opened a pull request:
https://github.com/apache/spark/pull/3870
SPARK-5049: ParquetTableScan always prepends the values of partition col...
...umns in output rows irrespective of the order of the partition columns
in the original SELECT query
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3870#issuecomment-68506985
[Test build #24989 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24989/consoleFull)
for PR 3870 at commit
Github user ash211 commented on the pull request:
https://github.com/apache/spark/pull/3870#issuecomment-68506968
Jenkins this is ok to test
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3870#issuecomment-68486322
Can one of the admins verify this patch?
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3870#issuecomment-68507755
[Test build #24989 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24989/consoleFull)
for PR 3870 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3870#issuecomment-68507758
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
14 matches
Mail list logo
