From dev-return-49083-archive-asf-public=cust-asf.ponee.io@phoenix.apache.org Fri Feb 2 21:24:04 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 4F968180608 for ; Fri, 2 Feb 2018 21:24:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 3F216160C25; Fri, 2 Feb 2018 20:24:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8A15C160C49 for ; Fri, 2 Feb 2018 21:24:03 +0100 (CET) Received: (qmail 78059 invoked by uid 500); 2 Feb 2018 20:24:02 -0000 Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@phoenix.apache.org Delivered-To: mailing list dev@phoenix.apache.org Received: (qmail 78041 invoked by uid 99); 2 Feb 2018 20:24:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Feb 2018 20:24:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 08C2A198C46 for ; Fri, 2 Feb 2018 20:24:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id EixD1Dbg2Flu for ; Fri, 2 Feb 2018 20:24:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D3C575F666 for ; Fri, 2 Feb 2018 20:24:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6AE82E02F7 for ; Fri, 2 Feb 2018 20:24:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2763121E84 for ; Fri, 2 Feb 2018 20:24:00 +0000 (UTC) Date: Fri, 2 Feb 2018 20:24:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (PHOENIX-4231) Support restriction of remote UDF load sources MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/PHOENIX-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350909#comment-16350909 ] ASF GitHub Bot commented on PHOENIX-4231: ----------------------------------------- GitHub user ChinmaySKulkarni opened a pull request: https://github.com/apache/phoenix/pull/292 PHOENIX-4231: Support restriction of remote UDF load sources - Added feature to be able to add jars from an HDFS URI. - Restrict loading of jars to be only from the hbase.dynamic.jars.dir directory. Testing done: - Tested that the user is able to add jars from an HDFS URI reachable on the network as well as local filesystem. - Tested that the user is unable to create a function where the jar is loaded from any directory apart from hbase.dynamic.jars.dir. - Tested that HDFS URIs without scheme and authority work. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ChinmaySKulkarni/phoenix PHOENIX-4231 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/phoenix/pull/292.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #292 ---- commit 9351e1b4d4a5741bbf063f0d6cd31f14cfa1e6b6 Author: Chinmay Kulkarni Date: 2018-02-02T20:16:47Z PHOENIX-4231: Support restriction of remote UDF load sources - Added feature to be able to add jars from an HDFS URI. - Restrict loading of jars to be only from the hbase.dynamic.jars.dir directory. Testing done: - Tested that the user is able to add jars from an HDFS URI reachable on the network as well as local filesystem. - Tested that the user is unable to create a function where the jar is loaded from any directory apart from hbase.dynamic.jars.dir. - Tested that HDFS URIs without scheme and authority work. ---- > 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)