Re: Airflow Meetup in NYC @ Blue Apron

2017-01-30 Thread Boris Tyukin
i hope you guys can share presentation slides at least for all of us who are not in NYC On Mon, Jan 30, 2017 at 7:33 PM, Maxime Beauchemin < maximebeauche...@gmail.com> wrote: > I'd love to watch, is there any way you guys can livecast or share a video > after the event? > > Looking forward to

Re: Airflow Meetup in NYC @ Blue Apron

2017-01-30 Thread Joseph Napolitano
Max, I'll look into it first thing tomorrow. Would be thrilled. Cheers! On Mon, Jan 30, 2017 at 7:33 PM, Maxime Beauchemin < maximebeauche...@gmail.com> wrote: > I'd love to watch, is there any way you guys can livecast or share a video > after the event? > > Looking forward to it! > > Max >

Re: Airflow 1.8.0 BETA 5

2017-01-30 Thread Dan Davydov
@Alex I'm not able to reproduce locally (assuming the two python files are in the same folder or is on your PYTHONPATH). I don't see that import error anyways. Just in case, what is your complete DAG definition? Is anyone else able to repro? On Mon, Jan 30, 2017 at 3:09 PM, Alex Van Boxel

Re: Airflow 1.8.0 BETA 5

2017-01-30 Thread Alex Van Boxel
Well this means none of my DAG's work anymore: you just can do this anymore: file bqschema.py with def marketing_segment(): return [ {"name": "user_id", "type": "integer", "mode": "nullable"}, {"name": "bucket_date", "type": "timestamp", "mode": "nullable"}, {"name":

Re: Airflow 1.8.0 BETA 5

2017-01-30 Thread Chris Riccomini
We're upgraded to b5 in dev/prod as of an hour ago. Will keep you posted. On Mon, Jan 30, 2017 at 2:45 PM, Dan Davydov wrote: > The latest commit fixed a regression since 1.7 that files with parsing > errors no longer showed up on the UI. > > On Mon, Jan 30,

Re: Airflow 1.8.0 BETA 5

2017-01-30 Thread Dan Davydov
The latest commit fixed a regression since 1.7 that files with parsing errors no longer showed up on the UI. On Mon, Jan 30, 2017 at 2:42 PM, Alex Van Boxel wrote: > Just installed beta 5 on our dev environment it lighted up as a christmas > tree. I got a a screen full of

Re: Airflow 1.8.0 BETA 5

2017-01-30 Thread Alex Van Boxel
Just installed beta 5 on our dev environment it lighted up as a christmas tree. I got a a screen full of import errors. I see that the latest commit did something with import errors... is it coorect?! On Sun, Jan 29, 2017 at 4:37 PM Bolke de Bruin wrote: > Hey Boris > > The

Re: Airflow Meetup in NYC @ Blue Apron

2017-01-30 Thread Joseph Napolitano
Hi All! We are excited to host an Airflow Meetup in NYC. We will have a guest speaker from Spotify! The Meetup is in 2 days, on Feb 1st @ 6:30pm at Blue Apron's headquarters. In Summary: Date: Feb 1st Time 6:30 - 9pm EST Location: 40 W 23rd St. New York, NY 10010

Re: Airflow + Celery + SQS

2017-01-30 Thread Jason Chen
Joseph, Thanks for sharing the ideas and I am looking forward to your announcement and results. We do use AWS ElasticCache for Celery and lean on SQS mainly due to the cost! -Jason On Mon, Jan 30, 2017 at 11:01 AM, Joseph Napolitano < joseph.napolit...@blueapron.com.invalid> wrote: >

Re: Airflow + Celery + SQS

2017-01-30 Thread Joseph Napolitano
Jason, We've considered SQS as the messaging backend for Celery, mostly due to its serverless nature. The disadvantage is that we'd depend on AWS for local development. Given this, we're leaning on Redis for messaging because we can use AWS's ElasticCache help manage it. This gives us the

Re: Airflow + Celery + SQS

2017-01-30 Thread Jeremiah Lowin
Jason, I don't believe Airflow cares about Celery's backend as long as the task API remains the same. You should be OK (though I haven't tested to confirm). J On Sat, Jan 28, 2017 at 5:09 PM Jason Chen wrote: > Hi Airflow team, > > Celery 4 supports AWS SQS >

Re: nvd3 is an external resource

2017-01-30 Thread Bolke de Bruin
Have look at https://github.com/apache/incubator-airflow/pull/2035 and see if you can test it (I havent been able to yet, so ymmv). Bolke > On 30 Jan 2017, at 13:04, Сёмочкин Максим Викторович wrote: > > I think I found a way to prevent the generation of unnecessary headers

RE: nvd3 is an external resource

2017-01-30 Thread Сёмочкин Максим Викторович
I think I found a way to prevent the generation of unnecessary headers in the html code. Maybe instead of a chart.buildhtml() will call the method buildcontent()? See my example below which shows how it is implemented now in the Airflow and how this can be implemented First, prepare a random

Re: nvd3 is an external resource

2017-01-30 Thread Bolke de Bruin
This is in python-nvd3, NVD3Chart.py. Can you please open an issue with them? It seems we can override the setting in Airflow so we can workaround it, but they should fix this. Bolke > On 30 Jan 2017, at 10:50, Сёмочкин Максим Викторович wrote: > > I checked again and it

RE: nvd3 is an external resource

2017-01-30 Thread Сёмочкин Максим Викторович
I checked again and it seems I saw the problem. In the Airflow (more precisely in the Flask) the necessary files are loaded from the directory static no problem with that. But at some point in the code the method is called chart.buildhtml(), then a representation of a chart object will become an

RE: nvd3 is an external resource

2017-01-30 Thread Сёмочкин Максим Викторович
Unfortunately, yes. Here is the output from the developer console of Chrome: GET https://cdnjs.cloudflare.com/ajax/libs/nvd3/1.7.0/nv.d3.min.css net::ERR_CONNECTION_REFUSED duration?dag_id=test_task:431 GET https://cdnjs.cloudflare.com/ajax/libs/d3/3.5.5/d3.min.js net::ERR_CONNECTION_REFUSED

nvd3 is an external resource

2017-01-30 Thread Сёмочкин Максим Викторович
Hello! Did I understand correctly that version 1.8 is a library for drawing charts (nvd3) is loaded from external resource - cloudflare? Our problem is that the Airflow is installed in a closed network segment that has no Internet access