Re: phoenix explain plan not showing any difference after adding a local index on the table column that is used in query filter

Please replace 'Select * from...' with 'Select COL1,COL2,COL3 from...'. I did the same and it worked. Not sure about the exact reason. -- View this message in context:

Re: How to deal with Phoenix Secondary Indexes & HBase snapshots in batch job

Hi Vamsi, Can you please explain what is the rational behind maintaining 2 phoenix tables? If I'm not wrong, maintaining a single phoenix table with single view on it and updating/inserting new data into that table with oozie job should work fine. Phoenix csvBulkLoad tool also populates all

Re: For multiple local indexes on Phoenix table only one local index table is being created in HBase

Hi Vamsi, Creating a single hbase table for all LOCAL indexes of a phoenix data table is a regular/expected behavior. Phoenix local indexes targets write heavy use cases hence maintaining data table and single index table in same region server prevents network overhead during writes. If you want

Number of Columns in Phoenix Table

Hi , Is there any limit on the number of columns that can be stored in a Phoenix table where all the columns are qualifiers of a single Column family ? I would like to create a table which will scale horizontally with dynamic columns and should not be more than 2500 columns , each of these

PhoenixFunction

when I use the functions described on your website. some function work well such as count() and min(), But with exp() it returned with Function undefined. functionName=[EXP] not found my phoenix version is phoenix-4.4.0-HBase-0.98-bin. I just want to confirm whether my version not support some

Errors while launching sqlline

Hi, We are trying to do a small POC with Hbase 1.2.1 , Hadoop 2.6.4, zookeeper 3.4.8 and phoenix 4.7.0. We have setup a three node zookeeper quorum, and hbase 1.2.1 setup with 3 region servers. The Hbase and zk setup seems to be OK, as we are able to do basic CRUD operations with

Re: dropping Phoenix local index is not dropping the local index table in HBase

Since we are storing all local indexes data in a single shared table that's why we are not dropping when we drop a local index. We can check for any local indexes or not and then we can drop it. Now as part of PHOENIX-1734 we have reimplemented local indexes and storing local indexes also in same

Re: PhoenixFunction

Hi Yang, Actually , I use org.apache.phoenix.expression.ExpressiontType of the version I'm using to check the build in function available in that version. I know this is not a good way. For example , following built in functions will not be available in 4.4 as they are added in later

Re: For multiple local indexes on Phoenix table only one local index table is being created in HBase

Hi Vamsi, Phoenix uses single local Index table for all the local indexes created on a particular data table. Rows are differentiated by local index sequence id and filtered when requested during the query for particular index. Regards, Ankit Singhal Re On Tue, Jun 28, 2016 at 4:18 AM, Vamsi

Re: phoenix explain plan not showing any difference after adding a local index on the table column that is used in query filter

Hi Vamsi, *Explain plan:* explain select * from vamsi.table_a where col2 = 'abc'; +-+ |PLAN | +-+ | CLIENT 5-CHUNK

RE: phoenix explain plan not showing any difference after adding a local index on the table column that is used in query filter

Hi Ankit, I think this is not completely true.  Phoenix uses local index table when all columns in where clause and atleast one column in select clause are part of local index table.  "Select col1,col2,col3 from table" uses local index but "select * from table" do not.  I'm not certain of

Re: Number of Columns in Phoenix Table

I haven't exhaustively perf. tested but I have a Phoenix table with 15K columns in a single column family storing values in only 20 or so columns per row and it's performance seems on par with table with few columns. On Wed, Jun 29, 2016 at 3:27 AM, Siddharth Ubale < siddharth.ub...@syncoms.com>