: Re: Avoid deleting Hbase table when droping table with Phoenix
From: tdsi...@salesforce.com
To: user@phoenix.apache.org
Jose,
hbase-site.xml needs to be on the classpath in order for the config to
get picked up.
Regarding the empty key value see :
https://groups.google.com/forum/#!msg
Jose,
hbase-site.xml needs to be on the classpath in order for the config to
get picked up.
Regarding the empty key value see :
https://groups.google.com/forum/#!msg/phoenix-hbase-user/UWdBghSfePo/BmCxOUOPHn8J
-Thomas
On Mon, Jun 29, 2015 at 4:38 PM, Jose M soloning...@hotmail.com wrote:
Hi,
Hi,
I'm new to Phoenix and trying it right now. I had installed it as Parcel in
Cloudera 5.4.
I'm planning to use it with an already existant Hbase table (other systems use
it and I can't recreate it). I see that I can create it without problem with
the CREATE TABLE command.
But in case I
You can avoid the creation of the empty value and avoid data being dropped
by using the CREATE VIEW command instead of creating a table. Follow the
link that Thomas posted to see some of the trade-offs between a view versus
table. The main one is that a view is read-only and don't support