Re: Secondary index rebuilding

Yes, see https://phoenix.apache.org/secondary_indexing.html#Consistency_ Guarantees On Wednesday, June 1, 2016, Sumit Nigam wrote: > Hi, > > I recently noticed that one of my secondary index was short of 2 entries > compared to data table. > > AFAIK, the first update is

Secondary index rebuilding

Hi, I recently noticed that one of my secondary index was short of 2 entries compared to data table.  AFAIK, the first update is always to index table. So, the only way an index table could fall behind the main table is when the index was disabled by phoenix. Maybe the region server hosting

Does Phoenix Secondary Indexes handle WAL log specially ?

Hi, We are using phoenix and hbase-indexer for our hbase cluster and we have found a curious phenomenon about phoenix secondary indexes : We put data (use psql to import csv data) into one table(C_PICRECORD) with two global mutable index tables(C_PICRECORD_IDX1 and C_PICRECORD_IDX2) from phoenix

linkage error using Groovy

I’m trying to get a database connection using the Phoenix JDBC driver in a Groovy script. I’m running into linkage errors. I assume its a conflict between the xerces libraries packaged in the phoenix-client.jar and those included in the JDK. Is there a workaround for this? Caught: