phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-4231) Support restriction of remote UDF load sources
Date Tue, 13 Feb 2018 00:49:00 GMT


Andrew Purtell commented on PHOENIX-4231:

No, we want to restrict loading to hbase.dynamic.jars.dir. Or we could define a Phoenix specific
directory for UDFs, configurable by site file.

Whether or not the user can write to the directory isn't important. In fact, in our production
we don't want the user to be able to write jars to HDFS at all. We will preposition safe and
vetted UDF jars in HDFS and Phoenix can load them from there, but ONLY from there.

> 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