[
https://issues.apache.org/jira/browse/SPARK-30095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067892#comment-17067892
]
Huaxin Gao edited comment on SPARK-30095 at 3/26/20, 5:45 PM:
--------------------------------------------------------------
I took a look of the create function doc, it has the following syntax for jar
and file:
{code:java}
resource_locations
Specifies the list of resources that contain the implementation of the function
along with its dependencies.
Syntax: USING { { (JAR | FILE ) resource_uri } , ... }
{code}
The syntax has ... which means the preceding elements can be repeated. It seems
to me that we cover the multiple jars OK. It also seems to me that we cover the
file syntax OK. I am thinking of closing this ticket.
was (Author: huaxingao):
I took a look of the create function doc, it has the following syntax for jar
and file:
resource_locations
Specifies the list of resources that contain the implementation of the function
along with its dependencies.
Syntax: USING { { (JAR | FILE ) resource_uri } , ... }
The syntax has ... which means the preceding elements can be repeated. It seems
to me that we cover the multiple jars OK. It also seems to me that we cover the
file syntax OK. I am thinking of closing this ticket.
> create function syntax has to be enhance in Doc for multiple dependent jars
> ----------------------------------------------------------------------------
>
> Key: SPARK-30095
> URL: https://issues.apache.org/jira/browse/SPARK-30095
> Project: Spark
> Issue Type: Sub-task
> Components: Documentation
> Affects Versions: 3.0.0
> Reporter: ABHISHEK KUMAR GUPTA
> Priority: Minor
>
> Create Function Example and Syntax has to be enhance as below
> 1. Case 1: How to use multiple dependent jars in the path while creating
> function is not clear. -- Syntax to be given
> 2. Case 2: What are the different schema supported like file:/// is not
> updated in doc - Supported Schema to be provided
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]