LOL.
Yeah, Chris and I were talking about how awesome it would be to have the
hosting (meet-up) company print off shirts that say things like "Company X
loves Apache Airflow". Also, one thing we are trying out in this upcoming
meet-up and should continue is that there are 3 speakers : 1 from the h
I'll add this to my TODO. There's a lot that I think we can updated.
On Tue, May 31, 2016 at 3:53 PM, Jakob Homan wrote:
> A lot of those tasks are specific to the Champion. Also it's part of
> the Incubator infrastucture, which generally only mentors and champion
> have access to.
>
> On 31 Ma
Hi Chris,
I see.
I switched to LocalExecutor and the scheduler is working as expected.
Thanks a lot for your help!
Jason
On Tue, May 31, 2016 at 3:35 PM, Chris Riccomini
wrote:
> Hey Jason,
>
> The SequentialExecutor only ever runs one task at a time. It's meant for
> debugging purposes. Try s
A lot of those tasks are specific to the Champion. Also it's part of
the Incubator infrastucture, which generally only mentors and champion
have access to.
On 31 May 2016 at 15:39, siddharth anand wrote:
> Any takers?
>
> -s
>
> On Tue, May 31, 2016 at 10:32 AM, Hitesh Shah wrote:
>
>> Addition
Any takers?
-s
On Tue, May 31, 2016 at 10:32 AM, Hitesh Shah wrote:
> Additionally, it would be good if someone from the community can keep
> http://incubator.apache.org/projects/airflow.html updated for important
> events such as new committers, infra setup, code migration, etc.
>
>
> — Hitesh
Hey Jason,
The SequentialExecutor only ever runs one task at a time. It's meant for
debugging purposes. Try switching to the LocalExecutor.
Cheers,
Chris
On Tue, May 31, 2016 at 3:31 PM, Jason Chen
wrote:
> Chris,
> I am running SequentialExecutor.
>
> Thanks.
> Jason
>
>
> On Tue, May 31, 20
Chris,
I am running SequentialExecutor.
Thanks.
Jason
On Tue, May 31, 2016 at 1:36 PM, Chris Riccomini
wrote:
> Hey Jason,
>
> Are you running the SerialExecutor? This is the default out-of-the-box
> executor.
>
> Cheers,
> Chris
>
> On Tue, May 31, 2016 at 12:59 PM, Jason Chen
> wrote:
>
>>
Hey Jason,
Are you running the SerialExecutor? This is the default out-of-the-box
executor.
Cheers,
Chris
On Tue, May 31, 2016 at 12:59 PM, Jason Chen
wrote:
> Hi Chris,
>
> I made the changes and tried it out.
> It seems not working as expected.
> When a dag is running (a particular task insi
Hi Chris,
I made the changes and tried it out.
It seems not working as expected.
When a dag is running (a particular task inside that dag is taking time),
another task from another dag seems "blocked".
My setting:
(1) airflow.cfg
max_active_runs_per_dag = 16
parallelism = 32
dag_concurrency
Additionally, it would be good if someone from the community can keep
http://incubator.apache.org/projects/airflow.html updated for important events
such as new committers, infra setup, code migration, etc.
— Hitesh
> On May 27, 2016, at 5:35 PM, siddharth anand wrote:
>
> Folks,
> I have
Chris,
Got it.
Thanks for your information.
I will make the change and try it out!
-Jason
On 5/31/16, 9:02 AM, "Chris Riccomini" wrote:
>Hey Jason,
>
>The problem is max_active_runs_per_dag=1. Set it back to 16. You just need
>max_active_runs=1 for the individual DAGs. This will allow multip
Dear podling,
This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.
The board meeting is scheduled for Wed, 15 June 2016, 10:30 am PDT.
The report for your podling will form a
Hey Brian,
Try going here to create the JIRA:
https://issues.apache.org/jira/secure/CreateIssue!default.jspa
Cheers,
Chris
On Tue, May 31, 2016 at 9:33 AM, Brian Candler wrote:
> Trying to follow the quickstart at
> http://pythonhosted.org/airflow/start.html (inside a fresh virtualenv,
> unde
Trying to follow the quickstart at
http://pythonhosted.org/airflow/start.html (inside a fresh virtualenv,
under ubuntu 14.04)
I get the following error:
(venv)brian@cfprov:~/airflow$ airflow initdb
[2016-05-31 17:02:25,939] {__init__.py:36} INFO - Using executor
SequentialExecutor
[2016-05-31
I agree. The date format handling in the CLI is not intuitive. IMO, it
should force full-resolution MMDDHHMMSS.micro.
On Fri, May 27, 2016 at 7:28 PM, Bence Nagy wrote:
> I can think of weird legit reasons why one would force running the dag on
> an intra-day start date, but a warning messag
Hey Jason,
The problem is max_active_runs_per_dag=1. Set it back to 16. You just need
max_active_runs=1 for the individual DAGs. This will allow multiple
(different) DAGs to run in parallel, but only one DAG of each type can run
at the same type.
Cheers,
Chris
On Fri, May 27, 2016 at 11:42 PM, J
That was the goal of getting the vectorized logo. :O)
On Tue, May 31, 2016 at 8:49 AM, Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:
> I don't have a vectorized version. If someone could vectorize it and limit
> the number of colors it'd be nice. We could even print a batch of t-shirt!
>
I don't have a vectorized version. If someone could vectorize it and limit
the number of colors it'd be nice. We could even print a batch of t-shirt!
Max
On Thu, May 26, 2016 at 3:18 PM, Chris Riccomini
wrote:
> @bolke, Thanks, that's a good start. Would prefer an SVG, though.
>
> On Thu, May 2
Mike, I think you'll need to overwrite the operator classes. Here's a
sketch to get you started, you may find more efficient ways of doing this:
```python
class MyHttpOperator(HttpOperator):
def execute(self, context):
# Code from parent class
http = HttpHook(self.method, http
Generally, sensors block ("running") until their success criteria are met.
They fail if they time out.
On Fri, May 27, 2016 at 4:51 PM Griffin Thornton
wrote:
> hello,
> I was wondering if sensors, specifically the web hdfs sensor succeed if
> there are any files in the file path or if they are
20 matches
Mail list logo
