Return-Path: 
 <hdfs-issues-return-40267-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 71B6ECB27
	for <apmail-hadoop-hdfs-issues-archive@minotaur.apache.org>;
 Thu,  3 May 2012 14:59:11 +0000 (UTC)
Received: (qmail 39686 invoked by uid 500); 3 May 2012 14:59:11 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 39647 invoked by uid 500); 3 May 2012 14:59:11 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Reply-To: hdfs-issues@hadoop.apache.org
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 39639 invoked by uid 99); 3 May 2012 14:59:11 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2012 14:59:11 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2012 14:59:10 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 333DC42E77B
	for <hdfs-issues@hadoop.apache.org>; Thu,  3 May 2012 14:58:50 +0000 (UTC)
Date: Thu, 3 May 2012 14:58:50 +0000 (UTC)
From: "Brahma Reddy Battula (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1096961489.22073.1336057130224.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (HDFS-3361) read(long position, byte[] buffer, int
 offset, int length) is not  behaving as expected
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org

Brahma Reddy Battula created HDFS-3361:
------------------------------------------

             Summary: read(long position, byte[] buffer, int offset, int length) is not  behaving as expected
                 Key: HDFS-3361
                 URL: https://issues.apache.org/jira/browse/HDFS-3361
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: hdfs client
    Affects Versions: 2.0.0, 3.0.0
            Reporter: Brahma Reddy Battula
             Fix For: 2.0.0


Start NN and DN
write a file with size 1024
now try to read file using following api
fsin.read(10, writeBuff, 10, fsin.available())

Here it's returning zero..But actual file length is 1024
 
  *Java Docs provided* 
{code}
/**
   * Read bytes from the given position in the stream to the given buffer.
   *
   * @param position  position in the input stream to seek
   * @param buffer    buffer into which data is read
   * @param offset    offset into the buffer in which data is written
   * @param length    maximum number of bytes to read
   * @return total number of bytes read into the buffer, or <code>-1</code>
   *         if there is no more data because the end of the stream has been
   *         reached
   */
  public int read(long position, byte[] buffer, int offset, int length)
    throws IOException {
    return ((PositionedReadable)in).read(position, buffer, offset, length);
  }
{code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira