Re: Call for fixes for Airflow 1.10.1

Thanks Kaxil! I'll get on with finishing off the 1.10.1 release next week after my talk at the London Meetup. -ash > On 15 Sep 2018, at 16:03, Kaxil Naik wrote: > > I have cherry-picked the fix for this issue on top of 1.10-test branch > along-with 16 other commits (the ones I listed earlier

Re: Call for fixes for Airflow 1.10.1

I have cherry-picked the fix for this issue on top of 1.10-test branch along-with 16 other commits (the ones I listed earlier in the mail + their dependent commits) Regards, Kaxil On Fri, Sep 14, 2018 at 6:07 AM Gerardo Curiel wrote: > Hello, > > I wonder if there is still time to wait for a

Re: Call for fixes for Airflow 1.10.1

Hello, I wonder if there is still time to wait for a fix for "BigQuery hook does not allow specifying both the partition field name and table name at the same time": https://issues.apache.org/jira/browse/AIRFLOW-2772. The BigQueryHook is taking some liberties and implementing some client-side

Re: Call for fixes for Airflow 1.10.1

Hi Ash, I've cherry-picked two commits on top of 1.10-test branch: https://github.com/apache/incubator-airflow/commit/4d2f83b19af3489d6c9563d51210a3dab2f38b26 https://github.com/apache/incubator-airflow/commit/0d2bb5cd215bd3e2d4f47033230ea03b14b36634 This was on request of Yuan of the Amazon

Re: Call for fixes for Airflow 1.10.1

I've (re)created the v1-10-test branch with some of the fixes cherry-picked in. I can't give much time this week (as what spare time I have is being used up working on my talk) but I'll work more on this towards the end of next week. I'll look at resolved Jira tickets targeted with a fix

Re: Call for fixes for Airflow 1.10.1

You can already add them to v1-10-test. Normally we are a bit cautious to this if you are not the release manager to ensure that he/she knows what the state is. B Op zo 9 sep. 2018 18:02 schreef Driesprong, Fokko : > Can we add this one as well? > >

Re: Call for fixes for Airflow 1.10.1

Can we add this one as well? https://github.com/apache/incubator-airflow/pull/3862 https://issues.apache.org/jira/browse/AIRFLOW-1917 I'm happy to cherry pick them onto the 1.10.1 by myself as well. Any idea when we will start this branch? Cheers, Fokko Op do 6 sep. 2018 om 08:08 schreef Deng

Re: Call for fixes for Airflow 1.10.1

Hi Ash, May you consider including JIRA ticket 2848 (PR 3693, Ensure dag_id in metadata "job" for LocalTaskJob) in 1.10.1 as well? https://issues.apache.org/jira/browse/AIRFLOW-2848 https://github.com/apache/incubator-airflow/pull/3693 This is a bug in terms of metadata, which also affects

Re: Call for fixes for Airflow 1.10.1

airflowuser Can you pick a more descriptive email handle? We are all Airflow users, so perhaps pick an email handle that better identifies you, especially if you report bugs or raise PRs. To do this, you simply send an email to dev-subscr...@airflow.incubator.apache.org with a handle that is

Re: Call for fixes for Airflow 1.10.1

You should push these to v1-10-test not to stable. Only once we start cutting RCs you should push to -stable. See the docs. This ensures a stable “stable”branch. Cheers Bolke. > On 3 Sep 2018, at 14:20, Ash Berlin-Taylor wrote: > > Hi everyone, > > I'm starting the process of gathering

Re: Call for fixes for Airflow 1.10.1

>From what I see on the Jira it actually very organized. At least from Bugs vs Features. I don't think tasks /sub task / tweaks / feature requests is organized... but even splitting the list into Bugs and Features (including tasks / tweaks / feature requests) is a step forward. Sent with

Re: Call for fixes for Airflow 1.10.1

That is a good idea! Though it would involve some work right now as I don't think anyone (committers or contributors) have been particularly careful of what type of Jira issue they create. Or at least not uniformly. -ash > On 5 Sep 2018, at 14:08, airflowuser > wrote: > > May I suggest for

Re: Call for fixes for Airflow 1.10.1

May I suggest for future releases to show the change log as: Bug Fixes: New Features: etc... This makes it easier to look over the list. This shouldn't be manual work.. it can be taken from the Jira ticket. Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On September

Re: Call for fixes for Airflow 1.10.1

Also please add the following fixes: - https://issues.apache.org/jira/browse/AIRFLOW-2763 (Add check to validate worker connectivity to metadata) - https://issues.apache.org/jira/browse/AIRFLOW-1874 (use_legacy_sql added to BigQueryCheck operators) -

Re: Call for fixes for Airflow 1.10.1

Ash, thanks for picking this up! Maybe add this one: https://github.com/apache/incubator-airflow/pull/3804 https://issues.apache.org/jira/browse/AIRFLOW-2866 Cheers, Fokko Op ma 3 sep. 2018 om 14:47 schreef Deng Xiaodong : > Hi Ash, > > JIRA ticket 2922

Re: Call for fixes for Airflow 1.10.1

Hi Ash, JIRA ticket 2922 was fixed together with *2921* in PR 3773 (which was already listed by you). Understand that it may be included in 1.10.1 automatically if this PR is included, but

Call for fixes for Airflow 1.10.1

Hi everyone, I'm starting the process of gathering fixes for a 1.10.1. So far the list of issues I have that we should pull in are https://issues.apache.org/jira/issues/?jql=project%20%3D%20AIRFLOW%20AND%20fixVersion%20%3D%201.10.1%20ORDER%20BY%20key%20ASC (reproduces below) I will start