Re: Problems upgrading 2.2.3-incubating to 3.2.1

2015-01-15 Thread James Taylor
Yes, you can delete the SYSTEM.TABLE through the hbase shell. You can also remove any coprocessors that no longer exist from existing tables. But I wouldn't do that until you're sure everything is functioning correctly. That's worrisome that sqlline isn't displaying the metadata properly. Other

Re: Problems upgrading 2.2.3-incubating to 3.2.1

2015-01-14 Thread Kristoffer Sjögren
Yes, single quotes for the default column family works. CREATE TABLE TABLE ( C1 INTEGER NOT NULL, C2 INTEGER NOT NULL, C3 BIGINT NOT NULL, C4 BIGINT NOT NULL, C5 CHAR(2) NOT NULL, V BIGINT CONSTRAINT PK PRIMARY KEY ( C1, C2, C3, C4,

Re: Problems upgrading 2.2.3-incubating to 3.2.1

2015-01-13 Thread Kristoffer Sjögren
Hi James I tried the upgrade path you mentioned and it worked as far as I can tell. Insert and query existing tables works at least. The only thing that worries me is an exception thrown at region server start up [1] and frequent periodic exceptions complaining about building the index [2] in

Re: Problems upgrading 2.2.3-incubating to 3.2.1

2015-01-13 Thread James Taylor
The warning for [1] can be ignored, but [2] is problematic. You're coming from a very old version (our first incubator release ever), it's going to be difficult to figure out where the issue is. One alternative means of upgrading might be to manually rerun your CREATE TABLE statements on top of

Problems upgrading 2.2.3-incubating to 3.2.1

2015-01-12 Thread Kristoffer Sjögren
Hi I'm trying to upgrade phoenix 2.2.3-incubating to phoenix 3.2.2 on my local computer first in order to gain confidence that it will work on the production cluster. We use HBase 0.94.6 CDH 4.4.0. 1) My first question is what release to pick? There is no phoenix 3.2.2 jar in maven central (only