airflow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arthur Wiedmer <arthur.wied...@gmail.com>
Subject Re: DAG logging
Date Tue, 31 Oct 2017 18:02:05 GMT
Hey Chris,

Most operators now have a self.log which should be available if you derive
from the BaseOperator

self.log.info('foo')

should work.

But that's indeed a minor breaking change for custom operators. We might
need to warn users.

Best,
Arthur

On Tue, Oct 31, 2017 at 10:54 AM, Chris Riccomini <criccomini@apache.org>
wrote:

> Correction:
>
> import logging
>
> class DqRowCheckOperator(BaseOperator):
>   ...
>   def execute(...):
>     logging.info('foo')
>   ...
>
> It's an operator that we're using. The 'foo' doesn't show up in the logs in
> the UI or file.
>
> On Tue, Oct 31, 2017 at 10:47 AM, Chris Riccomini <criccomini@apache.org>
> wrote:
>
> > Hey all,
> >
> > Just noticed when we upgraded to 1.9.0 that logging from our custom
> > operators are no longer visible in the file. Assuming this is due to all
> > the log changes that were made in 1.9.0.
> >
> > Our custom operators just have:
> >
> > import logging
> >
> > class DbDagBuilder(object):
> >   ...
> >   logging.info('foo')
> >   ...
> >
> > This was working fine in 1.8.2. What is the suggested way to make this
> > work?
> >
> > Cheers,
> > Chris
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message