[
https://issues.apache.org/jira/browse/AIRFLOW-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287063#comment-15287063
]
Chris Riccomini commented on AIRFLOW-119:
-----------------------------------------
{quote}
Actually there may be a use case where someone would like to templatify
script_location as well
{quote}
If I understand correctly, you mean if someone wanted to do:
{code}
script_location: 's3n://path/to/script_{{env}}.hql'
{code}
I buy this use case. That would mean that we'd have to leave script_location in
the {{templates}} list, which is fine, and shouldn't break you.
{quote}
Also leaving one extension (here .txt) will keep a way to use file templating
{quote}
Which param would you use this with?
{noformat}
:param query: inline query statement
:param script_location: s3 location containing query statement
:param macros: macro values which were used in query
:param tags: array of tags to be assigned with the command
:param cluster_label: cluster label on which to execute command
:param name: name to be given to command
{noformat}
We've established than any file templating on {{script_location}} won't work
because script_location is always remote (according to the docs--S3). None of
the other params look like file locations to me. If that's the case, I think
removing template_ext makes sense.
> "Template Not Found" error from QuboleOperator
> ----------------------------------------------
>
> Key: AIRFLOW-119
> URL: https://issues.apache.org/jira/browse/AIRFLOW-119
> Project: Apache Airflow
> Issue Type: Bug
> Components: operators
> Affects Versions: Airflow 1.7.0
> Reporter: Sumit Maheshwari
> Labels: qds
>
> From the given example set, when I am using qbol operator for a hive
> workload, whose script resides in s3 and ends with ".qbl", I am getting
> "Template Not Found" error.
> Also it would be nice, if airflow always tags commands going from airflow to
> qds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
