Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of jim@powerset.com designates
 207.5.72.95 as permitted sender)
From: Jim Kellerman <jim@powerset.com>
To: "hbase-dev@hadoop.apache.org" <hbase-dev@hadoop.apache.org>
Date: Mon, 3 Mar 2008 19:00:56 -0800
Subject: RE: Renaming the table.
Thread-Topic: Renaming the table.
Thread-Index: Ach9jde5Bjbi9hLyTlSQIxB0bHWasQAFfm5g
Message-ID: 
 <84E2AE771361E9419DD0EFBD31F09C4D4F47C88F47@EXVMBX015-1.exch015.msoutlookonline.net>
References: <eb4706e0803022156y7bcd3ffdl2b16d66148cd8827@mail.gmail.com>
 <EC52E829-71EF-4449-9385-1B6A703334C0@rapleaf.com>
 <eb4706e0803031558w7658c73cqc6af517ea757b4f2@mail.gmail.com>
 <BAC681C3-3B36-466D-BB18-5AABEAA68E72@rapleaf.com>
In-Reply-To: <BAC681C3-3B36-466D-BB18-5AABEAA68E72@rapleaf.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="windows-1250"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

+1 Bryan. In the future, we need to be able to recover HBase entirely from =
the file system
without either the META or ROOT region's help since they may be corrupted.

---
Jim Kellerman, Senior Engineer; Powerset


> -----Original Message-----
> From: Bryan Duxbury [mailto:bryan@rapleaf.com]
> Sent: Monday, March 03, 2008 4:22 PM
> To: hbase-dev@hadoop.apache.org
> Subject: Re: Renaming the table.
>
> I'm not sure I understand. Do you mean you'd maintain a
> mapping between the old, actual table name and the new,
> logical table name? I don't really like that idea. It sounds
> like it would add a ton of failure cases and complexity to
> the system. We need tables to stay in a really consistent
> state so that we can have as much data reliability as possible.
>
> -Bryan
>
> On Mar 3, 2008, at 3:58 PM, edward yoon wrote:
>
> >> We'd need to add a new table operation for renaming a table
> >> internally. The ugly part is that we'd have to rewrite
> every row for
> >> the table in META to do this.
> >
> > In fact, i thought a physical/logical table name management for
> > high-performance without no changing the meta data.
> >
> > On 3/4/08, Bryan Duxbury <bryan@rapleaf.com> wrote:
> >> We'd need to add a new table operation for renaming a table
> >> internally. The ugly part is that we'd have to rewrite
> every row for
> >> the table in META to do this.
> >>
> >>  The SQL way to do this would be "ALTER TABLE table RENAME
> new name".
> >>  However, that's a bit verbose, so I think "RENAME table TO
> >> new_table"
> >>  would be fine.
> >>
> >>
> >>  -Bryan
> >>
> >>
> >>  On Mar 2, 2008, at 9:56 PM, edward yoon wrote:
> >>
> >>> A renaming function of table alteration is needed.
> >>> Is there a tool for renaming the table?
> >>>
> >>> Any ideas please post back.
> >>> Also, i'd like to add renaming syntax to hql as describe below.
> >>>
> >>> hql > RENAMING table_name TO new_table_name;
> >>>
> >>> What do you think?
> >>> --
> >>> B. Regards,
> >>> Edward yoon @ NHN, corp.
> >>
> >>
> >
> >
> > --
> > B. Regards,
> > Edward yoon @ NHN, corp.
>
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.516 / Virus Database: 269.21.3/1308 - Release
> Date: 3/3/2008 10:01 AM
>
>

No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.21.3/1308 - Release Date: 3/3/2008 1=
0:01 AM