Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of yuzhihong@gmail.com
 designates 209.85.217.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALr1C9pbDnz91sGnJ=WC6QYpWRP-+b9ZH0iwpQ3pypsbMw+n_A@mail.gmail.com>
References: 
 <CALte62wpnRt=bmu5XugsL4GmY7TtnJToyL+SC6nT=Z5OpsHb1w@mail.gmail.com>
	<1366081212.85695.YahooMailNeo@web140603.mail.bf1.yahoo.com>
	<CALte62yYgQO9bsPXETCcgJ-7WkyryEJiu1WMrvuRhj4d0BfW0Q@mail.gmail.com>
	<CALte62yF56OCrn9ZmhOHW=+=1h2oG47kPG_Lj3Y9__=GzJMxBA@mail.gmail.com>
	<CALr1C9pbDnz91sGnJ=WC6QYpWRP-+b9ZH0iwpQ3pypsbMw+n_A@mail.gmail.com>
Date: Mon, 15 Apr 2013 20:26:36 -0700
Message-ID: 
 <CALte62x-ek2SBM3uLeLNk00q2qis0--K7e7mSebj7RYfO9SxLQ@mail.gmail.com>
Subject: Re: collision in the naming of '.snapshot' directory between hdfs
 snapshot and hbase snapshot
From: Ted Yu <yuzhihong@gmail.com>
To: hdfs-dev@hadoop.apache.org, dev@hbase.apache.org
Content-Type: multipart/alternative; boundary=089e01494232d351e204da71ef3c

--089e01494232d351e204da71ef3c
Content-Type: text/plain; charset=ISO-8859-1

Putting back dev@hbase.

".hbase-sanpshot" would be created at cluster startup. After that user
wouldn't be able to use the same directory name.

On Mon, Apr 15, 2013 at 8:23 PM, Azuryy Yu <azuryyyu@gmail.com> wrote:

> I think ".hbase-sanpshot" is good, but we should also disallow user to
> create ".hbase-sanpshot" under hbase.root sub directories.
>
>
> On Tue, Apr 16, 2013 at 11:18 AM, Ted Yu <yuzhihong@gmail.com> wrote:
>
> > I plan to rename ".sanpshot" in HBase to ".hbase-sanpshot"
> >
> > Please suggest better name in future correspondence.
> >
> > Thanks
> >
> > On Mon, Apr 15, 2013 at 8:12 PM, Ted Yu <yuzhihong@gmail.com> wrote:
> >
> > > Lars:
> > > I will go ahead and log an HBase JIRA, tomorrow morning.
> > >
> > > This hopefully would give people enough time to respond.
> > >
> > > Cheers
> > >
> > >
> > > On Mon, Apr 15, 2013 at 8:00 PM, lars hofhansl <larsh@apache.org>
> wrote:
> > >
> > >> OK. Let's try to fix that quickly, so that I can release HBase 0.94.7.
> > >>
> > >> -- Lars
> > >>
> > >>
> > >>
> > >> ________________________________
> > >>  From: Ted Yu <yuzhihong@gmail.com>
> > >> To: dev@hbase.apache.org; hdfs-dev@hadoop.apache.org
> > >> Sent: Monday, April 15, 2013 7:13 PM
> > >> Subject: collision in the naming of '.snapshot' directory between hdfs
> > >> snapshot and hbase snapshot
> > >>
> > >>
> > >> Hi,
> > >> This afternoon Huned ad I discovered an issue while playing with HBase
> > >> Snapshots on top of Hadoop's Snapshot branch (
> > >> http://svn.apache.org/viewvc/hadoop/common/branches/HDFS-2802/).
> > >>
> > >> HDFS (built from HDFS-2802 branch) doesn't allow paths with .snapshot
> > as a
> > >> component while HBase tries to create paths with .snapshot as a
> > component.
> > >> This leads to issues in HBase, and one of HDFS or HBase needs to give
> up
> > >> the .snapshot reserved keyword. HBase released Snapshots feature in
> > 0.94.6
> > >> (quite recently) and it may not be too late to change HBase to use a
> > >> different path component in an upcoming new release.
> > >>
> > >> In HBase these path names are not user visible. If there is a
> deployment
> > >> of
> > >> 0.94.6, one could provide a migration tool that renames .snapshot to
> > >> .hbase-snapshot or something to be able to move to the Snapshot
> release
> > of
> > >> Hadoop. On the other hand, .snapshot in HDFS is a user visible name
> and
> > is
> > >> a convention that is used by many file systems. It's a matter of
> > >> familiarity with such path names that would help users in using HDFS
> > >> snapshots.
> > >>
> > >> I am including the hdfs-dev in this email. Would appreciate if we
> could
> > >> work together and come up with a solution.
> > >>
> > >> You can find sample output from hdfs command here:
> > >> http://pastebin.com/bBqR4Fvr
> > >>
> > >> Cheers
> > >>
> > >
> > >
> >
>

--089e01494232d351e204da71ef3c--