ashb commented on PR #73301: URL: https://github.com/apache/airflow/pull/73301#issuecomment-5757640832
@o-nikolas A discussion thread is just that, a discussion, and not a detailed design discussion. Doubly so as in that discuss list you said nothing about "AwsDuckDBOperator". The main thing I don't like about this is, as a user, why do I need to go "okay, I've developed this against local files and it works, now I need to swap it to a different operator to deploy to prod." It really feels like it should be "I just change the connection". Why can't it work this way? It's a much nicer user experience. > Many many services can connect with DuckDB, we cannot have the vendor neutral Hook support all of them I never said the _hook code_ has to live in the DuckDB provider, this is all about the user experience - i.e. operators.. Having an dedicated operator for DuckDB on S3 is an anti-pattern that sets a bad precedent. -- 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]
