Re: [VOTE][RESULT] Replace with Gitter with Slack?

[Sid Anand]

BTW.. big thanks to @Kaxil Naik  for deploying a
heroku app that makes automatic Slack invitations a snap :
https://apache-airflow-slack.herokuapp.com/

I'll be update the Readme.md shortly via
https://github.com/apache/incubator-airflow/pull/3878

I'll see if I can badge-ify this link!

-s

On Tue, Sep 11, 2018 at 7:36 AM Ben Gregory  wrote:

> Here you go Andrew --
>
> This link should work for the next 27 days:
>
> https://join.slack.com/t/apache-airflow/shared_invite/enQtNDMxMTU3MzM1NDg4LTVkMTg3MGU5MzhhMDQ1NDNjNjgyNTQ3MjQzNjk1YmVmZWFiYWY4NjlhNDQ5MWQyNzZlYzE3NTIyMDBiYWQxNjM
>
> On Tue, Sep 11, 2018 at 4:31 AM Andrew Harmon 
> wrote:
>
> > are there any instructions on how to join the slack workspace?
> >
> > On Mon, Sep 10, 2018 at 9:57 PM Sid Anand  wrote:
> >
> > > Thanks for the context.
> > >
> > > So, I created the slack workspace and it has ~ 100 people on it now and
> > it
> > > pretty active.
> > >
> > > What's pretty cool is that some folks created regional channels (e.g.
> > > singapore, boston, etc...), which is a good way to seed future meetups.
> > >
> > > At some point, we may want to retire the Gitter channel.
> > > -s
> > >
> > > On Sat, Sep 8, 2018 at 11:45 PM Jakob Homan  wrote:
> > >
> > > > So, binding VOTEs are generally only called on releases, where PMC
> > > > members get those binding votes (and on electing new committers or
> PMC
> > > > members, and those votes happen in private on the private list).
> > > > Communities often call VOTEs on other things, like logos, questions
> of
> > > > sponsorship, large scale tech decisions, etc.  How those VOTEs are
> > > > executed (consesus [ie anyone with a binding vote can VETO] or
> > > > majority) are up to the community to decide.
> > > >
> > > > The community can codify those decisions with bylaws (Here's
> Hadoop's:
> > > > https://hadoop.apache.org/bylaws.html).  However, extensive bylaws
> are
> > > > considered an anti-pattern - they can be indicative of a fractured or
> > > > unwieldy community.  This is why Incubator projects are not generally
> > > > recommended to go down this route.  Also, incubator podlings are not
> > > > separate top-level projects, and so would be governed by the
> Incubator
> > > > project bylaws, which as far as I can tell, don't exist.
> > > >
> > > > Also, keep in mind that the bylaws of any particular project are
> valid
> > > > at the pleasure of the Board.  If the Board deems any part of them
> > > > invalid, which it has done even very recently, it can come in and
> > > > require the project to change them immediately.
> > > >
> > > > As for the current discussion, the large number of <1 votes, is a bit
> > > > concerning.  This is indicative of lack of consensus and that further
> > > > discussion is probably warranted.  Whether or not it's an official
> > > > result is up for debate.
> > > >
> > > > However, one thing worth noting is that there's no 'official' gitter
> > > > or slack channel for any ASF project.  The only official
> communication
> > > > medium for ASF is mailing lists.  The edict 'If it didn't happen on
> > > > the mailing list, it didn't happen' is one of the axioms of the
> Apache
> > > > Way [1][2].  There's also no official IRC channel or official Stack
> > > > Overflow tag or official in-person meetup.  Every member of the
> > > > community is welcome to participate in whatever forum they want, but
> > > > the only place things actually happen is on the list.  Any non-PMC
> > > > discussions can happen anywhere, but if a decision needs to occur as
> > > > part of that discussion, the discussion needs to be re-homed onto the
> > > > mailing list and made there.  Part of the PMC's job is to enforce and
> > > > model this behavior.
> > > >
> > > > Speaking entirely for myself, I'm not comfortable with the invitation
> > > > model of Slack discussions.  For most of my time at Apache, irc was
> > > > the way to go for most projects.  Some had very active irc channels
> > > > and some were nearly dead.  (The #infra irc channel is a godsend
> > > > though.)
> > > >
> > > > And again, this type of meta discussion is awesome.  It shows the
> > > > project is maturing and thinking through some of the edge cases of
> > > > what it means to an Apache project.
> > > >
> > > > -Jakob
> > > >
> > > >
> > > >
> > > > [1]
> > > >
> > >
> >
> https://community.apache.org/newbiefaq.html#NewbieFAQ-IsthereaCodeofConductforApacheprojects
> > > > ?
> > > > [2]
> > > >
> > >
> >
> https://blogs.apache.org/foundation/entry/success-at-apache-asynchronous-decision
> > > >
> > > > On 8 September 2018 at 23:14, Sid Anand  wrote:
> > > > > Taking Binding votes into account :
> > > > >
> > > > > +1: 1 vote
> > > > >
> > > > >- Sid Anand
> > > > >
> > > > > 0: 2 votes
> > > > >
> > > > >- Bolke de Bruin
> > > > >- Kaxil Naik
> > > > >
> > > > > -0.5: 1 vote
> > > > >
> > > > >- Arthur Wiedmer
> > > > >
> > > > >
> > > > > Vote result is a net positive of +0.5.
> > > > >
> > > > > I cou

Re: Salesforce Hook/Operator

[Daniel Cohen]

I used  airflow-plugins/salesforce_plugin
 as a base for my
work.
I disregarded the hook in the repo since it didn't work and used the OOTB
hook

.
The operator (SalesforceToS3Operator
)
on the other hand is pretty useful and there is not equivalent in
apache-airflow repo.
I eventually contributed everything back
to airflow-plugins/salesforce_plugin so comments or questions are welcome.

d.



On Tue, Sep 11, 2018 at 7:53 PM Taylor Edmiston  wrote:

> The version in airflow-plugins/salesforce_plugin is borrowed from the one
> in airflow.contrib, so I would prefer the official one.
>
> If you have time to test, feel free to send us a PR that upgrades to the
> latest stable version (looks like some changes are on master but not
> v1-10-stable) from contrib, or removes the forked hook from that plugin and
> instead reference the official one.  On GitHub you can tag
> @benjamingregory @andscoop
> or me (@tedmiston) for review.
>
> *Taylor Edmiston*
> Blog  | CV
>  | LinkedIn
>  | AngelList
>  | Stack Overflow
> 
>
>
>
> On Mon, Sep 10, 2018 at 5:12 PM Jon Nalley  wrote:
>
> > Hi,
> >
> > I noticed that there is a sales force hook included in the Airflow repo:
> >
> >
> https://github.com/apache/incubator-airflow/blob/master/airflow/contrib/hooks/salesforce_hook.py
> >
> > There is also a salesforce hook and operator in the salesforce_plugin
> repo:
> > https://github.com/airflow-plugins/salesforce_plugin
> >
> > Is one preferred over the other?
> >
> > Thanks!
> >
>


-- 
daniel cohen
+972-(0)54-4799-147

Re: Cold-case PRs

[Sid Anand]

Looks cool Max.

Filed an Infra ticket:
https://issues.apache.org/jira/browse/INFRA-17005

Created a Jira to add a policy file: .github/stale.yml

https://issues.apache.org/jira/browse/AIRFLOW-3040

& raised a PR : https://github.com/apache/incubator-airflow/pull/3883

We can manage the Jira backlog separately.
-s

On Mon, Sep 10, 2018 at 8:38 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> It doesn't deal with Jiras, just PRs and GH issues (which we don't use...)
>
> Max
>
> On Mon, Sep 10, 2018 at 6:58 PM Sid Anand  wrote:
>
> > Max,
> > How do these manage the JIRAs?
> >
> > -s
> >
> > On Mon, Sep 10, 2018 at 6:14 PM Maxime Beauchemin <
> > maximebeauche...@gmail.com> wrote:
> >
> > > I've used https://github.com/bstriner/github-bot-close-inactive-issues
> > in
> > > the past to auto-close issues / PRs based on a policy around
> inactivity.
> > It
> > > worked alright.
> > >
> > > There's also https://github.com/probot/stale which seems to be one of
> > the
> > > leading solutions, but it may require an Apache INFRA ticket to make
> the
> > > integration work (if they'll allow it).
> > >
> > > Max
> > >
> > > On Mon, Sep 10, 2018 at 5:21 PM Sid Anand  wrote:
> > >
> > > > Folks!
> > > > It's around that time (over 200 PRs with some 2 years old) when we
> need
> > > to
> > > > consider closing some abandoned PRs. We have a lot more active
> > > maintainers
> > > > now today than we had 1 or 2 years ago, we are better able to keep up
> > > with
> > > > new PR demand, but it's still not perfect.
> > > >
> > > > I've created a GitHub Label : *Potential_Cold_Case_PR.*
> > > >
> > > > I've started labeling some old PRs likewise and pinging the
> submitters.
> > > > Anyone in the community can help with labeling and pinging
> submitters.
> > If
> > > > we (maintainers) find the PR abandoned (i.e. no updates from
> submitters
> > > for
> > > > a few days), we can close the PRs.
> > > >
> > > > Additionally, if the JIRAs themselves are obsolete and no longer
> apply,
> > > we
> > > > can consider closing the JIRAs as obsolete.
> > > >
> > > > Here's one example :
> > > > https://github.com/apache/incubator-airflow/pulls/vijaysbhat
> > > >
> > > > -s
> > > >
> > >
> >
>

Re: Salesforce Hook/Operator

[Taylor Edmiston]

The version in airflow-plugins/salesforce_plugin is borrowed from the one
in airflow.contrib, so I would prefer the official one.

If you have time to test, feel free to send us a PR that upgrades to the
latest stable version (looks like some changes are on master but not
v1-10-stable) from contrib, or removes the forked hook from that plugin and
instead reference the official one.  On GitHub you can tag
@benjamingregory @andscoop
or me (@tedmiston) for review.

*Taylor Edmiston*
Blog  | CV
 | LinkedIn
 | AngelList
 | Stack Overflow




On Mon, Sep 10, 2018 at 5:12 PM Jon Nalley  wrote:

> Hi,
>
> I noticed that there is a sales force hook included in the Airflow repo:
>
> https://github.com/apache/incubator-airflow/blob/master/airflow/contrib/hooks/salesforce_hook.py
>
> There is also a salesforce hook and operator in the salesforce_plugin repo:
> https://github.com/airflow-plugins/salesforce_plugin
>
> Is one preferred over the other?
>
> Thanks!
>

Re: [VOTE][RESULT] Replace with Gitter with Slack?

[Ben Gregory]

Here you go Andrew --

This link should work for the next 27 days:
https://join.slack.com/t/apache-airflow/shared_invite/enQtNDMxMTU3MzM1NDg4LTVkMTg3MGU5MzhhMDQ1NDNjNjgyNTQ3MjQzNjk1YmVmZWFiYWY4NjlhNDQ5MWQyNzZlYzE3NTIyMDBiYWQxNjM

On Tue, Sep 11, 2018 at 4:31 AM Andrew Harmon 
wrote:

> are there any instructions on how to join the slack workspace?
>
> On Mon, Sep 10, 2018 at 9:57 PM Sid Anand  wrote:
>
> > Thanks for the context.
> >
> > So, I created the slack workspace and it has ~ 100 people on it now and
> it
> > pretty active.
> >
> > What's pretty cool is that some folks created regional channels (e.g.
> > singapore, boston, etc...), which is a good way to seed future meetups.
> >
> > At some point, we may want to retire the Gitter channel.
> > -s
> >
> > On Sat, Sep 8, 2018 at 11:45 PM Jakob Homan  wrote:
> >
> > > So, binding VOTEs are generally only called on releases, where PMC
> > > members get those binding votes (and on electing new committers or PMC
> > > members, and those votes happen in private on the private list).
> > > Communities often call VOTEs on other things, like logos, questions of
> > > sponsorship, large scale tech decisions, etc.  How those VOTEs are
> > > executed (consesus [ie anyone with a binding vote can VETO] or
> > > majority) are up to the community to decide.
> > >
> > > The community can codify those decisions with bylaws (Here's Hadoop's:
> > > https://hadoop.apache.org/bylaws.html).  However, extensive bylaws are
> > > considered an anti-pattern - they can be indicative of a fractured or
> > > unwieldy community.  This is why Incubator projects are not generally
> > > recommended to go down this route.  Also, incubator podlings are not
> > > separate top-level projects, and so would be governed by the Incubator
> > > project bylaws, which as far as I can tell, don't exist.
> > >
> > > Also, keep in mind that the bylaws of any particular project are valid
> > > at the pleasure of the Board.  If the Board deems any part of them
> > > invalid, which it has done even very recently, it can come in and
> > > require the project to change them immediately.
> > >
> > > As for the current discussion, the large number of <1 votes, is a bit
> > > concerning.  This is indicative of lack of consensus and that further
> > > discussion is probably warranted.  Whether or not it's an official
> > > result is up for debate.
> > >
> > > However, one thing worth noting is that there's no 'official' gitter
> > > or slack channel for any ASF project.  The only official communication
> > > medium for ASF is mailing lists.  The edict 'If it didn't happen on
> > > the mailing list, it didn't happen' is one of the axioms of the Apache
> > > Way [1][2].  There's also no official IRC channel or official Stack
> > > Overflow tag or official in-person meetup.  Every member of the
> > > community is welcome to participate in whatever forum they want, but
> > > the only place things actually happen is on the list.  Any non-PMC
> > > discussions can happen anywhere, but if a decision needs to occur as
> > > part of that discussion, the discussion needs to be re-homed onto the
> > > mailing list and made there.  Part of the PMC's job is to enforce and
> > > model this behavior.
> > >
> > > Speaking entirely for myself, I'm not comfortable with the invitation
> > > model of Slack discussions.  For most of my time at Apache, irc was
> > > the way to go for most projects.  Some had very active irc channels
> > > and some were nearly dead.  (The #infra irc channel is a godsend
> > > though.)
> > >
> > > And again, this type of meta discussion is awesome.  It shows the
> > > project is maturing and thinking through some of the edge cases of
> > > what it means to an Apache project.
> > >
> > > -Jakob
> > >
> > >
> > >
> > > [1]
> > >
> >
> https://community.apache.org/newbiefaq.html#NewbieFAQ-IsthereaCodeofConductforApacheprojects
> > > ?
> > > [2]
> > >
> >
> https://blogs.apache.org/foundation/entry/success-at-apache-asynchronous-decision
> > >
> > > On 8 September 2018 at 23:14, Sid Anand  wrote:
> > > > Taking Binding votes into account :
> > > >
> > > > +1: 1 vote
> > > >
> > > >- Sid Anand
> > > >
> > > > 0: 2 votes
> > > >
> > > >- Bolke de Bruin
> > > >- Kaxil Naik
> > > >
> > > > -0.5: 1 vote
> > > >
> > > >- Arthur Wiedmer
> > > >
> > > >
> > > > Vote result is a net positive of +0.5.
> > > >
> > > > I counted all of the PMC/committers' votes as binding.
> > > >
> > > > -s
> > > >
> > > > On Sat, Sep 8, 2018 at 11:07 PM Arthur Wiedmer <
> > arthur.wied...@gmail.com
> > > >
> > > > wrote:
> > > >
> > > >> Sid,
> > > >>
> > > >> Erm, the next line is (emphasis mine) :
> > > >>
> > > >> PMC members have formally binding votes, but in general community
> > > members
> > > >> are encouraged to vote, even if their votes are *only advisory*.
> > > >>
> > > >> Again, that's not to say that the community at large cannot decide
> to
> > > host
> > > >> a Slack channel. I think you are mo

Re: Delay between tasks executions issue

[Chandu Kavar]

Thanks a lot.

On Tue, Sep 11, 2018, 6:25 PM ramandu...@gmail.com 
wrote:

> We use max_threads = number of scheduler cores.
>
> On 2018/09/11 09:49:53, Chandu Kavar  wrote:
> > Thanks Raman,
> >
> > Understood.
> >
> > We have around 500 DAGs. What value do you suggest for max_threads?
> >
> > On Tue, Sep 11, 2018, 5:44 PM ramandu...@gmail.com  >
> > wrote:
> >
> > > Hi Chandu,
> > > How many dag files are there on the scheduler. As per my understanding
> > > scheduler processes each file to trigger any dag/task run. It spawns
> number
> > > of processes equivalent to "max_threads" count to parallelize file
> > > processing. So you can try by increasing airflow config's max_threads
> count.
> > >
> > > Thanks,
> > > Raman Gupta
> > >
> > > On 2018/09/11 07:11:23, Chandu Kavar  wrote:
> > > > Hi All,
> > > >
> > > > We are seeing there is a delay between triggering the next task.
> Please
> > > > find the attached screenshot.
> > > >
> > > > First and the last task are very small. So, you can see the tiny
> object.
> > > >
> > > > [image: image.png]
> > > > Do you suggest any airflow config can resolve this problem?
> > > >
> > > > Thanks,
> > > > Chandu
> > > >
> > >
> >
>

Re: Delay between tasks executions issue

[ramandumcs]

We use max_threads = number of scheduler cores.

On 2018/09/11 09:49:53, Chandu Kavar  wrote: 
> Thanks Raman,
> 
> Understood.
> 
> We have around 500 DAGs. What value do you suggest for max_threads?
> 
> On Tue, Sep 11, 2018, 5:44 PM ramandu...@gmail.com 
> wrote:
> 
> > Hi Chandu,
> > How many dag files are there on the scheduler. As per my understanding
> > scheduler processes each file to trigger any dag/task run. It spawns number
> > of processes equivalent to "max_threads" count to parallelize file
> > processing. So you can try by increasing airflow config's max_threads count.
> >
> > Thanks,
> > Raman Gupta
> >
> > On 2018/09/11 07:11:23, Chandu Kavar  wrote:
> > > Hi All,
> > >
> > > We are seeing there is a delay between triggering the next task. Please
> > > find the attached screenshot.
> > >
> > > First and the last task are very small. So, you can see the tiny object.
> > >
> > > [image: image.png]
> > > Do you suggest any airflow config can resolve this problem?
> > >
> > > Thanks,
> > > Chandu
> > >
> >
> 

Re: [VOTE][RESULT] Replace with Gitter with Slack?

[Andrew Harmon]

are there any instructions on how to join the slack workspace?

On Mon, Sep 10, 2018 at 9:57 PM Sid Anand  wrote:

> Thanks for the context.
>
> So, I created the slack workspace and it has ~ 100 people on it now and it
> pretty active.
>
> What's pretty cool is that some folks created regional channels (e.g.
> singapore, boston, etc...), which is a good way to seed future meetups.
>
> At some point, we may want to retire the Gitter channel.
> -s
>
> On Sat, Sep 8, 2018 at 11:45 PM Jakob Homan  wrote:
>
> > So, binding VOTEs are generally only called on releases, where PMC
> > members get those binding votes (and on electing new committers or PMC
> > members, and those votes happen in private on the private list).
> > Communities often call VOTEs on other things, like logos, questions of
> > sponsorship, large scale tech decisions, etc.  How those VOTEs are
> > executed (consesus [ie anyone with a binding vote can VETO] or
> > majority) are up to the community to decide.
> >
> > The community can codify those decisions with bylaws (Here's Hadoop's:
> > https://hadoop.apache.org/bylaws.html).  However, extensive bylaws are
> > considered an anti-pattern - they can be indicative of a fractured or
> > unwieldy community.  This is why Incubator projects are not generally
> > recommended to go down this route.  Also, incubator podlings are not
> > separate top-level projects, and so would be governed by the Incubator
> > project bylaws, which as far as I can tell, don't exist.
> >
> > Also, keep in mind that the bylaws of any particular project are valid
> > at the pleasure of the Board.  If the Board deems any part of them
> > invalid, which it has done even very recently, it can come in and
> > require the project to change them immediately.
> >
> > As for the current discussion, the large number of <1 votes, is a bit
> > concerning.  This is indicative of lack of consensus and that further
> > discussion is probably warranted.  Whether or not it's an official
> > result is up for debate.
> >
> > However, one thing worth noting is that there's no 'official' gitter
> > or slack channel for any ASF project.  The only official communication
> > medium for ASF is mailing lists.  The edict 'If it didn't happen on
> > the mailing list, it didn't happen' is one of the axioms of the Apache
> > Way [1][2].  There's also no official IRC channel or official Stack
> > Overflow tag or official in-person meetup.  Every member of the
> > community is welcome to participate in whatever forum they want, but
> > the only place things actually happen is on the list.  Any non-PMC
> > discussions can happen anywhere, but if a decision needs to occur as
> > part of that discussion, the discussion needs to be re-homed onto the
> > mailing list and made there.  Part of the PMC's job is to enforce and
> > model this behavior.
> >
> > Speaking entirely for myself, I'm not comfortable with the invitation
> > model of Slack discussions.  For most of my time at Apache, irc was
> > the way to go for most projects.  Some had very active irc channels
> > and some were nearly dead.  (The #infra irc channel is a godsend
> > though.)
> >
> > And again, this type of meta discussion is awesome.  It shows the
> > project is maturing and thinking through some of the edge cases of
> > what it means to an Apache project.
> >
> > -Jakob
> >
> >
> >
> > [1]
> >
> https://community.apache.org/newbiefaq.html#NewbieFAQ-IsthereaCodeofConductforApacheprojects
> > ?
> > [2]
> >
> https://blogs.apache.org/foundation/entry/success-at-apache-asynchronous-decision
> >
> > On 8 September 2018 at 23:14, Sid Anand  wrote:
> > > Taking Binding votes into account :
> > >
> > > +1: 1 vote
> > >
> > >- Sid Anand
> > >
> > > 0: 2 votes
> > >
> > >- Bolke de Bruin
> > >- Kaxil Naik
> > >
> > > -0.5: 1 vote
> > >
> > >- Arthur Wiedmer
> > >
> > >
> > > Vote result is a net positive of +0.5.
> > >
> > > I counted all of the PMC/committers' votes as binding.
> > >
> > > -s
> > >
> > > On Sat, Sep 8, 2018 at 11:07 PM Arthur Wiedmer <
> arthur.wied...@gmail.com
> > >
> > > wrote:
> > >
> > >> Sid,
> > >>
> > >> Erm, the next line is (emphasis mine) :
> > >>
> > >> PMC members have formally binding votes, but in general community
> > members
> > >> are encouraged to vote, even if their votes are *only advisory*.
> > >>
> > >> Again, that's not to say that the community at large cannot decide to
> > host
> > >> a Slack channel. I think you are more than welcome to if you want to.
> > >>
> > >> Best,
> > >> Arthur
> > >>
> > >> On Sat, Sep 8, 2018 at 10:59 PM Sid Anand  wrote:
> > >>
> > >> > Why doesn't every vote matter for this topic?
> > >> > https://www.apache.org/foundation/voting.html#binding-votes
> > >> >
> > >> > Am I misinterpreting the "Who is permitted to vote is, to some
> > extent, a
> > >> > community-specific thing."?
> > >> >
> > >> > For the established Apache processes around promoting a contributor
> to
> > >> > committer/PMC, deciding on th

Re: Delay between tasks executions issue

[Chandu Kavar]

Thanks Raman,

Understood.

We have around 500 DAGs. What value do you suggest for max_threads?

On Tue, Sep 11, 2018, 5:44 PM ramandu...@gmail.com 
wrote:

> Hi Chandu,
> How many dag files are there on the scheduler. As per my understanding
> scheduler processes each file to trigger any dag/task run. It spawns number
> of processes equivalent to "max_threads" count to parallelize file
> processing. So you can try by increasing airflow config's max_threads count.
>
> Thanks,
> Raman Gupta
>
> On 2018/09/11 07:11:23, Chandu Kavar  wrote:
> > Hi All,
> >
> > We are seeing there is a delay between triggering the next task. Please
> > find the attached screenshot.
> >
> > First and the last task are very small. So, you can see the tiny object.
> >
> > [image: image.png]
> > Do you suggest any airflow config can resolve this problem?
> >
> > Thanks,
> > Chandu
> >
>

Re: Delay between tasks executions issue

[ramandumcs]

Hi Chandu,
How many dag files are there on the scheduler. As per my understanding 
scheduler processes each file to trigger any dag/task run. It spawns number of 
processes equivalent to "max_threads" count to parallelize file processing. So 
you can try by increasing airflow config's max_threads count.

Thanks,
Raman Gupta 

On 2018/09/11 07:11:23, Chandu Kavar  wrote: 
> Hi All,
> 
> We are seeing there is a delay between triggering the next task. Please
> find the attached screenshot.
> 
> First and the last task are very small. So, you can see the tiny object.
> 
> [image: image.png]
> Do you suggest any airflow config can resolve this problem?
> 
> Thanks,
> Chandu
> 

Delay between tasks executions issue

[Chandu Kavar]

Hi All,

We are seeing there is a delay between triggering the next task. Please
find the attached screenshot.

First and the last task are very small. So, you can see the tiny object.

[image: image.png]
Do you suggest any airflow config can resolve this problem?

Thanks,
Chandu