Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18000
Thanks! Merging to master/2.2
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18000
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77051/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18000
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/18000
**[Test build #77051 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77051/testReport)**
for PR 18000 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18000
LGTM pending Jenkins
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18000
**[Test build #77051 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77051/testReport)**
for PR 18000 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/18000
Seems jenkins doesn't work for now.
---
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
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18000
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 this feature
enabled and wishes so, or if
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18000
test 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 so,
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18000
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/18000
Based on the discussion in https://github.com/apache/parquet-mr/pull/361,
it does not sound Parquet will support it in the short term. We might need to
live with it for a long time.
---
If
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18000
LGTM, is parquet going to fix it in the future? or is there any official
way to support filter push down for column names with dot?
---
If your project is set up for it, you can reply to this
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/18000
LGTM
---
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
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18000
I would rather like to say it is a limitation in Parquet API. It looks
there is no way to set column names having dots in Parquet filters properly.
https://github.com/apache/spark/pull/17680
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18000
a high-level question, is it a parquet bug or Spark doesn't use parquet
reader correctly?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18000
Thank you @viirya.
---
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 viirya commented on the issue:
https://github.com/apache/spark/pull/18000
Sounds ok for me.
---
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
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18000
Just to make sure, I don't feel strongly for both comments @viirya. I am
willing to fix if you feel strongly. Please let me know.
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18000
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/18000
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77026/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18000
**[Test build #77026 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77026/testReport)**
for PR 18000 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18000
@viirya, I addressed your comments. Could you take another look when you
have sometime?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18000
**[Test build #77026 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77026/testReport)**
for PR 18000 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18000
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76987/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18000
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76989/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18000
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/18000
**[Test build #76989 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76989/testReport)**
for PR 18000 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18000
**[Test build #76987 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76987/testReport)**
for PR 18000 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18000
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/18000
**[Test build #76989 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76989/testReport)**
for PR 18000 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18000
**[Test build #76987 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76987/testReport)**
for PR 18000 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18000
^ Yea, maybe. we need to make sure
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18000
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76958/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18000
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/18000
**[Test build #76958 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76958/testReport)**
for PR 18000 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18000
In addition, we need to know the limitation of column names in Parquet. See
the related PR in Parquet: https://github.com/apache/parquet-mr/pull/361
---
If your project is set up for it, you
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18000
Now, the fix is much safer for merging to 2.2. Will review the test case
later.
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18000
**[Test build #76958 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76958/testReport)**
for PR 18000 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18000
cc @gatorsmile who reviewed the latter way in that PR, @cloud-fan who
reviewed my previous Parquet related PR, @liancheng and @viirya who I believe
is used to this code path, @ash211 who found
39 matches
Mail list logo
