Re: Local index not used with non covered queries

Hi Rajeshbabu, Thanks for the quick answer! I will keep an eye on that issue. I was expecting this to be working at least for local indexes. So, if the where condition refers to an indexed column and a non indexed column, it should use the index? I have tried this, and its not working for me.

Re: Hbase on EMR for phoenix

The problem is that EMR hasn't updating their HBase version past 0.94 in the last two years. Phoenix stopped doing releases supporting 0.94 a year ago and HBase has moved well past 0.94 as well. Phoenix will run just fine on EMR if they update their HBase version. My two cents: I'd recommend

Re: Hbase on EMR for phoenix

Thanks for the update James. Is the latest HBase getting integrated into BigTop - perhaps I'm looking in the wrong place, but this is what I found and it's hard to tell if it's the latest. https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common/hbase It seems like the latest EMR

Re: Hbase on EMR for phoenix

Let the folks at EMR know. I will too. On Thu, Feb 4, 2016 at 5:14 PM, j pimmel wrote: > It would appear not at this point. Though it would be great to get the > full Hbase + Phoenix stacks supported out-of-the-box. > > > > On Thu, 4 Feb 2016 at 16:56 James Taylor

Re: Hbase on EMR for phoenix

That's good news. Phoenix is in BigTop too. Did EMR not include it? On Thu, Feb 4, 2016 at 4:48 PM, j pimmel wrote: > Thanks for the update James. > > Is the latest HBase getting integrated into BigTop - perhaps I'm looking > in the wrong place, but this is what I

Re: Disable Index

See https://phoenix.apache.org/language/index.html#alter_index On Thu, Feb 4, 2016 at 12:11 PM, Kumar Palaniappan < kpalaniap...@marinsoftware.com> wrote: > While data migration, we simply drop the indices on the tables and > recreate. Would like to avoid. > > Is there disable all index syntax

Re: Hbase on EMR for phoenix

It would appear not at this point. Though it would be great to get the full Hbase + Phoenix stacks supported out-of-the-box. On Thu, 4 Feb 2016 at 16:56 James Taylor wrote: > That's good news. Phoenix is in BigTop too. Did EMR not include it? > > On Thu, Feb 4, 2016 at

Re: Hbase on EMR for phoenix

Bigtop packages HBase 0.98 and is something Phoenix still supports. The latest HBase release is 1.1. I think Bigtop will be moving up to HBase 1.1 soon. Phoenix supports that version as well. On Thu, Feb 4, 2016 at 4:48 PM, j pimmel wrote: > Thanks for the update

REG: Query failing when executing through JDBC

Hi There, I have a query which is failing when executing through JDBC (using spring jdbctemplate) but when the same query is executed through sqlline it is working fine. the thing is the column does not belong to my table at all. Here is the Stack Trace of the error when executing through JDBC

Re: Hbase on EMR for phoenix

I asked about Phoenix on EMR, and also received no response. It would be nice to have a comment on this from someone in the know, if only to confirm that Phoenix and EMR are no longer friends. James On 26/01/16 16:37, j pimmel wrote: Hi all I'm just evaluating using HBase with phoenix on

Re: Local index not used with non covered queries

bq. if the where condition refers to an indexed column and a non indexed column, it should use the index? This case also we will not use the index because we need to know the values of non indexed columns first to apply the filter which we need to get from the data table. So better to include

Phoenix Query Server and/or Avatica Bug and/or My Misunderstanding

I can query Phoenix by doing something like this: curl -v -XPOST -H 'request: {"request":"prepareAndExecute","connectionId":"aaa","sql":"select * from CAT_MAP"}' http://10.0.100.57:8765/ However, I am unable to make such a request in Javascript in my web page because the POST method, along with

Re: Local index not used with non covered queries

Hi Jacobo, The local index will be used if you have any where condition on indexed column otherwise we need to scan index table and data table for each row. That's the reason why it's not using local indexes. There is no index merging currently in Phoenix. There is an improvement task raised for

Disable Index

While data migration, we simply drop the indices on the tables and recreate. Would like to avoid. Is there disable all index syntax in phoenix grammar? How do we disable an index? If we disable index in phoenix and rebuild what does that translates to phoenix intercepting WAL? We know rebuilding