You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by Jason Rutherglen <ja...@gmail.com> on 2011/03/15 20:19:04 UTC
Coprocessor postWALRestore deletes
How does one know if a postWALRestore is a delete? There's a set of
methods KeyValue.isDelete*. Should one use these? For a single
postWALRestore method call, is there only one delete (rather than an a
batch delete, add, etc)?
Re: Coprocessor postWALRestore deletes
Posted by Ted Yu <yu...@gmail.com>.
I think there may be more than one delete per edit.
On Tue, Mar 15, 2011 at 2:45 PM, Jason Rutherglen <
jason.rutherglen@gmail.com> wrote:
> Ted, thanks for the info.
>
> > Please note that WALEdit parameter for postWALRestore() contains the
> > collection of edits (KeyValue objects)
>
> Is the collection of edit limited to a single row? Can there be
> multiple deletes per edit?
>
> On Tue, Mar 15, 2011 at 1:38 PM, Ted Yu <yu...@gmail.com> wrote:
> > Jason:
> > There're 3 types of deletes:
> > Delete((byte)8),
> > DeleteColumn((byte)12),
> > DeleteFamily((byte)14),
> > You can choose the corresponding KeyValue method
> >
> > Please note that WALEdit parameter for postWALRestore() contains the
> > collection of edits (KeyValue objects)
> >
> > On Tue, Mar 15, 2011 at 12:19 PM, Jason Rutherglen <
> > jason.rutherglen@gmail.com> wrote:
> >
> >> How does one know if a postWALRestore is a delete? There's a set of
> >> methods KeyValue.isDelete*. Should one use these? For a single
> >> postWALRestore method call, is there only one delete (rather than an a
> >> batch delete, add, etc)?
> >>
> >
>
Re: Coprocessor postWALRestore deletes
Posted by Jason Rutherglen <ja...@gmail.com>.
Ted, thanks for the info.
> Please note that WALEdit parameter for postWALRestore() contains the
> collection of edits (KeyValue objects)
Is the collection of edit limited to a single row? Can there be
multiple deletes per edit?
On Tue, Mar 15, 2011 at 1:38 PM, Ted Yu <yu...@gmail.com> wrote:
> Jason:
> There're 3 types of deletes:
> Delete((byte)8),
> DeleteColumn((byte)12),
> DeleteFamily((byte)14),
> You can choose the corresponding KeyValue method
>
> Please note that WALEdit parameter for postWALRestore() contains the
> collection of edits (KeyValue objects)
>
> On Tue, Mar 15, 2011 at 12:19 PM, Jason Rutherglen <
> jason.rutherglen@gmail.com> wrote:
>
>> How does one know if a postWALRestore is a delete? There's a set of
>> methods KeyValue.isDelete*. Should one use these? For a single
>> postWALRestore method call, is there only one delete (rather than an a
>> batch delete, add, etc)?
>>
>
Re: Coprocessor postWALRestore deletes
Posted by Ted Yu <yu...@gmail.com>.
Jason:
There're 3 types of deletes:
Delete((byte)8),
DeleteColumn((byte)12),
DeleteFamily((byte)14),
You can choose the corresponding KeyValue method
Please note that WALEdit parameter for postWALRestore() contains the
collection of edits (KeyValue objects)
On Tue, Mar 15, 2011 at 12:19 PM, Jason Rutherglen <
jason.rutherglen@gmail.com> wrote:
> How does one know if a postWALRestore is a delete? There's a set of
> methods KeyValue.isDelete*. Should one use these? For a single
> postWALRestore method call, is there only one delete (rather than an a
> batch delete, add, etc)?
>