BTW, I'm using version phoenix-4.7.0.2.5.0.0-1245
On Fri, Jun 9, 2017 at 12:58 PM, Michael Young wrote:
> Thanks, Ankit!
>
> I have an issue when connecting to sqlline.py using the
> CurrentSCN=149091840
> (3/31/2017)
>
> I get >> java.sql.SQLException: ERROR 1010 (42M01): Not allowed to mu
Thanks, Ankit!
I have an issue when connecting to sqlline.py using the
CurrentSCN=149091840
(3/31/2017)
I get >> java.sql.SQLException: ERROR 1010 (42M01): Not allowed to mutate
table.
I use TS=1 day prior to last timestamp in row data (
timestamp=149100480 (4/1/2017)) and my data has on
Hi Michael,
bq. "exact DDL" Does this mean including all qualifiers like
COMPRESSION='SNAPPY', SALT_BUCKETS=64, ... etc...? If we don't use the
exact DDL, will Phoenix not behave correctly?
yes, Phoenix will not behave well if properties affecting the write path
are not consistent during the read
I have a doubt about step 2 from Ankit Singhal's response in
http://apache-phoenix-user-list.1124778.n5.nabble.com/Phoenix-4-4-Rename-table-Supported-td1781.html
He says:
2. Open phoenix connection at timestamp 1 day less than the oldest data in
your tables ( by specifying ts in CurrentSCN ./sqll
ah haafter some googling I found some info from Ankit, copied below
Looks like I was missing step 2. I don't know how to get the CurrentSCN.
Can someone help me with this?
== From
http://apache-phoenix-user-list.1124778.n5.nabble.com/Phoenix-4-4-Rename-table-Supported-td1781.html
It is possible to rename a table in Hbase, but it doesn't appear to be
recognized by Phoenix.
I use the approach documented for HBase:
disable 'MySchema.TABLE1'
snapshot 'MySchema.TABLE1', 'MySchema.TABLE1_SNAPSHOT'
clone_snapshot 'MySchema.TABLE1_SNAPSHOT', NewSchema.TABLE1'
delete_snapshot 'MyS
