Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of yuzhihong@gmail.com
 designates 209.85.213.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAJo9sUYPX=sK_2XDsVUT_8N5HPH0QX6Qc31oPT65g6xtd7H7bw@mail.gmail.com>
References: 
 <CAJo9sUYPX=sK_2XDsVUT_8N5HPH0QX6Qc31oPT65g6xtd7H7bw@mail.gmail.com>
Date: Tue, 9 Sep 2014 13:23:54 -0700
Message-ID: 
 <CALte62x7R8kAg9GVMxOoMeQuKrs+P6_zX_0sgWtoL_BACr2yCA@mail.gmail.com>
Subject: Re: HBase custom filter protocol buffers
From: Ted Yu <yuzhihong@gmail.com>
To: "user@hbase.apache.org" <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=20cf30563e8be207cc0502a7b64d

--20cf30563e8be207cc0502a7b64d
Content-Type: text/plain; charset=UTF-8

For each of your filters that carries custom information (limit, range,
etc), you need to create corresponding protobuf entity.

See hbase-protocol/src/main/protobuf/Filter.proto for examples.

Cheers

On Tue, Sep 9, 2014 at 12:55 PM, Kevin <kevin.macksamie@gmail.com> wrote:

> Hi,
>
> I'm making the switch from 0.92.1 to 0.98.1, and I'm in the process of
> updating all my custom filters to conform to the new HBase Filter API. I
> have quite a few custom filters, so my question is: Must I create a custom
> protocol buffer for each of my filters or I can reuse the custom logic that
> I had in writeFields() and readFields() in toByteArray() and
> parseFrom(byte[]), respectively?
>
> I did post this same question on Cloudera's CDH User Google group, but I
> figured it was better suited to be asked on the official HBase mailing
> list. (Sorry for posting in multiple locations.)
>
> Thanks,
> Kevin
>

--20cf30563e8be207cc0502a7b64d--