hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Taylor <jtay...@salesforce.com>
Subject Re: Errors :Undefined table and DoNotRetryIOException while querying from phoenix to hbase
Date Sat, 14 Dec 2013 23:27:23 GMT
Mathan,
We already answered your question on the Phoenix mailing list. If you
have a follow up question, please post it there. This is not an HBase
issue.
Thanks,
James

On Dec 14, 2013, at 2:10 PM, mathan kumar <immathankumar@gmail.com> wrote:

> ---------- Forwarded message ----------
> From: xxxxx <xxxxxxx@gmail.com>
> Date: Sat, Dec 14, 2013 at 10:28 AM
> Subject: Re: Errors :Undefined table and DoNotRetryIOException while
> querying from phoenix to hbase
> To: yyyyy<yyyyy@gmail.com>
>
>
> But I could drop the table in HBase using HBase shell and verified that the
> table is not listed in HBase after that.
> Even now Phoenix could not drop the table and still listing the entry while
> using !tables command.
>
> Where would be the mapping gets stored. Is ter any way to delete the table
> entry from phoenix which may / may not be in HBase.
>
> or else can I map a HBase table with the name "Table1" in HBase to table
> name "Table2" in Phoenix.
>
> coz I found that "Table1" name is freezed to the above said errors in
> Phoenix though the table is available or not available in HBase.
>
>
> On Sat, Dec 14, 2013 at 5:58 AM, yyyyy<yyyy@gmail.com<giacomotaylor@gmail.com>
>> wrote:
>
>> Sounds like an HBase bug. Have you asked on their mailing list?
>>
>> For info and restrictions on mapping an existing HBase table to Phoenix,
>> see here:
>> https://github.com/forcedotcom/phoenix/wiki/Phoenix-Introduction#mapping-to-an-existing-hbase-table
>>
>> Thanks,
>> James
>>
>>
>>
>>
>> On Fri, Dec 13, 2013 at 1:56 PM, xxxx <xxxxxx@gmail.com<immathankumar@gmail.com>
>>> wrote:
>>
>>> 0: jdbc:phoenix:localhost> !tables
>>>
>>> +------------+-------------+------------+------------+------------+------------+---------------------------+----------------+-------------+----------------+
>>> | TABLE_CAT  | TABLE_SCHEM | TABLE_NAME | TABLE_TYPE |  REMARKS   |
>>> TYPE_NAME  | SELF_REFERENCING_COL_NAME | REF_GENERATION | INDEX_STATE |
>>> IMMUTABLE_ROWS |
>>>
>>> +------------+-------------+------------+------------+------------+------------+---------------------------+----------------+-------------+----------------+
>>> | null       | SYSTEM      | TABLE      | SYSTEM TABLE | null       |
>>> null       | null                      | null           | null        |
>>> false         |
>>> | null       | null        | MyTable      | TABLE      | null       |
>>> null       | null                      | null           | null        |
>>> false  |
>>>
>>> +------------+-------------+------------+------------+------------+------------+---------------------------+----------------+-------------+----------------+
>>>
>>>
>>> 0: jdbc:phoenix:localhost> !dropall
>>> Really drop every table in the database? (y/n)abort-drop-all: Aborting
>>> drop all tables.y
>>> Error: ERROR 1012 (42M03): Table undefined. tableName=MyTable (state=
>>> 42M03,code=1012)
>>> Aborting command set because "force" is false and command failed: "DROP
>>> TABLE MyTable;"
>>>
>>>
>>>

Mime
View raw message