Re: Direct HBase vs. Phoenix query performance

Thanks James! I've made a JIRA ticket here: https://issues.apache.org/jira/projects/PHOENIX/issues/PHOENIX-4666 This is a priority for us at 23andMe as it substantially affects some of our queries, so we'd be happy to provide a patch if Phoenix maintainers are able to provide some guidance on the

Re: phoenix + protobuf 3

You'll like have to shade the use of Protobuf3 in your application. this is not something "optional". HBase2 (and the sister release Phoenix5) will have done this shading internally which will make this easier for you downstream. However, these releases have not yet been made. On 3/21/18

Re: tmp files

I would assume that they would be cleaned up, but I don't have specifics to point you to off the top of my head. On 3/21/18 4:32 AM, Flavio Pompermaier wrote: Is there a way to cleanup them? Are they left there when client query are interrupted? On Wed, Mar 21, 2018 at 3:00 AM, Josh Elser

Re: tmp files

Is there a way to cleanup them? Are they left there when client query are interrupted? On Wed, Mar 21, 2018 at 3:00 AM, Josh Elser wrote: > Are they ResultSpooler files? > > If so, you want to set `phoenix.spool.directory` which defaults to the > java.io.tmpdir system