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
Hi Xiaodong,
Thanks for preparing the questions.
Setting-Up: In container (previously Swarm and now K8S)
Executor: CeleryExecutor
Scale: two airflow workers
Queue: No
SLA: We don't have a hard limit but it would be unbearable for a DAG to be
scheduled in more than one minute.
Airflow has been
I'll play!
Setting up: containerized (kubernetes/helm on GCP)
Executors: CeleryExecutor
Scale: 1 worker node
Queues: not using, we use pools very lightly to restrict some long running
tasks but mostly get away without it
Scheduler SLA: no
# of DAGs/Tasks: more on the scale of 10-15 DAGs with 3-20
Hi,
Setting up Airflow for the first time is a BIG DEAL.
unlike the initial intention of the community of easy install with SQLite and
SequentialExecutor - for actually working environment you need to change a lot
of settings. It doesn't help much that the demo install went smoothly.
The
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
I have no comment on your comments.
Just to make my questions clearer: SLA here means the internal service
agreement on how quickly a DAG should be processed by the scheduler or a
task be scheduled, in order to assess the performance. I'm not talking
about the SLA email notification feature in
>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
Many thanks for sharing, Manu!
I realise I have missed an important question: how many DAGs/tasks are your
Airflow instance dealing with.
I would like to share the current status in my organisation as well:
*- Setting-up*: we're using both "one-time" and container setting-up ways,
in different
Hi Folks!
In the Apache tradition, I'd like to ask the community to vote on replacing
Gitter with Slack.
For more information about what was recently discussed, refer to
https://lists.apache.org/thread.html/8eeb6c46ec431b9158f87022ceaa5eed8dbaaf082c887dae55f86f96@%3Cdev.airflow.apache.org%3E
If
+1
Sent from my iPhone
> On 6 Sep 2018, at 12:45 pm, Sid Anand wrote:
>
> +1
>
> On Wed, Sep 5, 2018 at 7:38 PM Steve Carpenter
> wrote:
>
>> +1
>>
>>> On Wed, Sep 5, 2018 at 8:30 PM Sid Anand wrote:
>>>
>>> Hi Folks!
>>> In the Apache tradition, I'd like to ask the community to vote on
+1
On Wed, Sep 5, 2018 at 7:38 PM Steve Carpenter
wrote:
> +1
>
> On Wed, Sep 5, 2018 at 8:30 PM Sid Anand wrote:
>
> > Hi Folks!
> > In the Apache tradition, I'd like to ask the community to vote on
> replacing
> > Gitter with Slack.
> >
> > For more information about what was recently
+1
On Wed, Sep 5, 2018 at 7:46 PM, Beau Barker
wrote:
> +1
>
> Sent from my iPhone
>
> > On 6 Sep 2018, at 12:45 pm, Sid Anand wrote:
> >
> > +1
> >
> > On Wed, Sep 5, 2018 at 7:38 PM Steve Carpenter <
> steve.carpen...@ibotta.com>
> > wrote:
> >
> >> +1
> >>
> >>> On Wed, Sep 5, 2018 at 8:30
+1
On Wed, Sep 5, 2018 at 9:30 PM Sid Anand wrote:
> Hi Folks!
> In the Apache tradition, I'd like to ask the community to vote on replacing
> Gitter with Slack.
>
> For more information about what was recently discussed, refer to
>
>
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
Hi Sid,
Definitely, there are a few things about this flow that could be better
documented. I'm planning to address a few things like this as part of
https://issues.apache.org/jira/browse/AIRFLOW-87. Do you have any specifics
about what you would like to be documented about this flow?
The build
Any chance you can document a flow that ties the CI build artifacts to this
repo and how we would use them? Would our build times go down?
-s
On Sun, Aug 19, 2018 at 11:43 AM Driesprong, Fokko
wrote:
> Hi all,
>
> Gerardo is doing some awesome work on Dockerizing the CI pipeline. The PR
> is
Hi Folks!
@verdan did some work to modularlize / modernize the UI for the rbac_ui in
https://github.com/apache/incubator-airflow/pull/3572
In another commit (https://github.com/apache/incubator-airflow/pull/3641),
@verdan added eslint support to the rbac_ui
*Question 1*
What's keeping us from
-1
On Thu, 6 Sep 2018, 06:16 Arthur Wiedmer, wrote:
> -0.5 (binding)
>
> I should probably have spoken during the discuss, but I was hoping that we
> would just settle on the mailing list.
>
> I am not sure what we gain by having an "official" Slack channel. Without a
> sustained financial
+1
On Sep 5, 2018, 7:30 PM -0700, Sid Anand , wrote:
> Hi Folks!
> In the Apache tradition, I'd like to ask the community to vote on replacing
> Gitter with Slack.
>
> For more information about what was recently discussed, refer to
>
Hi,
This PR has to rebase onto master first to get rid of the conflicts.
Cheers, Fokko
Op wo 5 sep. 2018 om 09:20 schreef airflowuser
:
> Can someone assist with rerun build for:
> https://github.com/apache/incubator-airflow/pull/2488
>
> tried to send it to committers mailing list but for
Hi folks,
May you kindly share how your organization is setting up Airflow and using
it? Especially in terms of architecture. For example,
- *Setting-Up*: Do you install Airflow in a "one-time" fashion, or
containerization fashion?
- *Executor:* Which executor are you using (*LocalExecutor*,
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
22 matches
Mail list logo
