Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16896
Sorry. I didn't realized too.
---
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 davies commented on the issue:
https://github.com/apache/spark/pull/16896
My bad, did not realized that, sorry.
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16896
This PR didn't go through jenkins and break the build. I've reverted it
from master and branch 2.1.
@JasonMWhite can you submit a new PR please? thanks
---
If your project is set up for
Github user davies commented on the issue:
https://github.com/apache/spark/pull/16896
Merged into master and 2.1 branch.
---
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 davies commented on the issue:
https://github.com/apache/spark/pull/16896
lgtm, will merge it when I get a chance.
---
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 dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16896
+1 LGTM.
Could you review and merge this please, @davies ?
---
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 JasonMWhite commented on the issue:
https://github.com/apache/spark/pull/16896
This PR is pretty tiny, and corrects a problem that led to corrupt Parquet
files in our case. Can anyone spare a minute to review?
---
If your project is set up for it, you can reply to this
Github user JasonMWhite commented on the issue:
https://github.com/apache/spark/pull/16896
Ping @davies
---
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 JasonMWhite commented on the issue:
https://github.com/apache/spark/pull/16896
Modified as suggested. Don't think this has been through CI at all yet.
---
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 davies commented on the issue:
https://github.com/apache/spark/pull/16896
Just one minor comment
---
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 dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16896
Hi, @davies .
Could you review this PR?
---
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
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16896
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16896
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 project does not have this
13 matches
Mail list logo
