Re: Phoenix index update on direct HBase row update

2017-06-15 Thread James Taylor
See MutationState.setMetaDataOnMutations(). We either make a separate RPC so as not to put too much data on every mutation or we attach the metadata on every mutation. On Thu, Jun 15, 2017 at 6:17 PM, Batyrshin Alexander <0x62...@gmail.com> wrote: > What metadata is needed? Maybe you point me to

Re: Phoenix index update on direct HBase row update

2017-06-15 Thread Batyrshin Alexander
What metadata is needed? Maybe you point me to example or to related source code of Phoenix API? > On 16 Jun 2017, at 03:41, James Taylor wrote: > > No, not unless you write the code that keeps the index in sync yourself, > attach the metadata needed by index maintenance coprocessor in your up

Re: Phoenix index update on direct HBase row update

2017-06-15 Thread James Taylor
No, not unless you write the code that keeps the index in sync yourself, attach the metadata needed by index maintenance coprocessor in your update code, or use the Phoenix update APIs which do this for you. On Thu, Jun 15, 2017 at 5:29 PM, Batyrshin Alexander <0x62...@gmail.com> wrote: > We upd

Phoenix index update on direct HBase row update

2017-06-15 Thread Batyrshin Alexander
We updates our HBase table directly without Phoenix. Is it possible to make indexes keep in sync with this updates?