t; > [ ] -1 disapprove with the reason
>> > >
>> > >
>> > > Only votes from PMC members are binding, but members of the community
>> are
>> > > encouraged to test the release and vote with "(non-binding)".
>> > >
>> > > Please note that the version number excludes the 'rcX' string.
>> > > This will allow us to rename the artifact without modifying
>> > > the artifact checksums when we actually release.
>> > >
>> > > You can find packages as well as detailed changelog following the
>> below links:
>> > >
>> > > https://pypi.org/project/apache-airflow-providers-amazon/2.4.0rc2/
>> > >
>> > > Cheers,
>> > >
>> > > J.
>>
> --
Kyle Hamlin
bserver UI for SubDag*: Proposed UI modification to allow
> >> (un)collapse a group of tasks for a flat structure to pair with the
> first
> >> change instead of the original hierarchical structure.
> >>
> >>
> >> Please see related documents and PRs for details:
> >> AIP:
> >>
> https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-34+Rewrite+SubDagOperator
> >>
> >> Original Issue: https://github.com/apache/airflow/issues/8078
> >> Draft PR: https://github.com/apache/airflow/pull/9243
> >>
> >> Please let me know if there are any aspects that you agree/disagree
> >> with or
> >> need more clarification (especially the third change regarding
> TaskGroup).
> >> Any comments are welcome and I am looking forward to it!
> >>
> >> Cheers
> >> Bin
> >>
>
--
Kyle Hamlin
nt known problems with airflow on kube?
> >
> > 2. I notice that some jiras are still pending in the umbrella jira(
> > https://issues.apache.org/jira/browse/AIRFLOW-1314). Is it better to
> wait
> > for these tickets to be closed?
> >
> > 3. How does kube deployment compare to Celery in terms of stability,
> > performance, feature set, ease of deployment, maintenance?
> >
> > Thanks,
> > Ash
> >
>
--
Kyle Hamlin
be solved by simply parsing the YAML file.>
> >
> > *Idea:*>
> >
> > Either pass in the YAML as string or have a path to the YAML file.>
> >
>
--
Kyle Hamlin
t's all worth it, right? Right!? :)
> >
> > On Tue, Feb 26, 2019 at 3:09 AM Kevin Yang wrote:
> >
> > > My bad, I was misunderstanding a bit and mixing up two issues. I was
> > > thinking about the multiple runs for one DagRun issue( e.g. after we
> > clear
> > > the DagRun).
> > >
> > > This is an orthogonal issue. So the current implementation can work in
> > the
> > > long term plan.
> > >
> > > Cheers,
> > > Kevin Y
> > >
> > > On Tue, Feb 26, 2019 at 2:34 AM Ash Berlin-Taylor
> > wrote:
> > >
> > > >
> > > > > On 26 Feb 2019, at 09:37, Kevin Yang wrote:
> > > > >
> > > > > Now since we're already trying to have multiple graphs for one
> > > > > execution_date, maybe we should just have multiple DagRun.
> > > >
> > > > I thought that there is exactly 1 graph for a DAG run - dag_run has a
> > > > "graph_id" column
> > >
> >
>
--
Kyle Hamlin
