I too agree with what you are saying, Jarek.
I do not think there is any direct dependency here from what I know so far.
Looking forward to when someone adds Valkey support.
Thanks & Regards,
Amogh Desai
On Thu, Apr 11, 2024 at 10:06 PM Vikram Koka
wrote:
> Agree with your assessment Jarek,
This has been resolved now
If you are still facing trouble, do the following (as advised by Slack
Support).
Please try reloading Slack (*Command + Shift + R* on Mac or *Ctrl + Shift +
R* on Windows/Linux)
On Thu, 11 Apr 2024 at 17:21, Amogh Desai wrote:
> Thanks for your email, Kaxil.
>
> I
databricks and yandex providers are excluded from rc1.
Please continue testing/voting without considering these two providers.
On Thu, Apr 11, 2024 at 3:25 PM Pankaj Koti
wrote:
> +1 (non-binding)
>
> Verified my changes and our provider's example DAGs are running fine
> on the RCs.
>
> Best
Agree with your assessment Jarek, and that we don't have to do anything
here.
On Thu, Apr 11, 2024 at 5:29 AM Jarek Potiuk wrote:
> Hello here,
>
> I've raised the discussion on private@ and it seems that there are no
> private/controversies there, so I bring the discussion to devlist where it
There are some drawbacks I saw here, it would force to upgrade other
providers to the latest version.
Some scenarios from the my head:
End users use amazon provider and google provider, and do not use
common.sql and both of them have mandatory common.sql as dependency.
if everything works fine
Thanks for your email, Kaxil.
I have been facing similar issues as well.
Thanks & Regards,
Amogh Desai
On Thu, 11 Apr 2024 at 9:45 PM, Kaxil Naik wrote:
> Hi all,
>
> I wanted to let you all know that I am facing & aware that others like me
> are facing issues with Airflow's Slack workspace.
Hi all,
I wanted to let you all know that I am facing & aware that others like me
are facing issues with Airflow's Slack workspace. Things like: you don't
see member's name, messages aren't visible or don't load etc.
I have raised a support ticket with Slack, sent them logs and they are
working
Hello here,
I've raised the discussion on private@ and it seems that there are no
private/controversies there, so I bring the discussion to devlist where it
belongs.
You might want to be aware that Redis announced licensing changes that make
future Redis 7.4+ releases not good for "mandatory"
+1 (non-binding)
Verified my changes and our provider's example DAGs are running fine
on the RCs.
Best regards,
*Pankaj Koti*
Senior Software Engineer (Airflow OSS Engineering team)
Location: Pune, Maharashtra, India
Timezone: Indian Standard Time (IST)
On Thu, Apr 11, 2024 at 3:01 PM Jarek
+1 (binding). Checked all my changes, including the celery provider bug
that prevented 3.6.1 from running on Airflow 2.7.* (celery 3.6.2rc1 now
works just fine for Airflow 2.7). Checked reproducibility, licences,
signatures, checksums. All good.
On Wed, Apr 10, 2024 at 8:11 PM Vincent Beck
Hello here,
I have a proposal to add a general policy that all our providers depending
on common.sql provider always use >= LATEST_MNOR version of the provider.
For example, following the change here
https://github.com/apache/airflow/pull/38707 by David we will update all
sql providers to have:
Any other ideas or suggestions here? Can someone explain how the
"polypill" approach would look like, maybe? How do we imagine this working?
Just to continue this discussion - another example.
Small thing that David wanted to add for changes in some sql providers:
@contextmanager
def
12 matches
Mail list logo
