[jira] [Updated] (AIRFLOW-3447) Intended usage of ts_nodash macro broken with migration to new time system.
[
https://issues.apache.org/jira/browse/AIRFLOW-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kaxil Naik updated AIRFLOW-3447:
Fix Version/s: 1.10.2
> Intended usage of ts_nodash macro broken with migration to new time system.
> ---
>
> Key: AIRFLOW-3447
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3447
> Project: Apache Airflow
> Issue Type: Bug
> Components: core
>Reporter: Luka Draksler
>Priority: Minor
> Labels: easyfix
> Fix For: 1.10.2
>
>
> Migration to timezone aware times broke the intended usage of ts_nodash macro.
> ts_nodash is used in certain placeholders to create different names (table
> names, cluster names...). As such it is alphanumeric only, it contains no
> characters that could be deemed illegal by various naming restrictions.
> Migration to new time system changed that.
> As an example, this would be returned currently:
> {{20181205T125657.169324+}}
> {{before:}}
> {{20181204T03}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AIRFLOW-3447) Intended usage of ts_nodash macro broken with migration to new time system.
[
https://issues.apache.org/jira/browse/AIRFLOW-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luka Draksler updated AIRFLOW-3447:
---
Description:
Migration to timezone aware times broke the intended usage of ts_nodash macro.
ts_nodash is used in certain placeholders to create different names (table
names, cluster names...). As such it is alphanumeric only, it contains no
characters that could be deemed illegal by various naming restrictions.
Migration to new time system changed that.
As an example, this would be returned currently:
{{20181205T125657.169324+}}
{{before:}}
{{20181204T03}}
was:
Migration to timezone aware times broke the intended usage of ts_nodash macro.
ts_nodash is used in certain placeholders to create different names (table
names, cluster names...). As such it is alphanumeric only, it contains no
characters that could be deemed illegal by various naming restrictions.
Migration to new time system changed that.
As an example, this would be returned currently:
{{20181205T125657.169324+}}
{{before:}}
{{20181204T03}}{{}}
> Intended usage of ts_nodash macro broken with migration to new time system.
> ---
>
> Key: AIRFLOW-3447
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3447
> Project: Apache Airflow
> Issue Type: Bug
> Components: core
>Reporter: Luka Draksler
>Priority: Minor
> Labels: easyfix
>
> Migration to timezone aware times broke the intended usage of ts_nodash macro.
> ts_nodash is used in certain placeholders to create different names (table
> names, cluster names...). As such it is alphanumeric only, it contains no
> characters that could be deemed illegal by various naming restrictions.
> Migration to new time system changed that.
> As an example, this would be returned currently:
> {{20181205T125657.169324+}}
> {{before:}}
> {{20181204T03}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AIRFLOW-3447) Intended usage of ts_nodash macro broken with migration to new time system.
[
https://issues.apache.org/jira/browse/AIRFLOW-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luka Draksler updated AIRFLOW-3447:
---
Summary: Intended usage of ts_nodash macro broken with migration to new
time system. (was: Migration to timezone aware times broke the intended usage
of ts_nodash macro.)
> Intended usage of ts_nodash macro broken with migration to new time system.
> ---
>
> Key: AIRFLOW-3447
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3447
> Project: Apache Airflow
> Issue Type: Bug
> Components: core
>Reporter: Luka Draksler
>Priority: Minor
> Labels: easyfix
>
> Migration to timezone aware times broke the intended usage of ts_nodash macro.
> ts_nodash is used in certain placeholders to create different names (table
> names, cluster names...). As such it is alphanumeric only, it contains no
> characters that could be deemed illegal by various naming restrictions.
> Migration to new time system changed that.
> As an example, this would be returned currently:
> {{20181205T125657.169324+}}
> {{before:}}
> {{20181204T03}}{{}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
