David
https://issues.apache.org/jira/browse/AIRFLOW-558 (i.e. http
s://github.com/apache/incubator-airflow/pull/1830 ) Is on my plate.. have
already gone through many rounds of reviews, testing, and fixes with the
submitter and does not need to wait till 2.0. We should be able to merge it
soon. BTW
Kapil,
Please resubmit the email with links to the images. All embedded or
attached objects are stripped from email before Apache mail servers forward
them to recipients.
-s
On Fri, Nov 18, 2016 at 4:20 PM, Kapil Khandelwal
wrote:
> Hi,
>
> I am trying to run command pip install airflow[all] on
As we near the last month of the year and the 9th month in Apache
Incubation, I'd like to share some thoughts and gauge community feedback.
At the beginning of this year, we saw a good deal of interest in Airbnb's
Airflow project. As more companies started using it for business critical
work, it b
I didn't see a specific
> page for that meetup for slides in general.
>
> On Thu, Nov 17, 2016 at 11:39 AM, siddharth anand
> wrote:
>
> > Rob,
> > Wiki Access granted.
> > -s
> >
> > On Thu, Nov 17, 2016 at 10:49 AM, Rob Froetscher <
>
Cool! Submit a PR.. and Jakob can help test it and merge it :-) Always a
positive when there are multiple members of the community using the same
integrations.
-s
On Thu, Nov 17, 2016 at 2:31 PM, Jakob Homan wrote:
> Yes! We were just about to start writing one of our own.
>
> -Jakob
>
> On 17
t; On Thu, Nov 17, 2016 at 10:41 AM, Chris Riccomini
> wrote:
>
> > We'll be posting the video recording shortly. IT is working on it. :)
> >
> > Will post link on the meetup and mailing list.
> >
> > On Thu, Nov 17, 2016 at 10:12 AM, Siddharth Anand
>
http://blog.gitter.im/2016/11/17/join-the-dark-side/
Chris and WePayEng,
Thanks for hosting another great Airflow meet-up.
Can all of the speakers post their slides online and add links to those
talks in response to this email (and also on our Wiki)?
-s
Committers, please resolve any open Cold Case PRs that you still have on
your list below :
https://cwiki.apache.org/confluence/display/AIRFLOW/Cold-Case+PR+Resolution
In the past 6 weeks, we've cleaned up over 70 (from over 110 down to 36! We
have 16 more to go to get to our goal of ~20.
Dan, Max
Not seeing this, but I am not running master in my staging or production
envs currently.
-s
On Mon, Nov 14, 2016 at 12:38 PM, Ben Tallman wrote:
> We are seeing an issue when running Master where tasks sometimes never run.
> It seems that once they get marked as Dependencies Not met because the
s. I could then also use this functionality to add the ability to run
> from a certain point in a DAG or to a certain point in the DAG.
>
>
>
> Thanks,
> Luke Maycock
> OLIVER WYMAN
> luke.mayc...@affiliate.oliverwyman.com<mailto:luke.
> mayc...@affiliate.oliverw
Today is the 6-week deadline to close or reduce our Cold Case PR (Pull
Request) backlog.
6 weeks ago today, we had 110+ open pull requests (PRs) -- right now, we
have 47.
https://cwiki.apache.org/confluence/display/AIRFLOW/Cold-Case+PR+Resolution
Having so many open PRs is a case of broken wind
correct
On Tue, Nov 15, 2016 at 1:11 AM wrote:
Thanks siddharth for your answer. I'm going to look at the extra "failure
processing branch" as you suggested.
>It is intended that a DAGRun be deemed successful in all cases except for
> failure. So, skipped nodes F and G, would result in a Succ
https://github.com/apache/incubator-airflow/blob/master/README.md
If you haven't yet, make sure to add your company to the list of companies
using Airflow! Submit a PR to add your company to the list.
-s
Hi Gerard,
I have them both under my name on the following wiki though anyone from the
community is welcome to help with the review and test it out as well.
https://cwiki.apache.org/confluence/display/AIRFLOW/Cold-Case+PR+Resolution
About 6 weeks ago, we had over 110 open PRs, many of which were v
> PS: link to screenshot
>
> https://www.dropbox.com/s/wql05icqgnewl0d/Screenshot%202016-11-14%2006.55.43.png?dl=0
>
>
>
>
> On Mon, Nov 14, 2016 at 12:30 PM, siddharth anand
> wrote:
>
> > Found the issue.. it seems the gantt charts load from the most recent
>
FYI,
I needed to revert a commit made roughly 6 hours ago.
https://github.com/apache/incubator-airflow/commit/c6dd4d4578918364da1cd3d5655a8d41a65871b5
If you submitted any PRs in the last 6 hours and all of your travis tests
failed because of the error below, please rebase, squash commits, and
For cases like this, we (Agari) use the following approach :
1. Create a Variable in the UI of type boolean such as *enable_feature_x*
2. Use a ShortCircuitOperator (or BranchPythonOperator) to Skip
downstream processing based on the value of *enable_feature_x*
3. Assuming that you don
I don't run celery.
However, I would suggest that any solutions that you come up with be
followed up by a PR with version updates to setup.py.
On Mon, Nov 14, 2016 at 11:56 AM, Miller, Robin <
robin.mil...@affiliate.oliverwyman.com> wrote:
> Hi Nadeem,
>
>
> We are using Celery with RabbitMQ. T
Ben,
I ran into issues while maintaining my company's airflow fork and
cherry-picking my changes into the fork, especially when my changes
included db changes.
I had to play with the alembic_version in the db and do some other magic
that escapes me now. My best guidance for the future is to cherry
A couple things are at play.
The best practice is to ensure that your branch python operator does not
fail. Catch the most general exception and return a value that would pick a
"failure processing branch". If neither D nor E is your failure processing
branch, then add one more branch - BranchPyth
Current status : we have < 50 open PRs presently!
https://cwiki.apache.org/confluence/display/AIRFLOW/Cold-Case+PR+Resolution
-s
On Sat, Nov 5, 2016 at 8:06 PM, siddharth anand wrote:
> Committers,
> If you have time this week, please make a push to get your cold case
> PR clean
rt
instead defaulted to the most recent running DagRun with at least one task
complete, it would be more useful IMHO.
-s
On Sun, Nov 13, 2016 at 9:53 PM, siddharth anand wrote:
> I've installed airflow on a fresh virtualenv and I still have the issue
> above on the gantt chart. Anyone
v 12, 2016 at 9:25 PM, siddharth anand wrote:
> Gantt chart is broken for me on master.
>
> I think it's due to this merge.
> https://github.com/apache/incubator-airflow/commit/
> 868bc83137adca0ebfd5780f0dff5a7bfdfaadf9
>
> Why is an end_date needed?
>
> [i
SGTM
On Sun, Nov 13, 2016 at 12:02 PM, Bolke de Bruin wrote:
> Hi All,
>
> I count 3 positive votes, 0 negative ones. Therefore, I will finalize
> https://github.com/apache/incubator-airflow/pull/1794 which implements
> Option 1.
>
> Thanks!
> Bolke
>
> > Op 9 nov. 2016, om 22:48 heeft Arthur Wi
Gantt chart is broken for me on master.
I think it's due to this merge.
https://github.com/apache/incubator-airflow/commit/868bc83137adca0ebfd5780f0dff5a7bfdfaadf9
Why is an end_date needed?
[image: Inline image 1]
This is the tree view:
[image: Inline image 2]
Sumit, as the merger/committer,
Chris,
I have scheduled a meeting with Arthur to discuss this same topic on
Monday. Anyone who would like to join the meeting, email me and I will add
them to the meeting. It's set for 11-11:30a on Monday.
I'd like to help with this process, but I suspect we are all too new to
know what is needed.
Kevin,
Here's a link to the 1Q17 meet-up.
https://www.meetup.com/Bay-Area-Apache-Airflow-Incubating-Meetup/events/235259523/
Both upcoming meet-ups (next week at WePay and 1Q17 at Clover Health) can
be found on http://www.meetup.com/Bay-Area-Apache-Airflow-Incubating-Meetup/
-s
On Wed, Nov 9, 2
Committers,
If you have time this week, please make a push to get your cold case
PR cleanup done. The deadline is Nov 15, just in time for our WePay meetup.
I will be making an announcement there.
-s
-- Forwarded message --
From: *siddharth anand*
Date: Friday, November 4, 2016
the
maintainer group sticks to. BTW, I've seen a few contributors pitch in by
reviewing PRs. That is extremely helpful and speeds up PR review/merge
times. Please continue.
Here's the current cold-case status.
[image: Inline image 1]
-s
On Wed, Nov 2, 2016 at 12:50 PM, siddharth an
t; > maximebeauche...@gmail.com> wrote:
> >
> >> in the meantime I added a link to your docs here:
> >> https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Links
> >>
> >> On Wed, Nov 2, 2016 at 12:33 PM, siddharth anand
> >> wrote:
Laura,
Feel free to add these links to our
https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Links in the
future. For that, I need you to create a CWiki account and provide the
username so I can grant you access to it. You can then add any links you
deem useful to the community. Feel free
when this endeavor started, we were at *110*
open PRs.
[image: Inline image 1]
-s
On Wed, Nov 2, 2016 at 12:30 AM, siddharth anand wrote:
> https://cwiki.apache.org/confluence/display/AIRFLOW/
> Cold-Case+PR+Resolution
>
> [image: Inline image 1]
>
> -s
>
erard
>
> On Wed, Nov 2, 2016 at 7:43 PM, Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
> > Here:
> > https://github.com/apache/incubator-airflow/pull/1863
> >
> >
> > On Wed, Nov 2, 2016 at 10:51 AM, siddharth anand
> > wrote:
> >
Merged.
On Wed, Nov 2, 2016 at 11:43 AM, Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:
> Here:
> https://github.com/apache/incubator-airflow/pull/1863
>
>
> On Wed, Nov 2, 2016 at 10:51 AM, siddharth anand
> wrote:
>
> > Removing laurel's e
Removing laurel's email address as it appears to be wrong.
-s
On Wed, Nov 2, 2016 at 10:49 AM, siddharth anand wrote:
> +1 for that idea. We should place all links on the wiki and just have the
> project page point to the wiki!
> (https://airflow.incubator.apache.org/project.htm
+1 for that idea. We should place all links on the wiki and just have the
project page point to the wiki!
(https://airflow.incubator.apache.org/project.html).
Gerard, would you like to file a quick PR for that change and I can
approve/merge it?
-s
On Wed, Nov 2, 2016 at 10:37 AM, Gerard Toonstra
https://cwiki.apache.org/confluence/display/AIRFLOW/Cold-Case+PR+Resolution
[image: Inline image 1]
-s
A DAG Run is a run for a particular dag at a particular time. For example,
if your DAG were called FOO and if its schedule interval were @hourly, then
you would have DAG runs : Foo @ noon, Foo @ 1p, Foo @ 2p, etc...
If you need to seed a table prior to each run, just add a task at the start
of you
Yes.. we have seen the over-subscription of pools. We do need a fix for it
--- I don't believe there is one. We need someone to own and fix it.. happy
to review a PR.
We use pools at Agari for all of our needs. We are okay with mild
oversubscription, so we do see numbers slightly higher, but our p
*Today*
You would need to add 2 new tasks in a chain to the end of your current
dag, your_dag --> ShortCircuitOperator --> PythonOperator. The
ShortCircuitOperator will need to specify a trigger rule of *all_done *to
ensure it's always called. Then, specify a python callable that checks the
status
If someone has time in the community, it would be great if he/she could
take on AIRFLOW-526 in order to make our setup.py install script
predictable. Part of that work is to pin all dependencies.
@mistercrunch (Max) started the work in
https://github.com/apache/incubator-airflow/pull/1809 but the
For completeness, there is also support for a DAG run timeout, which is yet
another mechanism - I haven't used it though and I believe it was
introduced in 1.7.x.
-s
On Fri, Oct 28, 2016 at 9:42 AM, siddharth anand wrote:
> 1.6.x had an infinite retry problem. If you specified a ret
1.6.x had an infinite retry problem. If you specified a retry count greater
than 1, the tasks would get retried ad infinitum.
This was fixed in 1.7.x (1.7.1.3 is most recent release).
We use and have been using the *execution_timeout* for over a year.
build_sender_models_spark_job = BashOperator
This might be relevant as well if you want to learn more about VPC :
https://www.youtube.com/watch?v=HexrVfuIY1k
On Thu, Oct 27, 2016 at 6:39 PM, siddharth anand wrote:
> Hmn.. it looks like traffic within AWS's VPC is not encrypted.. so using
> TLS between all services is a need
, Oct 27, 2016 at 6:20 PM, siddharth anand wrote:
> I haven't looked into it but would welcome a PR if you were to propose
> one. We use SQL Alchemy for our ORM, so you may want to look at that for 1)
> above.
>
> We (Agari) run in AWS and run all our EC2-based services (e.g.
I haven't looked into it but would welcome a PR if you were to propose one.
We use SQL Alchemy for our ORM, so you may want to look at that for 1)
above.
We (Agari) run in AWS and run all our EC2-based services (e.g. Airflow
servers and the DB) within a VPC. I suspect the folks running in GCP have
way (although it's more writing operators :-).
>
> On Thu, Oct 27, 2016 at 6:22 PM siddharth anand wrote:
>
> > I believe the release manager is/was Max, though it might be Dan (@aoen).
> >
> > -s
> >
> > On Thu, Oct 27, 2016 at 9:20 AM, Chris Riccomini
&g
Oct 27, 2016 at 1:19 AM, siddharth anand
> wrote:
>
> > Max, Chris, Bolke?
> >
> > Any news on the 1.8 release?
> > -s
> >
>
Max, Chris, Bolke?
Any news on the 1.8 release?
-s
We are down to 71 open PRs from 110 a couple of weeks ago.
Chris, Bolke, Jeremiah, Dan, Max? Can we knock that number down to 30?
[image: Inline image 1]
On Wed, Oct 26, 2016 at 12:58 AM, siddharth anand wrote:
> Pretty good activity on Cold Case PR clean-up. We've clean up about 3
[image: Inline image 1]
https://github.com/apache/incubator-airflow/pull/1855
-s
> However, for the most part, SubDags are an effective way to group tasks
> into chunks of behavior that should be treated itself as a task, with
> retry, etc.
>
> On Tue, Aug 2, 2016 at 8:37 PM, siddharth anand wrote:
>
> > Hi Arthur,
> > It's not a dumb question.
week? Also, if others have time, please pitch in.
-s[image: Inline image 1]
On Mon, Oct 17, 2016 at 10:33 AM, siddharth anand wrote:
> Arthur's picked up 12 (Yaay)! Please work with him to resolve your PRs.
>
> Steven, Dan (Aoen), Chris, Bolke, Patrick? Any chance you
I got some more information from my Spotify contact - it looks like they
are in fact moving to Airflow from Luigi.
-s
On Fri, Oct 21, 2016 at 11:12 AM, siddharth anand wrote:
> This info came from the head of their ads team -- they have been using
> Airflow for a few months now and ar
vibrant and
growing.
-s
On Fri, Oct 21, 2016 at 10:46 AM, Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:
> Oh interesting. Are they replacing Luigi, or committed to using both on the
> long run?
>
> On Oct 20, 2016 7:09 PM, "siddharth anand" wrote:
>
> >
Hi Folks!
While speaking to some folks from Spotify at QCon Shanghai, I learned they
are using Airflow -- they will be submitting a PR to add Spotify to the
Airflow read_me file over the next few days.
-s
Arthur's picked up 12 (Yaay)! Please work with him to resolve your PRs.
Steven, Dan (Aoen), Chris, Bolke, Patrick? Any chance you can take on a few?
[image: Inline image 1]
On Sun, Oct 16, 2016 at 2:53 PM, siddharth anand wrote:
> I've closed around 13... less than half of whic
I will likely be delayed looking at PRs - returning on 10/26.
-s
047-656d-4e35-b344-b55a7b0d51ef>
> <http://t.sidekickopen06.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nM
> JW7t5XZs4WJfgqW4WJj7n3MP7VWW3LqXLC56dWRRf2H8CkP02?t=http%3A%
> 2F%2Fadapt.apigee.com%2F&si=5141814536306688&pi=26651047-
> 656d-4e35-b344-b55a7b0d51ef>
>
> On Wed
weight': 10,
> # 'end_date': datetime(2016, 1, 1),
> }
>
> # Change version number if schedule needs to be changed:
> dag = DAG(
> 'pipeline1_v8', default_args=default_args, schedule_interval=dag_
> schedule_interval)
>
> dag.doc_md = __doc__
&g
If you use depends_on_past=True, it won't proceed to the next DAG Run if
the previous DAG Run failed. If Day 2 fails, Day 3 won't run.
-s
On Thu, Oct 13, 2016 at 10:34 AM, siddharth anand wrote:
> Yes! It does work with Depends_on_past=True.
> -s
>
> On Thu, Oct 13, 2
Thu, Oct 13, 2016 at 1:11 PM, siddharth anand
> wrote:
>
> > Boris,
> >
> > *Question 1*
> > Only_Run_Latest is in master -
> > https://github.com/apache/incubator-airflow/commit/
> > edf033be65b575f44aa221d5d0ec9ecb6b32c67a.
> > That will solve you
itter Code review.
> >
> > On top of that, it makes it easier to tally the votes.
> >
> > Best,
> > Arthur
> >
> > On Tue, Oct 11, 2016 at 2:31 PM, siddharth anand
> > wrote:
> >
> > > Thanks for clarifying that for the community Jakob. It&#
timedelta(seconds=30),
'priority_weight': import_airflow_priority_weight}dag =
DAG(DAG_NAME, schedule_interval='@hourly', default_args=default_args,
sla_miss_callback=sla_alert_func)
I also use retries to sidestep intermittent issues. If you need to retry a
failed dag
Boris,
*Question 1*
Only_Run_Latest is in master -
https://github.com/apache/incubator-airflow/commit/edf033be65b575f44aa221d5d0ec9ecb6b32c67a.
That will solve your problem.
Releases come out one a quarter sometimes once every 2 quarters, so I would
recommend that you run off master or off your o
e already
started working on this.
Bolke, Chris, Dan (aeon), Patrick, Steven : Please update the wiki above at
your earliest convenience.
Contributors,
If you have thoughts on this process, please share them.
-s
On Tue, Oct 11, 2016 at 8:41 AM, siddharth anand wrote:
> Aoen, max?
>
>
>
;>>>
> > >> >>>> I've booked the meetup!
> > >> >>>>
> > >> >>>>
> > >> >>>>
> > >> >>>> http://www.meetup.com/Bay-Area-Apache-Airflow-
> > Incubating-Meetup/e
d City, CA
> >>>>
> >>>> See you then!
> >>>>
> >>>> Cheers,
> >>>> Chris
> >>>>
> >>>> On Fri, Oct 7, 2016 at 1:08 PM, Chris Riccomini <
> criccom...@apache.org>
> >>>>
on from the non-committer.
>
>
> On 11 October 2016 at 12:16, Laura Lorenz
> wrote:
> > I started to do this and totally got myself stuck answering bug reports
> 😅🙃
> >
> > On Mon, Oct 10, 2016 at 11:33 PM, siddharth anand
> wrote:
> >
> >&
Aoen, max?
On Monday, October 10, 2016, siddharth anand wrote:
> Great! Yep, Nov 15th.
>
> Thx Arthur and best of luck on your imminent deadline.
>
> -s
>
> On Mon, Oct 10, 2016 at 10:26 AM, Arthur Wiedmer > wrote:
>
>> The deadline is November 15th, no
Great idea, Max.
There is also a vote feature on JIRAs. Sometimes PRs get abandoned, whereas
the JIRA tends to stick around longer, sometimes even without an owner. I'm
not sure which is the best way, but I completely agree with the sentiment.
-s
On Mon, Oct 10, 2016 at 6:01 PM, Maxime Beauchemi
It's in master. It hasn't been picked up in a release yet.
-s
On Mon, Oct 10, 2016 at 3:49 PM, Colin Son wrote:
> Hello,
>
> Do you happen to know in what version of Airflow that "task_fail" table was
> introduced?
>
> Thanks
>
> On Mon, Oct 1
ask Instances, will also
> only display successful attempts, when the task succeeds on subsequent
> retries?
>
> Thanks
>
> On Mon, Oct 10, 2016 at 1:06 PM, siddharth anand
> wrote:
>
> > Colin,
> >
> > Have a look at the link below:
> > https://www.ag
There is a current limitation that Airflow only runs on GMT/UTC. I believe
you are asking for a purely cosmetic change to allow the UI to convert date
times displayed to any TZ. I can't speak to that ability and I expect it's
easy if we assume that we are always converting from GMT/UTC to a
display
Colin,
Have a look at the link below:
https://www.agari.com/a-summer-interns-journey-into-airflow-agari/
We committed some changes to master over the Summer that provide a few new
UI controls:
* A new Task Tries view that plots Task Tries as a function of time for
each task in a DAG
* A Cumulativ
ke some time for Airflow afterwards. Just so Sid is reassured
> ;p
>
>
> Best,
> Arthur
>
> On Sat, Oct 8, 2016 at 9:59 AM, siddharth anand wrote:
> > Excellent.. thanks for committing to that. Are any of the Airbnb folks
> > (Arthur, Dan, Max, Patrick) able to help o
Folks!
What are our remaining requirements to graduate from the incubator? My
understanding is that we need to start doing Apache releases. If that is
the case, can we prioritize this and have someone lead it?
I know Max/Bolke were working on a 1.7.3 apache release, so we could follow
up with a 1.
Excellent.. thanks for committing to that. Are any of the Airbnb folks
(Arthur, Dan, Max, Patrick) able to help out?
-s
On Sat, Oct 8, 2016 at 2:25 AM, Sumit Maheshwari wrote:
> Hi Sid,
>
> I've also picked up my share.
>
>
> Thanks,
> Sumit
>
> On Fri, Oct 7,
6:36 PM Chris Riccomini
> > wrote:
> >
> >> I think WePay can do November 16. Alex, can you make it then?
> >>
> >> On Thu, Oct 6, 2016 at 8:38 PM, siddharth anand
> wrote:
> >> > I think a sane process for deciding meet-ups is to go in order off
l a few things down but my tentative plan was for December
> 7th.
>
> If enough people prefer November 16th, Clover Health could do the 17Q1
> meetup instead of 16Q4.
>
> --George
>
> On Sat, Oct 1, 2016 at 12:37 AM siddharth anand wrote:
>
> > +1
> >
> &
p 10 CCPRs & add them
to the list.
-s
On Tue, Oct 4, 2016 at 1:05 PM, siddharth anand wrote:
> I've added my 10 to https://cwiki.apache.org/co
> nfluence/display/AIRFLOW/Whittling+down+PR+List
>
> Li Xuanji, Sumit, Dan, Arthur, Max, Bolke, Chris, Jeremiah et al please
>
bmit a PR documentation / PR template?
>
> On Sat, Oct 1, 2016 at 1:31 AM siddharth anand wrote:
>
> > For all PRs with UI changes, it is a requirement that screenshots be
> > included in the PR. Please help reinforce this practice.
> >
> >
> > -s
> >
>
Thu, Oct 6, 2016 at 7:03 AM, siddharth anand wrote:
> There's a 50-50 chance I will be attending - today's a very busy day with
> double-bookings. Gurer, can you record the video stream?
>
> -s
>
> On Fri, Sep 30, 2016 at 10:20 PM, George Leslie-Waksman <
> geo...@c
There's a 50-50 chance I will be attending - today's a very busy day with
double-bookings. Gurer, can you record the video stream?
-s
On Fri, Sep 30, 2016 at 10:20 PM, George Leslie-Waksman <
geo...@cloverhealth.com> wrote:
> Great, I'll be there.
>
> --George Leslie-Waksman (Clover Health)
>
>
If you've been seeing slowness on the scheduler on master, please git pull
the latest change : https://github.com/apache/incubator-airflow/pull/1823
This may not solve all of your problems, but it will improve matters. Notes
from the commit :
"A recent commit has changed the scheduler behavior th
That sounds possible. Can you set min_file_process_interval = 0? My airflow
config looks as shown below.
[scheduler]
# Task instances listen for external kill signal (when you clear tasks
# from the CLI or the UI), this defines the frequency at which they should
# listen (in seconds).
job_hear
Fellow Airflowers,
Apache Airflow is now required to provide podling status updates every 3
months.
https://wiki.apache.org/incubator/October2016
Please review the status available at the link above and provide any
feedback that you think should be included in the report. The report is due
(EOD PS
I've added my 10 to https://cwiki.apache.org/confluence/display/AIRFLOW/
Whittling+down+PR+List
Li Xuanji, Sumit, Dan, Arthur, Max, Bolke, Chris, Jeremiah et al please
add yours to the list.
On Sun, Oct 2, 2016 at 9:57 AM, siddharth anand wrote:
> Hi Folks,
> We have in excess of
I have content ready to add to the Oct podling report. In the 3 months
since I last did this, I forgot how to edit this page.
-s
-- Forwarded message --
From:
Date: Mon, Oct 3, 2016 at 7:47 PM
Subject: Podling Report Reminder - October 2016
To: dev@airflow.incubator.apache.org
Hi Folks,
We have in excess of a 100 open PRs. We have 11 committers. Though having a
lot of open PRs is a sign of a healthy project, the majority of our PRs are
over 3 months old - that's really not a healthy sign.
This is a call to committers to help whittle down this list. I'd like each
committ
For all PRs with UI changes, it is a requirement that screenshots be
included in the PR. Please help reinforce this practice.
-s
... sent too soon...
but, more info is needed to reproduce on our side. What version of Postgres
are you running and what is your env (e.g. cloud), etc...?
On Sat, Oct 1, 2016 at 1:03 AM, siddharth anand wrote:
> Hi Renaud,
> I've never encountered this issue though I do r
Hi Renaud,
I've never encountered this issue though I do run postgres & LocalExecutor
and am running 1.7.1.3 in all of my environments.
I'm running on master on my local dev machine. I changed the valid
sql_alchemy_conn
= postgresql://siddharth@localhost:5432/airflow to the invalid
sql_alchemy_con
Hila,
I commented just now.
-s
On Sun, Sep 25, 2016 at 10:11 PM, הילה ויזן wrote:
> Hi guys,
> I posted this issue 2 weeks ago.
> ExternalTaskSensor fails in each dag run - query to airflow DB fails.
>
> maybe one of you can help?
>
> https://issues.apache.org/jira/browse/AIRFLOW-503
>
(I'll volunteer for
> a talk then).
>
> Would be great. Thanks.
>
> On Sat, Oct 1, 2016 at 8:51 AM siddharth anand wrote:
>
> > SGTM.
> >
> > -s
> >
> > On Fri, Sep 30, 2016 at 10:18 PM, George Leslie-Waksman <
> > geo...@cloverhealth.com&
avoid
> Thanksgiving and the December holidays, and because it will be after we're
> through this year's annual enrollment period.
>
> --George Leslie-Waksman (Clover Health)
>
> On Fri, Sep 30, 2016 at 6:25 PM siddharth anand wrote:
>
> > Thanks again Gurer.
s things further, if you need more details.
> Certainly we could work around, and certainly there are things we don't
> like about the current system, but we only have so many places that we can
> devote resources at any given point in time.
>
> --George Leslie-Waksman (Clover Health
I'm trying to understand the impetus for a feature - the ability to define
connections using OS environment vars.
https://airflow.incubator.apache.org/concepts.html#connections
It seems folks use this so that they can set up Airflow connections using
automation (e.g. Ansible, chef, puppet. etc...
101 - 200 of 345 matches
Mail list logo
