[jira] [Commented] (AIRFLOW-210) sqlalchemy warns about task_instance.execution_date invoked with an empty sequence
[
https://issues.apache.org/jira/browse/AIRFLOW-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15590289#comment-15590289
]
Jeff Long commented on AIRFLOW-210:
---
A quick fix for this in 1.7.1.3 is adding the following around models.py:2633:
{code:title=models.py:2633}
task_instances = []
if len(execution_dates) > 0:
task_instances = (
{code}
> sqlalchemy warns about task_instance.execution_date invoked with an empty
> sequence
> --
>
> Key: AIRFLOW-210
> URL: https://issues.apache.org/jira/browse/AIRFLOW-210
> Project: Apache Airflow
> Issue Type: Bug
> Components: scheduler
>Affects Versions: Airflow 1.7.0
> Environment: Linux, python 2.7, and mysql 5.5.47
>Reporter: Eric Johnson
>Assignee: Ajay Yadava
>Priority: Minor
>
> On a fresh installation of airflow, I'm noticing this warning while running
> the scheduler. I'm using mysql as the storage for airflow.
> {{/opt/packages/python/2.7.5/lib/python2.7/site-packages/sqlalchemy/sql/default_comparator.py:153:
> SAWarning: The IN-predicate on "task_instance.execution_date" was invoked
> with an empty sequence. This results in a contradiction, which nonetheless
> can be expensive to evaluate. Consider alternative strategies for improved
> performance.}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AIRFLOW-385) Scheduler logs should have a "latest" directory
[ https://issues.apache.org/jira/browse/AIRFLOW-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15589859#comment-15589859 ] Ben Tallman commented on AIRFLOW-385: - Not sure I'm worried about the latest flag, but moving to dag_id/execution_date/task_id.log would be very helpful... > Scheduler logs should have a "latest" directory > --- > > Key: AIRFLOW-385 > URL: https://issues.apache.org/jira/browse/AIRFLOW-385 > Project: Apache Airflow > Issue Type: Improvement > Components: logging >Reporter: Dan Davydov >Assignee: Vijay Bhat >Priority: Minor > Labels: beginner, logging > > Right now the scheduler logs for each parsed file look like > /tmp/airflow/scheduler/logs/2016-07-17/some-dag/... > The problem is this makes it hard to find the latest logs which is the most > frequent use case. > Ideally we would create and have the scheduler keep up to date a symlink to > the latest date /tmp/airflow/scheduler/logs/latest which would point to e.g. > /tmp/airflow/scheduler/logs/2016-07-17 > We might also want to consider changing the structure to dag/date instead of > date/dag too, but that can be done as a separate task if desired. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AIRFLOW-385) Scheduler logs should have a "latest" directory
[ https://issues.apache.org/jira/browse/AIRFLOW-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay Bhat reassigned AIRFLOW-385: -- Assignee: Vijay Bhat > Scheduler logs should have a "latest" directory > --- > > Key: AIRFLOW-385 > URL: https://issues.apache.org/jira/browse/AIRFLOW-385 > Project: Apache Airflow > Issue Type: Improvement > Components: logging >Reporter: Dan Davydov >Assignee: Vijay Bhat >Priority: Minor > Labels: beginner, logging > > Right now the scheduler logs for each parsed file look like > /tmp/airflow/scheduler/logs/2016-07-17/some-dag/... > The problem is this makes it hard to find the latest logs which is the most > frequent use case. > Ideally we would create and have the scheduler keep up to date a symlink to > the latest date /tmp/airflow/scheduler/logs/latest which would point to e.g. > /tmp/airflow/scheduler/logs/2016-07-17 > We might also want to consider changing the structure to dag/date instead of > date/dag too, but that can be done as a separate task if desired. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AIRFLOW-582) ti.get_dagrun() should not filter on start_date
Ben Tallman created AIRFLOW-582: --- Summary: ti.get_dagrun() should not filter on start_date Key: AIRFLOW-582 URL: https://issues.apache.org/jira/browse/AIRFLOW-582 Project: Apache Airflow Issue Type: Bug Reporter: Ben Tallman The filter in ti.get_dagrun should not include start_date, it should only search on execution_date. @provide_session def get_dagrun(self, session): """ Returns the DagRun for this TaskInstance :param session: :return: DagRun """ dr = session.query(DagRun).filter( DagRun.dag_id == self.dag_id, DagRun.execution_date == self.execution_date, DagRun.start_date == self.start_date ).first() return dr -- This message was sent by Atlassian JIRA (v6.3.4#6332)
