Re: hbase.rpc.timeout issue

We have resolved the issue by following these steps. This is just for the benefit of someone facing similar issues. Regards, Ajit 1. Set client side environment variables: ​ Create some conf folder e.g. /home/conf​ setenv HBASE_CONF_DIR / ​home /conf ​ ​2. Create hbase-site.xml, Make sure

Re: Maximum (LIMIT) possible results

Yes. Please just try things like this in the future :) On 6/11/17 12:33 AM, Cheyenne Forbes wrote: Can I have something like /"select id from table limit 10"/ Regards, Cheyenne

Re: Phoenix index update on direct HBase row update

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

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

Re: Phoenix index update on direct HBase row update

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

Phoenix index update on direct HBase row update

We updates our HBase table directly without Phoenix. Is it possible to make indexes keep in sync with this updates?