You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Victor Villas Bôas Chaves (JIRA)" <ji...@apache.org> on 2019/06/05 15:03:00 UTC
[jira] [Created] (AIRFLOW-4737) Column queue on task_instance table
limit of 50 chars is too low
Victor Villas Bôas Chaves created AIRFLOW-4737:
--------------------------------------------------
Summary: Column queue on task_instance table limit of 50 chars is too low
Key: AIRFLOW-4737
URL: https://issues.apache.org/jira/browse/AIRFLOW-4737
Project: Apache Airflow
Issue Type: Improvement
Components: models
Affects Versions: 1.10.3
Reporter: Victor Villas Bôas Chaves
Assignee: Victor Villas Bôas Chaves
I tried to use an SQS queue named "airtest-AirflowStack-FW7GGJK59W9-Tasks-BL0L2W6F5OKF" as message broker, but the Scheduler fails to work because the queue name is 51 characters long.
Why this huge queue name? SQS queue names are automatically generated by CloudFormation, and it's best practice to let it do so. Also, when using nested stacks, the inner stack also has its name automatically generated and appended to the master stack.
So in short, my master stack is called "airtest" and the queue resource "Tasks" (which I believe are quite reasonably sized), but that huge name is what you end up in the end. Therefore the use case for longer queue names is there.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)