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
Hi Kristoffer,
You'll need to upgrade first from 2.2.3 to 3.0.0-incubating, and then
to each minor version (3.1 and then 3.2.2) to trigger the upgrade for
each release. You can access previous releases from the "Download
Previous Releases" link here: http://phoenix.apache.org/download.html.
We'll i
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 run
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 3.
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,
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 tha
Yes, all our test cases pass so I think we're good.
Maybe there isn't a problem in sqlline after all. It acts the same even if
I create 3.2.2 tables from a clean installation.
I realized that it calibrate the width of the console window and chop off
everything else off. This makes it look broken
This is not a major thing anyway. I managed to use SQuirreL with the JDBC
driver which works better than sqlline.
On Mon, Jan 19, 2015 at 11:53 AM, Kristoffer Sjögren
wrote:
> Yes, all our test cases pass so I think we're good.
>
> Maybe there isn't a problem in sqlline after all. It acts the sa
