From user-return-484-apmail-phoenix-user-archive=phoenix.apache.org@phoenix.incubator.apache.org Sun Apr 6 16:21:26 2014 Return-Path: X-Original-To: apmail-phoenix-user-archive@minotaur.apache.org Delivered-To: apmail-phoenix-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 376AD11175 for ; Sun, 6 Apr 2014 16:21:26 +0000 (UTC) Received: (qmail 18190 invoked by uid 500); 6 Apr 2014 16:21:24 -0000 Delivered-To: apmail-phoenix-user-archive@phoenix.apache.org Received: (qmail 18132 invoked by uid 500); 6 Apr 2014 16:21:23 -0000 Mailing-List: contact user-help@phoenix.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@phoenix.incubator.apache.org Delivered-To: mailing list user@phoenix.incubator.apache.org Received: (qmail 18123 invoked by uid 99); 6 Apr 2014 16:21:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Apr 2014 16:21:23 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of juan.rodriguez.hortala@gmail.com designates 209.85.219.44 as permitted sender) Received: from [209.85.219.44] (HELO mail-oa0-f44.google.com) (209.85.219.44) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Apr 2014 16:21:18 +0000 Received: by mail-oa0-f44.google.com with SMTP id n16so5649171oag.31 for ; Sun, 06 Apr 2014 09:20:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=+Ub2QssJ2DdRVw7ANRTmghqgGrNU02wEOOiNaAi3xJ0=; b=PVhMIP8LmmtYGmXrr3dFeOPk/RgxboAw6OumsLdiuSo2E9SrLgrVChWFKRdvlD/lN7 qMA+RaLnovb/GOakhPwfgix9MuYwQfgM9/GHSpfPUtec0VU2q/bomuK6ZnJof5AyEruu aTbgFKsEsuGlNUYEhMto1mgPftmkiBpInbpJH0RZNCqlPXMlXCc/YE6aEgu1X1HrjiPB YOEoWLbsm/egp3iWVUPuUuIANyBfQXKNA1LzNP+Ab7hCWwKV40Q/6ZuVrV5uOkCn8PA6 E+6D+NOmceKHERflnNYvmueWX1n7ptH1EkBsogXhy8rdS4ULKpInlInqs8aOfYY3lTcR mUEg== MIME-Version: 1.0 X-Received: by 10.60.176.39 with SMTP id cf7mr2785736oec.45.1396801255751; Sun, 06 Apr 2014 09:20:55 -0700 (PDT) Received: by 10.60.34.227 with HTTP; Sun, 6 Apr 2014 09:20:55 -0700 (PDT) Reply-To: juan.rodriguez.hortala@gmail.com In-Reply-To: References: Date: Sun, 6 Apr 2014 18:20:55 +0200 Message-ID: Subject: Re: Built-in functions in Phoenix From: =?ISO-8859-1?Q?Juan_Rodr=EDguez_Hortal=E1?= To: user@phoenix.incubator.apache.org Content-Type: multipart/alternative; boundary=089e01183fe8abc79204f662226b X-Virus-Checked: Checked by ClamAV on apache.org --089e01183fe8abc79204f662226b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi James, Thanks for your answer, from that I understand that built-in functions as described in that post are a way to extend Phoenix, but to use each new function you should recompile and redeploy Phoenix. Again, thanks for the information, Greetings, Juan 2014-04-06 9:49 GMT+02:00 James Taylor : > Hi Juan, > Good question. We're definitely interested in contributions for any > built-ins that folks think are useful, provided that they're generally > useful and follow SQL standards. In the past we've taken these and bundle= d > them in the next release of Phoenix. So please feel free to contribute. > > The JIRA you mentioned (https://issues.apache.org/jira/browse/PHOENIX-538= ) > is more about having a way for built-in functions to be dynamically loade= d. > We're open to that as well, but until coprocessors have a way of being > "sandboxed", we'd need a way to disable the feature, as I suspect many > companies would consider this a potential security hole (and thus want a > way of disabling it). > > Thanks, > James > > > On Sat, Apr 5, 2014 at 11:02 AM, Juan Rodr=EDguez Hortal=E1 < > juan.rodriguez.hortala@gmail.com> wrote: > >> Hi, >> >> In another message to this list, I saw a reference to >> http://phoenix-hbase.blogspot.com.es/2013/04/how-to-add-your-own-built-i= n-function.html?m=3D1, >> where it's shown how to create a scalar built-in function in Phoenix. I'= m >> surprised because I though UDF's were not in the roadmap, according to t= his >> Jira https://issues.apache.org/jira/browse/PHOENIX-538 where it says >> "until coprocessors have a way to run inside their own sandbox, we'd wan= t >> to have a way to disable this feature". I think this feature is very >> interesting, so I'm wondering whether this built-in functions are execut= ed >> in the client or in the Region Servers as coprocessors. If that's the ca= se, >> are they running in a sandboxed environment to protect the Region Server= s? >> >> Thanks a lot for the information, >> >> Greetings, >> >> >> Juan Rodr=EDguez Hortal=E1 >> > > --089e01183fe8abc79204f662226b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi James,

Thanks for your answer, = from that I understand that built-in functions as described in that post ar= e a way to extend Phoenix, but to use each new function you should recompil= e and redeploy Phoenix.

Again, thanks for the information,

Greetings,

Juan =


201= 4-04-06 9:49 GMT+02:00 James Taylor <jamestaylor@apache.org>:
Hi Juan,
Good question.= We're definitely interested in contributions for any built-ins that fo= lks think are useful, provided that they're generally useful and follow= SQL standards. In the past we've taken these and bundled them in the n= ext release of Phoenix. So please feel free to contribute.

The JIRA you mentioned (https://issues.apache.org/= jira/browse/PHOENIX-538) is more about having a way for built-in functi= ons to be dynamically loaded. We're open to that as well, but until cop= rocessors have a way of being "sandboxed", we'd need a way to= disable the feature, as I suspect many companies would consider this a pot= ential security hole (and thus want a way of disabling it).

Thanks,
James


On Sat, Apr 5, 2014 at 11:02 AM, Juan Rodr=EDguez Hortal=E1 <juan.rodriguez.hortala@gmail.com> wrote:

Hi,


In another message to this list, I saw a refe= rence to http://phoenix-hbase.blogspot.com.es/2013/04/how-to-add-your-own-built-in= -function.html?m=3D1, where it&rsq= uo;s shown how to create a scalar built-in function in Phoenix. I’m s= urprised because I though UDF’s were not in the roadmap, according to= this Jira https://issues.apache.org/jira/browse/PH= OENIX-538 where it says “unt= il coprocessors have a way to run inside their own sandbox, we'd want t= o have a way to disable this feature”. I think this feature is very i= nteresting, so I’m wondering whether this built-in functions are exec= uted in the client or in the Region Servers as coprocessors. If that’= s the case, are they running in a sandboxed environment to protect the Regi= on Servers?


Thanks a lot for the information,


Greetings,


Juan Rodr=EDguez Hortal=E1



--089e01183fe8abc79204f662226b--