nchammas commented on PR #44300: URL: https://github.com/apache/spark/pull/44300#issuecomment-1894096892
Silence on a PR usually means there is something wrong with it, so I am proactively trying to figure out how to move this idea forward. The possibilities I am considering are: 1. Committers disapprove of the abstract idea of automating the generation of config tables. 2. Committers approve of the abstract idea but disapprove of the implementation proposed in this PR. 3. Committers approve of the abstract idea and may approve of the implementation proposed here, but find it difficult to review. 4. Committers are constrained (due to time, energy, other priorities, etc.) and cannot participate at this time. In the case of 2, I have proposed a completely different approach in #44756 that does not touch Spark core. In the case of 3, I pushed #44755, which is a stripped down version of this PR which should be easier to review. In the case of 1, I need some feedback on why this is a bad idea so I can drop this effort. As you can see, I believe it's a good idea and am eager to push it forward. In the case of 4, please forgive me for repeatedly pinging this PR and being annoying. 😅 -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
