You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Nick Dimiduk (JIRA)" <ji...@apache.org> on 2016/06/16 16:09:05 UTC

[jira] [Commented] (PHOENIX-2891) Support system-wide UDFs

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

Nick Dimiduk commented on PHOENIX-2891:
---------------------------------------

bq. Similar to HBase "system coprocessors" in concept and implementation?

I'm not sure about this. I'm still talking about user-provided UDFs. All I'm thinking is we should support the "simple" path of just dropping jars into the region server's classpath in addition to the DynamicClassloader business we have today. From what I can tell, the only way to deploy a UDF right now is using DynamicClassloader, which as mentioned in the description, has some complexity.

> Support system-wide UDFs
> ------------------------
>
>                 Key: PHOENIX-2891
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2891
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 4.4.0
>            Reporter: Nick Dimiduk
>
> Current UDF implementation requires the use of DynamicClassLoader to locate function classes. This imposes all sorts of filesystem permissions complications when running clients as non-hbase users. Some of these problems can be simplified by supporting loading classes from "standard" classloader, IE, whatever is in hbase/sqlline's classpath. Not requiring the DynamicClassLoader means those permissions issues can be avoided and better support top-down installation of UDFs (ie, via configuration management systems like chef/puppet). This will enable a simplified model of deployment for system or "site" UDFs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)