potiuk commented on PR #52002: URL: https://github.com/apache/airflow/pull/52002#issuecomment-3096296262
> @potiuk I'm not 100% happy with any current solution and documenting my helper method is not good idea IMHO. It should be decided good pattern and merged or left on side, since it will be questionable why this helper is not part of the codebase if documented. And as mentioned it introduces some requirements on extra columns, which is not standard. Quite often we do not WANT to decide. When you build product, implementing single opinionated way means that you limit your users from doing things differently. So we often revert to options, flags, variations, best practices and patterns (often several of them) that our users can choose from - and we do not want to force them. And there is a fine balance and decision making process that usually you get the hang of after several years of delivering product, rather than using the product in single way that is best for "me". This is where my reservations are coming from. And I understand you are not 100% happy. When you make product it is impossible to make eveyrone 100% happy. You strive to make 80% people 80% happy, and if you achieve that. Your product is likely to succeed (that's how I see it at least). There are many decisions we made that made some people not 100% happy, there are even some that made some people 100% unhappy, and there are even some that made some of us (committers and PMC members) very unhappy where others were somewhat happy but this was the best choice overall. BTW. Every decision you made on such low-level, and changing some basic models in Airflow will need to be very thoroughly thought through and justified. So while now you are discussing with me - whatever your "100% happiness" solution that you might propose will be -> first thing to do will be to write a '[DISCUSS]` thread on the mailing list (see "community" tab in our docs") and either achieving consenus and sending a "[LAZY CONSENSUS]" thread or - if consensus cannot be reached - starting `[VOTE]` thread and get it pass with committers and PMC members having binding vote. So - just so you know - changing the basic behaviour of connection and object storage - requires such community decision, it will not be solved in a discussion in PR. Whatever you see here as my comments are "my comments only" - and whether the rest of the community will agree with it and with your proposal, it's not given. -- 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]
