phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ethan Wang (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-4231) Support restriction of remote UDF load sources
Date Mon, 26 Feb 2018 20:19:00 GMT


Ethan Wang commented on PHOENIX-4231:

To summarize what we are going to be working on this jira: As of today, loading from add
jars 'XX' allows loading the jars from any hdfs network location to local's hbase.dynamic.jars.dir.
So we are now going to make addition features to PHOENIX-1890 so that:

when a property, say "" property is configured as false, "add
jars" command only restricted to load from local file system or local hdfs.

Is the plan above accurate?



Once this feature is done. user will be doing the following for creating a Udf:

Add jars hdfs://localhost/udf.jar

CREATE FUNCTION func(VARCHAR) returns VARCHAR as 'com.example.test.udfFunc' using jar 'configured/hbase/dynamic/jars/dir/udf2.jar'


> Support restriction of remote UDF load sources 
> -----------------------------------------------
>                 Key: PHOENIX-4231
>                 URL:
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>            Assignee: Chinmay Kulkarni
>            Priority: Major
> When allowUserDefinedFunctions is true, users can load UDFs remotely via a jar file from
any HDFS filesystem reachable on the network. The setting hbase.dynamic.jars.dir can be used
to restrict locations for jar loading but is only applied to jars loaded from the local filesystem.
 We should implement support for similar restriction via configuration for jars loaded via
hdfs:// URIs.

This message was sent by Atlassian JIRA

View raw message