[
https://issues.apache.org/jira/browse/LIVY-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanskar Modi updated LIVY-988:
------------------------------
Description:
Currently, livy does not escape backticks from user-provided spark-submit
arguments. So if a customer is passing any arguments that contain backticks, it
will be considered as command substitution during spark-submit causing that
argument to become blank or invalid.
Example:
{code:java}
--query 'select * from test_db.`test_table`' {code}
will become
{code:java}
--query 'select * from test_db.' {code}
Github Issue: [https://github.com/apache/incubator-livy/issues/415]
was:
Currently, livy does not escape backticks from user-provided spark-submit
arguments. So if a customer is passing any arguments that contain backticks, it
will be considered as command substitution during spark-submit causing that
argument to become blank or invalid.
Example:
--query 'select * from test_db.`test_table`'
will become
--query 'select * from test_db.'
> Escape backtick from spark-submit arguments
> -------------------------------------------
>
> Key: LIVY-988
> URL: https://issues.apache.org/jira/browse/LIVY-988
> Project: Livy
> Issue Type: Task
> Reporter: Sanskar Modi
> Priority: Minor
>
> Currently, livy does not escape backticks from user-provided spark-submit
> arguments. So if a customer is passing any arguments that contain backticks,
> it will be considered as command substitution during spark-submit causing
> that argument to become blank or invalid.
> Example:
>
> {code:java}
> --query 'select * from test_db.`test_table`' {code}
> will become
>
>
> {code:java}
> --query 'select * from test_db.' {code}
>
> Github Issue: [https://github.com/apache/incubator-livy/issues/415]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
