You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2020/10/27 08:44:47 UTC
[GitHub] [airflow] potiuk opened a new issue #11879: Describe how pip and versioning interacts with the provider versions.
potiuk opened a new issue #11879:
URL: https://github.com/apache/airflow/issues/11879
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] vikramkoka commented on issue #11879: Describe how pip and versioning interacts with the provider versions.
Posted by GitBox <gi...@apache.org>.
vikramkoka commented on issue #11879:
URL: https://github.com/apache/airflow/issues/11879#issuecomment-722684511
@potiuk
Here are the questions that I have seen come up and please let me know if I should be adding these to a document some place instead of here.
Q. When upgrading to a new Airflow version such as 2.0, but possibly 2.0.1 and beyond, is the best practice to also upgrade provider packages at the same time?
Q. I have an Airflow version (1.10.12) running and it is stable. However, because of a Cloud provider change, I would like to upgrade the provider package. If I don't need to upgrade the Airflow version anymore, how do I know that this provider version is compatible with my Airflow version?
Q. I have an older version of my provider package which we have lightly customized and is working fine with my MSSQL installation. I am upgrading my Airflow version. Do I need to upgrade my provider, or can I keep it as it is.
I hope this helps, will be happy to clarify and add more as I encounter them.
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk closed issue #11879: Describe how pip and versioning interacts with the provider versions.
Posted by GitBox <gi...@apache.org>.
potiuk closed issue #11879:
URL: https://github.com/apache/airflow/issues/11879
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #11879: Describe how pip and versioning interacts with the provider versions.
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #11879:
URL: https://github.com/apache/airflow/issues/11879#issuecomment-722686406
Cool! Superb questions :) really helpful!
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] petedejoy commented on issue #11879: Describe how pip and versioning interacts with the provider versions.
Posted by GitBox <gi...@apache.org>.
petedejoy commented on issue #11879:
URL: https://github.com/apache/airflow/issues/11879#issuecomment-723742005
One thing I'd add is the inverse of the second question that @vikramkoka posed above- if I'd like to upgrade Airflow, how can I validate that the provider I'm installing will not break? What does that experience look like both from the user perspective and from the builder/maintainer perspective?
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] petedejoy edited a comment on issue #11879: Describe how pip and versioning interacts with the provider versions.
Posted by GitBox <gi...@apache.org>.
petedejoy edited a comment on issue #11879:
URL: https://github.com/apache/airflow/issues/11879#issuecomment-723742005
One thing I'd add is the inverse of the second question that @vikramkoka posed above- if I'd like to upgrade Airflow, how can I validate that the provider I'm installing and using in my DAG will not break? What does that experience look like both from the user perspective and from the builder/maintainer perspective?
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk closed issue #11879: Describe how pip and versioning interacts with the provider versions.
Posted by GitBox <gi...@apache.org>.
potiuk closed issue #11879:
URL: https://github.com/apache/airflow/issues/11879
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk edited a comment on issue #11879: Describe how pip and versioning interacts with the provider versions.
Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on issue #11879:
URL: https://github.com/apache/airflow/issues/11879#issuecomment-717085276
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #11879: Describe how pip and versioning interacts with the provider versions.
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #11879:
URL: https://github.com/apache/airflow/issues/11879#issuecomment-724097929
Hello everyone,
I prepared the first version of the documentation update including Provider
Packages and it's dependencies. It addresses (I hope) the questions pointed
out by Vikram and Pete,
I invite everyone interested in the discussion in the PR:
https://github.com/apache/airflow/pull/12203
Suggestions on re-wording are most appreciated, I am not a native speaker,
so grammar, wording etc. are equally welcome as a concrete proposal on what
to include, what questions/answers to provide, also I look forward to
phrase it in a way that will be nice and helpful, and at the same time, it
will leave enough freedom and enough information for the customers using
Airflow to make their own decisions on how they are testing and validating
any upgrades/downgrades.
I think we should stress (and this is what I tried to show in the PR) that
Provider Packages provide the nice feature that each business /user can
incrementally update those providers as they wish, where we as community
aim to provide backwards compatibility based on the SemVer versioning
principles. We are not able to tell our users how they are going to
upgrade, but we can tell them what freedom they have.
If you think that - as a community - we should approach it differently -
happy to discuss it in the PR and any proposals there are welcome.
J.
On Mon, Nov 9, 2020 at 11:34 AM Jarek Potiuk <Ja...@polidea.com>
wrote:
> Cool. I will try to prepare small "starting point" description PR that
> might be a good starting point that we will iterate over during betas.
>
> On Mon, Nov 9, 2020 at 5:08 AM Pete DeJoy <no...@github.com>
> wrote:
>
>> One thing I'd add is the inverse of the second question that @vikramkoka
>> <https://github.com/vikramkoka> posed above- if I'd like to upgrade
>> Airflow, how can I validate that the provider I'm installing will not
>> break? What does that experience look like both from the user perspective
>> and from the builder/maintainer perspective?
>>
>> —
>> You are receiving this because you were mentioned.
>> Reply to this email directly, view it on GitHub
>> <https://github.com/apache/airflow/issues/11879#issuecomment-723742005>,
>> or unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/AAERMI23GJAXZLDG6NVYUJTSO5TMJANCNFSM4TAP2IUA>
>> .
>>
>
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> [image: Polidea] <https://www.polidea.com/>
>
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #11879: Describe how pip and versioning interacts with the provider versions.
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #11879:
URL: https://github.com/apache/airflow/issues/11879#issuecomment-723925694
Cool. I will try to prepare small "starting point" description PR that
might be a good starting point that we will iterate over during betas.
On Mon, Nov 9, 2020 at 5:08 AM Pete DeJoy <no...@github.com> wrote:
> One thing I'd add is the inverse of the second question that @vikramkoka
> <https://github.com/vikramkoka> posed above- if I'd like to upgrade
> Airflow, how can I validate that the provider I'm installing will not
> break? What does that experience look like both from the user perspective
> and from the builder/maintainer perspective?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/airflow/issues/11879#issuecomment-723742005>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAERMI23GJAXZLDG6NVYUJTSO5TMJANCNFSM4TAP2IUA>
> .
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #11879: Describe how pip and versioning interacts with the provider versions.
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #11879:
URL: https://github.com/apache/airflow/issues/11879#issuecomment-717085276
cc: @vikramkoka since you have the customers that you talked to - if there are any
----------------------------------------------------------------
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:
users@infra.apache.org