HeartSaVioR commented on pull request #31355: URL: https://github.com/apache/spark/pull/31355#issuecomment-768580667
I'd like to see our preference on dealing with "possible (but just floated ideas now) improvements" in public API. I think this use case is clear, and the change fulfills the requirement if we only consider such use case. Possible improvements might require the API to be changed as a backward incompatible way; I guess that is the reason @aokolnychyi said we should discuss. But again for me this use case is only solid, others are just ideas/possibility. One possible deal is adding this first, and give us enough time (feature freeze on 3.2.0) to make improvement with "free to break". Even after 3.2.0 we could make an excuse to break based on the fact these classes are marked as Experimental, though we'd like to minimize the occurrence. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
