Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EB6BEDA34 for ; Wed, 27 Jun 2012 17:55:13 +0000 (UTC) Received: (qmail 30735 invoked by uid 500); 27 Jun 2012 17:55:11 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 30633 invoked by uid 500); 27 Jun 2012 17:55:11 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 30541 invoked by uid 99); 27 Jun 2012 17:55:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jun 2012 17:55:11 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FSL_RCVD_USER,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of amansk@gmail.com designates 209.85.220.169 as permitted sender) Received: from [209.85.220.169] (HELO mail-vc0-f169.google.com) (209.85.220.169) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jun 2012 17:55:03 +0000 Received: by vcbfl10 with SMTP id fl10so1122213vcb.14 for ; Wed, 27 Jun 2012 10:54:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references:subject:x-mailer :mime-version:content-type:content-transfer-encoding :content-disposition; bh=z5tIZNZ1q0L9F0LHsv765N9ydIpjRxFYXjdeGMti9dE=; b=rxkLyJSMxir4WJ0SBZPzo8G8DLlvmZaAKLdq5t67TMKJRVdO0DdMtW70/o/vx9GNX0 D2F7jAQyGjfI6wMxLR0on8AWa/W40kaVoN/cLlrFPp99HAVLdw6PwhCfEmQMqv5ikSWi i22INjb74E2OGWetTYXirxVN2faGIQk9NB8roCAGYCE4QMYDlKUzYUlZ/OCNcWijc5jr /dNt+C6Y1gVr/8wP5mREZplxv2LsSKB1VW58wz1nscC6eAYkwDxNMoJk5uRea47LPDt0 Ej/nrSaoswX9frHatvGQvsEPR1inkd7cE2LS2a+srtc4e3pWEtw5+xSenYA98tlgjoWB LcBA== Received: by 10.52.69.240 with SMTP id h16mr12521310vdu.107.1340819682788; Wed, 27 Jun 2012 10:54:42 -0700 (PDT) Received: from [10.1.0.103] ([64.119.157.6]) by mx.google.com with ESMTPS id bn5sm51756670vdb.19.2012.06.27.10.54.40 (version=SSLv3 cipher=OTHER); Wed, 27 Jun 2012 10:54:41 -0700 (PDT) Date: Wed, 27 Jun 2012 13:54:40 -0400 From: Amandeep Khurana To: user@hbase.apache.org Message-ID: <2A3A1F4DB5E54E318F4931EBE2C82249@gmail.com> In-Reply-To: References: Subject: Re: Best practices for custom filter class distribution? X-Mailer: sparrow 1.6 (build 1081.27) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org Currently, you have to compile a jar, put them on all servers and restart the RS process. I don't believe there is an easier way to do it as of right now. And I agree, it's not entirely desirable to have to restart the cluster to install a custom filter. You can combine multiple filters into a FilterList and configure it in two modes: Pass All, or Pass One. Did you try that? Example: List myList = new ArrayList(); myList.add(myTimestampFilter); myList.add(myRowFilter); FilterList myFilterList = new FilterList(FilterList.Operator.MUST_PASS_ALL, myList); myFilterList.addFilter(myQualiFilter); On Wednesday, June 27, 2012 at 1:47 PM, Evan Pollan wrote: > What're the current best practices for making custom Filter implementation > classes available to the region servers? My cluster is running 0.90.4 from > the CDH3U3 distribution, FWIW. > > I searched around and didn't find anything other than "add your filter to > the region server's classpath." I'm hoping there's support for something > that doesn't involve actually installing jar files on each region server, > updating each region server's configuration, and doing a rolling restart of > the whole cluster... > > I did find this still-outstanding bug requesting parity between HDFS-based > co-processor class loading and filter class loading: > https://issues.apache.org/jira/browse/HBASE-1936. > > How are folks handling this? > > The stock filters are fairly limited, especially without the ability (at > least AFAIK) to combine the existing filters together via basic boolean > algebra, so I can't do much without writing my own filter(s). > > > thanks, > Evan