I've discovered that i can simple delete schema
Like this:
delete from SYSTEM.CATALOG where "TABLE_NAME" = 'my_table_name';
Is this action has any consequence?
> On 16 Jan 2017, at 19:51, Josh Elser wrote:
>
> You could create a new table with the same schema and then
I've created a secondary index on my table
create index "test_index" on "sources"("column1") async;
And I'd like to kick off the map reduce job to populate said index.
However, when I run the following command:
./hbase org.apache.phoenix.mapreduce.index.IndexTool --data-table
sources
Couple of other options:
1) connect with a CURRENT_SCN [1] earlier than any timestamp for your data.
For example, if you know you created the table a month ago, then use an SCN
value of the epoch time for 1/1/2016. Then issue the DROP TABLE command
from that connection and no data will be removed.
Phoenix's grammar is documented at
http://phoenix.apache.org/language/index.html
Cheyenne Forbes wrote:
Can I use the SQL WITH clause Phoenix instead of "untidy" sub queries?
You could create a new table with the same schema and then flip the
underlying table out.
* Rename the existing table to "foo"
* Create your table via Phoenix with correct schema and desired name
* Delete underlying HBase table that Phoenix created
* Rename "foo" to the desired name
I _think_
Did you check the RegionServers logs I asked in the last message?
Chetan Khatri wrote:
Any updates for the above error guys ?
On Fri, Jan 13, 2017 at 9:35 PM, Josh Elser > wrote:
(-cc dev@phoenix)
phoenix-4.8.2-HBase-1.2-server.jar in the
Can I use the SQL WITH clause Phoenix instead of "untidy" sub queries?
Hello,
I've recreated HBase table with data, but phoenix doesn't work on it. But i
still see this table in phoenix.
How can I recreate pheonix table now?
As I know "drop table ... ; create table ..." in phoenix will destroy my HBase
table with data.