Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8403
---
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 enab
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8403#issuecomment-134516579
I've merged this.
---
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/8403#issuecomment-134506195
This PR LGTM.
@cloud-fan Same opinion as @rxin. Filter push-down itself isn't a critical
path.
---
If your project is set up for it, you can reply to this em
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8403#issuecomment-134505721
This is once for query - isn't it? It'd make sense to specialize the input,
but I don't think it's worth it for the filter pushdowns.
---
If your project is set up for it
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/8403#issuecomment-134471917
Like the `buildScan` in data source, we shoud not expose internal types
outside spark sql, but we also need to provide the ability to build efficient
data source by us
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8403#issuecomment-134443205
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8403#issuecomment-134443206
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8403#issuecomment-134443119
[Test build #41490 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41490/console)
for PR 8403 at commit
[`c3fb4eb`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8403#issuecomment-134415771
[Test build #41490 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41490/consoleFull)
for PR 8403 at commit
[`c3fb4eb`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8403#issuecomment-134415375
Merged build started.
---
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/8403#issuecomment-134415366
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8403#issuecomment-134412052
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8403#issuecomment-134412050
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8403#issuecomment-134411921
[Test build #41486 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41486/console)
for PR 8403 at commit
[`1a3d053`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8403#issuecomment-134406632
[Test build #41486 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41486/consoleFull)
for PR 8403 at commit
[`1a3d053`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8403#issuecomment-134406190
Merged build started.
---
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/8403#issuecomment-134406167
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8403#issuecomment-134404076
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8403#issuecomment-134404079
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8403#issuecomment-134404040
[Test build #41482 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41482/console)
for PR 8403 at commit
[`6af0a45`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8403#issuecomment-134399268
[Test build #41482 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41482/consoleFull)
for PR 8403 at commit
[`6af0a45`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8403#issuecomment-134398620
Merged build started.
---
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/8403#issuecomment-134398599
Merged build triggered.
---
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 h
GitHub user JoshRosen opened a pull request:
https://github.com/apache/spark/pull/8403
[SPARK-10195] [SQL] Data sources Filter should not expose internal types
Spark SQL's data sources API exposes Catalyst's internal types through its
Filter interfaces. This is a problem because typ
24 matches
Mail list logo
