HyukjinKwon commented on pull request #29067:
URL: https://github.com/apache/spark/pull/29067#issuecomment-688939879
Thank you @revans2
This is an automated message from the Apache Git Service.
To respond to the message,
HyukjinKwon commented on pull request #29067:
URL: https://github.com/apache/spark/pull/29067#issuecomment-688614177
Just for a bit of more contexts, the commits are regularly digested and
shared into the dev mailing list after being summarized. The PRs introducing
APIs are usually
HyukjinKwon commented on pull request #29067:
URL: https://github.com/apache/spark/pull/29067#issuecomment-688613392
Just for a bit of more contexts, the commits are regularly digested and
shared into the dev mailing list after being summarized. The PRs introducing
APIs are usually
HyukjinKwon commented on pull request #29067:
URL: https://github.com/apache/spark/pull/29067#issuecomment-688578327
I think he just simply meant the naming of APIs such as `decompressColumnar`
in the PR description are not matched to the actual APIs added (e.g., after
HyukjinKwon commented on pull request #29067:
URL: https://github.com/apache/spark/pull/29067#issuecomment-667634213
retest this please
This is an automated message from the Apache Git Service.
To respond to the message,
HyukjinKwon commented on pull request #29067:
URL: https://github.com/apache/spark/pull/29067#issuecomment-667432114
retest this please
This is an automated message from the Apache Git Service.
To respond to the message,
HyukjinKwon commented on pull request #29067:
URL: https://github.com/apache/spark/pull/29067#issuecomment-666898969
Looks getting closer to go to me too.
This is an automated message from the Apache Git Service.
To respond
HyukjinKwon commented on pull request #29067:
URL: https://github.com/apache/spark/pull/29067#issuecomment-666889187
https://github.com/apache/spark/pull/29067#issuecomment-666462746, @revans2,
there was a bit of unexpected test failures in GitHub Actions, and they are
fixed now. The
HyukjinKwon commented on pull request #29067:
URL: https://github.com/apache/spark/pull/29067#issuecomment-659464261
@tgravescs, I think he wanted to know the plan and how we will merge these
into one codebase with DSv2 in the end. Looks valid concern to me and I guess
this is his main
HyukjinKwon commented on pull request #29067:
URL: https://github.com/apache/spark/pull/29067#issuecomment-659306235
Okay, I took a look too. I think the actual API here itself is not very big
as it seems. It is a developer API. The idea makes sense to me too.
I guess the main
HyukjinKwon commented on pull request #29067:
URL: https://github.com/apache/spark/pull/29067#issuecomment-659141249
@maropu, per the documentation [Spark Project Improvement Proposals
(SPIP)](http://spark.apache.org/improvement-proposals.html), if you feel like
it needs an SPIP, it does.
HyukjinKwon commented on pull request #29067:
URL: https://github.com/apache/spark/pull/29067#issuecomment-659139846
I just saw the comment. Thanks for summarizing @revans2.
This is an automated message from the Apache Git
HyukjinKwon commented on pull request #29067:
URL: https://github.com/apache/spark/pull/29067#issuecomment-657080714
@revans2, would you mind outlining which APIs do you propose in the PR
description? Seems like it's not only configurations but classes. It would be
great if it describes
13 matches
Mail list logo
