Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/17024
@aramesh117 I just opened #17789 to finish the rest work. All credits will
go to you when merging the new PR.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/17024
@aramesh117 do you have time to work on this PR recently? We need to merge
this PR ASAP in order to get it into 2.2.0.
---
If your project is set up for it, you can reply to this email and have
Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/17024
@aramesh117 Unfortunately, since this heavily affects streaming, I cannot
sign off on it without someone more familiar with spark streaming reviews it as
well.
---
If your project is set up for
Github user aramesh117 commented on the issue:
https://github.com/apache/spark/pull/17024
@mridulm Waiting for @tdas and @zsxwing has taken more than a month now. Is
there any other way we can reach them or is there anyone else that can take a
look at this merge request? This is a
Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/17024
It makes it possible to identify what the data within the file is
(compressed or not) - for user's perusal (it does not change anything for the
application, that is true).
But before you change
Github user aramesh117 commented on the issue:
https://github.com/apache/spark/pull/17024
@mridulm Sure I can add in a file extension based on the codec being used.
But is there a specific use case that adding an extension would solve?
---
If your project is set up for it, you can
Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/17024
I wonder if adding an extension (to the file) helps based on codec ...
---
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 mridulm commented on the issue:
https://github.com/apache/spark/pull/17024
@aramesh117 looks good !
I would also like someone working on streaming to chime in - since that is
a common usecase for checkpoint.
+CC @tdas, @zsxwing
---
If your project is set up
Github user aramesh117 commented on the issue:
https://github.com/apache/spark/pull/17024
@mridulm I've added a new commit. Thank you for the review! :)
---
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 mridulm commented on the issue:
https://github.com/apache/spark/pull/17024
+CC @tdas
---
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 aramesh117 commented on the issue:
https://github.com/apache/spark/pull/17024
@mridulm Thank you so much! I will definitely update with your suggestions.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17024
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
12 matches
Mail list logo
