HeartSaVioR edited a comment on pull request #30210:
URL: https://github.com/apache/spark/pull/30210#issuecomment-727138220
I was feeling odd and became feeling upset because my intention wasn't
change from the first comment and the intention was disregarded (at least
that's what I felt li
HeartSaVioR edited a comment on pull request #30210:
URL: https://github.com/apache/spark/pull/30210#issuecomment-727121487
And I also admit I have different voice on post-review. I agree post-review
would open the possibility for reviewers to review later who weren't active
during the rev
HeartSaVioR edited a comment on pull request #30210:
URL: https://github.com/apache/spark/pull/30210#issuecomment-727120756
I was writing a wall of text and Chrome happily (?) killed itself. Rewriting
one.
What I really asked you to do is exactly this. The practice is also happened
HeartSaVioR edited a comment on pull request #30210:
URL: https://github.com/apache/spark/pull/30210#issuecomment-726569827
I'd rather avoid the chance of "post-review" whenever possible, but I'd
admit everyone has different thoughts. I'm OK with it, and if that's considered
here (and no o
HeartSaVioR edited a comment on pull request #30210:
URL: https://github.com/apache/spark/pull/30210#issuecomment-726569827
I'd rather avoid the chance of "post-review" whenever possible, but I'd
admit everyone has different thoughts. I'm OK with it, and if that's considered
here (and no o
HeartSaVioR edited a comment on pull request #30210:
URL: https://github.com/apache/spark/pull/30210#issuecomment-726418896
That's not my point. There's no indication I have produced all review
comments (while actually I produced all review comments), and review comment
author would be the
HeartSaVioR edited a comment on pull request #30210:
URL: https://github.com/apache/spark/pull/30210#issuecomment-721373759
That's the chicken and egg problem, you know. dev@ list is not so active
because all the important discussions aren't passing through the dev list,
which is I think b
HeartSaVioR edited a comment on pull request #30210:
URL: https://github.com/apache/spark/pull/30210#issuecomment-721373759
That's the chicken and egg problem, you know. dev@ list is not so active
because all the important discussions aren't passing through the dev list,
which is I think b
HeartSaVioR edited a comment on pull request #30210:
URL: https://github.com/apache/spark/pull/30210#issuecomment-720876379
No I don't have real case for knowing and taking the risk. Probably I could
create some query which could evade the issue, but I agree that's more likely
in theory an
