potiuk commented on pull request #10806: URL: https://github.com/apache/airflow/pull/10806#issuecomment-690612974
Question - do we actually __want__ it eventually ? I know from pure python installation "versatilty" point of view it might be a good idea, but I hardly imagine this causing a serious problem. And even if we allow to install providers from multiple folders, that potentially opens the door for more troubles. In the #10822 I currently have highly optimised (for speed) solution of discovering provider-specific code based on the fact that there is one provider's "path". It can likely be improved, but this will come with the potential penalties for speed (and I hardly imagine someone making a real production installation that would require this versatility. If we just limit it to he same "installation location", then anyone installing 2.0 will find out pretty quickly that they have to install providers in the same place where they installed airflow and it seems like pretty natural thing to do. I am not against fixing it, but seeing how many tools have problem with this, I think this might eventually bring us more problems than the (simple to detect and solve) problem we are trying to solve here. Just a thought @ashb and others. ---------------------------------------------------------------- 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]
