> wrote:
>
> > Thanks Nicolas,
> >
> > When will this file be finalized. Is it time bound? Or it will be always
> > be zero for last one (even if it contains the data)
> >
> > -Original Message-
> > From: Nicolas Liochon [mailto:nkey...@gm
Message-
> From: Nicolas Liochon [mailto:nkey...@gmail.com]
> Sent: Friday, May 17, 2013 4:39 PM
> To: user
> Subject: Re: Doubt Regading HLogs
>
> That's HDFS.
>
> When a file is currently written, the size is not known, as the write is
> in progress. So the namen
Thanks Nicolas,
When will this file be finalized. Is it time bound? Or it will be always be
zero for last one (even if it contains the data)
-Original Message-
From: Nicolas Liochon [mailto:nkey...@gmail.com]
Sent: Friday, May 17, 2013 4:39 PM
To: user
Subject: Re: Doubt Regading HLogs
That's HDFS.
When a file is currently written, the size is not known, as the write is in
progress. So the namenode reports a size of zero (more exactly, it does not
take into account the hdfs block beeing written when it calculates the
size). When you read, you go to the datanode owning the data,
Is it a bug or part of design. It seems more of a design to me. Can someone
guide me through the purpose of this feature.
Thanks
Rishabh
From: Rishabh Agrawal
Sent: Friday, May 17, 2013 4:24 PM
To: user@hbase.apache.org
Subject: Doubt Regading HLogs
Hello,
I am working with Hlogs of Hbase