git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: About the project support in Airflow


My suggestion would be to deploy airflow per project. You could even use airflow to manage your ci/cd pipeline. 

B.

Sent from my iPhone

> On 24 Apr 2018, at 18:33, Maxime Beauchemin <maximebeauchemin@xxxxxxxxx> wrote:
> 
> People have been talking about namespacing DAGs in the past. I'd recommend
> using tags (many to many) instead of categories/projects (one to many).
> 
> It should be fairly easy to add this feature. One question is whether tags
> are defined as code or in the UI/db only.
> 
> Max
> 
>> On Tue, Apr 24, 2018 at 1:48 AM, Song Liu <songliu@xxxxxxxxxxx> wrote:
>> 
>> Hi,
>> 
>> Basically the DAGs are created for a project purpose, so if I have many
>> different projects, will the Airflow support the Project concept and
>> organize them separately ?
>> 
>> Is this a known requirement or any plan for this already ?
>> 
>> Thanks,
>> Song
>> 



( ! ) Warning: include(msgfooter.php): failed to open stream: No such file or directory in /var/www/git/apache-airflow-development/msg03180.html on line 98
Call Stack
#TimeMemoryFunctionLocation
10.0006363640{main}( ).../msg03180.html:0

( ! ) Warning: include(): Failed opening 'msgfooter.php' for inclusion (include_path='.:/var/www/git') in /var/www/git/apache-airflow-development/msg03180.html on line 98
Call Stack
#TimeMemoryFunctionLocation
10.0006363640{main}( ).../msg03180.html:0