Github user liancheng commented on the issue:
https://github.com/apache/spark/pull/18181
@rdblue @mallman Thanks for the comments! As mentioned in the JIRA ticket,
we've decided to preserve parquet-mr 1.8.2. Instead, we'll add a release notes
entry to suggest using parquet-avro 1.8.1
Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/18181
It sounds like we should plan on a 1.8.3 and a 1.9.1 soon in the Parquet
community. I'll start this up.
On Fri, Jun 2, 2017 at 9:47 AM, Michael Allman
wrote:
> I can't speak
Github user mallman commented on the issue:
https://github.com/apache/spark/pull/18181
I can't speak to Parquet 1.8.x anymore. We use Parquet 1.9.0 plus a patch
for https://issues.apache.org/jira/browse/PARQUET-783 and have had no problems.
---
If your project is set up for it, you c
Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/18181
-1, with comments on the JIRA issue. I think it is better to include the
Parquet fixes in 1.8.2 since Parquet doesn't pull in Avro 1.8.1 - that happens
when users declare their own dependency on parq
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/18181
Also, cc @rdblue and @mallman .
---
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
enabl
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18181
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18181
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77673/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18181
**[Test build #77673 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77673/testReport)**
for PR 18181 at commit
[`c956201`](https://github.com/apache/spark/commit/c
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18181
**[Test build #77673 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77673/testReport)**
for PR 18181 at commit
[`c956201`](https://github.com/apache/spark/commit/c9
Github user liancheng commented on the issue:
https://github.com/apache/spark/pull/18181
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 so,
Github user liancheng commented on the issue:
https://github.com/apache/spark/pull/18181
Unfortunately, rolling back parquet-mr to 1.8.1 brings back
[PARQUET-389][1], which breaks multiple test cases involving schema evolution
(add a new column to a Parquet table and filter on that co
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18181
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77669/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18181
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18181
**[Test build #77669 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77669/testReport)**
for PR 18181 at commit
[`c956201`](https://github.com/apache/spark/commit/c9
Github user liancheng commented on the issue:
https://github.com/apache/spark/pull/18181
@viirya Thanks for reminding! I'm reverting that one.
---
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 liancheng commented on the issue:
https://github.com/apache/spark/pull/18181
@dongjoon-hyun I already reverted PR #16751 manually but forgot to mention
it in the PR description.
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18181
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77662/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18181
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18181
**[Test build #77662 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77662/testReport)**
for PR 18181 at commit
[`cf461d0`](https://github.com/apache/spark/commit/c
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/18181
@liancheng After upgrading to Parquet 1.8.2, #16756 is another PR merged
to remove a workaround for old Parquet issue. We should revert it too if
rolling back parquet-mr 1.8.1.
---
If your project
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/18181
Oh, it's already there in the code. Please just update the PR description.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If yo
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/18181
Sorry for this trouble. @liancheng .
Could you revert https://github.com/apache/spark/pull/16751 , too?
---
If your project is set up for it, you can reply to this email and have your
repl
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18181
**[Test build #77662 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77662/testReport)**
for PR 18181 at commit
[`cf461d0`](https://github.com/apache/spark/commit/cf
23 matches
Mail list logo