[ 
https://issues.apache.org/jira/browse/PHOENIX-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16360531#comment-16360531
 ] 

Rajeshbabu Chintaguntla commented on PHOENIX-4231:
--------------------------------------------------

[~aertoria] [~ckulkarni]
As for my understanding in the pull request we are restricting the udf jars 
path to hbase.dynamic.jars.dir path. But some cases as [~apurtell] mentioned 
all clients may not allowed for reading or writing jars to 
hbase.dynamic.jars.dir path in that case we can make use any other directory in 
HDFS for keeping the jars. So I think we should not impose this restriction 
otherwise UDFs feature may not be usable until unless the client have write 
permissions on hbase.dynamic.jars.dir path.
[~apurtell] 
As for the description what I think is currently we are able to load jars from 
any HDFS so we need to restrict udf jars to to be loaded from local HDFS only 
right?


> Support restriction of remote UDF load sources 
> -----------------------------------------------
>
>                 Key: PHOENIX-4231
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4231
>             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
(v7.6.3#76005)

Reply via email to