The first client to connect to Phoenix and notice the absence of
SYSTEM.SEQUENCE will create the table. That means the
configuration phoenix.sequence.saltBuckets must be set on that client.
On Tue, Mar 3, 2015 at 1:17 PM, Vamsi Krishna vamsi.attl...@gmail.com
wrote:
James,
We tried the
James,
We tried the following steps:
1) Dropped SYSTEM.SEQUENCE table from base
1.1) disable 'SYSTEM.SEQUENCE'
1.2) drop 'SYSTEM.SEQUENCE'
2) Deleted SYSTEM.SEQUENCE meta-data from phoenix system tables
(SYSTEM.CATALOG, SYSTEM.STATS)
2.1) delete from SYSTEM.CATALOG where table_name = 'SEQUENCE'
I'd recommend dropping the SYSTEM.SEQUENCE table from the HBase shell
(instead of deleting the folder in HDFS). Everything else sounded
fine, but make sure to bounce your cluster and restart your clients
after doing this.
Thanks,
James
On Thu, Feb 26, 2015 at 12:28 PM, Vamsi Krishna
Hi,
From phoenix archives I see that we can drop SYSTEM.SEQUENCE table and
set 'phoenix.sequence.saltBuckets'
property to '1' to see the SYSTEM.SEQUENCE table recreated with 1 salt
bucket on cluster restart.
Reference:
