[
https://issues.apache.org/jira/browse/AIRFLOW-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Arnold updated AIRFLOW-1775:
---------------------------------
Comment: was deleted
(was: in airflow/models.py:
if 'mysql' in settings.SQL_ALCHEMY_CONN:
LongText = LONGTEXT
else:
LongText = Text
This is not guarded at all, you can't iterate settings.SQL_ALCHEMY_CONN if it's
empty. You get a TypeError.)
> Remote file handler for logging
> -------------------------------
>
> Key: AIRFLOW-1775
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1775
> Project: Apache Airflow
> Issue Type: Bug
> Components: logging
> Reporter: Niels Zeilemaker
> Priority: Major
>
> We're using a mounted Azure file share to store our log files. Currently,
> Airflow is writing it's logs to that fileshare. However, this is making the
> solution quite expensive, as you pay per action on Azure file shares.
> If we would have a remote_file_task_logging handler, we could mimic the
> s3_task_logging, and copy the file to the fileshare in the close method.
> Reducing the cost, while still providing persistent storage.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
