Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
MIME-Version: 1.0
In-Reply-To: 
 <OF17D77399.6BBF5B92-ON85257C8C.00578B9C-85257C8C.0058C2AD@us.ibm.com>
References: 
 <OF17D77399.6BBF5B92-ON85257C8C.00578B9C-85257C8C.0058C2AD@us.ibm.com>
From: Jean-Marc Spaggiari <jean-marc@spaggiari.org>
Date: Thu, 27 Feb 2014 11:11:30 -0500
Message-ID: 
 <CAPQV63XtynQEKjbkVhSRKqEQm3y+awfSwtPqaR7M-jL+SjtHvQ@mail.gmail.com>
Subject: Re: mutable index in phoenix
To: user <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=089e013d0b5630f55504f365944c

--089e013d0b5630f55504f365944c
Content-Type: text/plain; charset=UTF-8

Hi Wei,

If this is a Phoenix specific question, you might want to ask it on the
Phoenix mailing list. You will get better results.

JM


2014-02-27 11:09 GMT-05:00 Wei Tan <wtan@us.ibm.com>:

> Hi, I am reading this
> https://github.com/forcedotcom/phoenix/wiki/Secondary-Indexing and trying
> to figure out what is the difference between mutable and immutable index.
> One difference I figure out is that immutable index is client-managed
> while mutable index is cp-managed.
>
> I was expecting that, mutable index coprocessor do three things: 1) put
> new index entry, 2) read base table and get old index value, 3) delete old
> index value if any. I could not find code for 2) and 3). So am I
> understanding it wrong, or I did not find the correct code path?
>
> Thanks,
> Wei
>
> ---------------------------------
> Wei Tan, PhD
> Research Staff Member
> IBM T. J. Watson Research Center
> http://researcher.ibm.com/person/us-wtan

--089e013d0b5630f55504f365944c--