HeartSaVioR commented on pull request #29066: URL: https://github.com/apache/spark/pull/29066#issuecomment-736073015
I'm OK to go in parallel - as I said write path is more critical for the functionality so read path shouldn't block this. The main point here may be "where" we should put the new interfaces. If I understand correctly, the direction of the PR (and the question) is rather we unify the interfaces between read path and write path, assuming the new interfaces could cover the further read path optimization as well. (I'm rather novice here, hence no opinion on the coverage.) It also sounds a good approach if we go with separate package for separate path, and let them evolve separately, and eventually merge once they've stabilized. The downside would be that it would require more changes on downstream during evolution. ---------------------------------------------------------------- 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]
