[jira] [Updated] (HADOOP-10618) Remove SingleNodeSetup.apt.vm

2014-05-18 Thread Akira AJISAKA (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-10618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira AJISAKA updated HADOOP-10618:
---

Status: Patch Available  (was: Open)

> Remove SingleNodeSetup.apt.vm
> -
>
> Key: HADOOP-10618
> URL: https://issues.apache.org/jira/browse/HADOOP-10618
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 2.4.0
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Minor
>  Labels: newbie
> Attachments: HADOOP-10618.patch
>
>
> http://hadoop.apache.org/docs/r2.4.0/hadoop-project-dist/hadoop-common/SingleNodeSetup.html
>  is deprecated and not linked from the left side page.
> We should remove the document and use 
> http://hadoop.apache.org/docs/r2.4.0/hadoop-project-dist/hadoop-common/SingleCluster.html
>  instead.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (HADOOP-10618) Remove SingleNodeSetup.apt.vm

2014-05-18 Thread Akira AJISAKA (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-10618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira AJISAKA updated HADOOP-10618:
---

Attachment: HADOOP-10618.patch

Attaching a patch.

> Remove SingleNodeSetup.apt.vm
> -
>
> Key: HADOOP-10618
> URL: https://issues.apache.org/jira/browse/HADOOP-10618
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 2.4.0
>Reporter: Akira AJISAKA
>Assignee: Akira AJISAKA
>Priority: Minor
>  Labels: newbie
> Attachments: HADOOP-10618.patch
>
>
> http://hadoop.apache.org/docs/r2.4.0/hadoop-project-dist/hadoop-common/SingleNodeSetup.html
>  is deprecated and not linked from the left side page.
> We should remove the document and use 
> http://hadoop.apache.org/docs/r2.4.0/hadoop-project-dist/hadoop-common/SingleCluster.html
>  instead.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (HADOOP-10460) Please update on-line documentation for hadoop 2.3

2014-05-18 Thread Akira AJISAKA (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-10460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira AJISAKA updated HADOOP-10460:
---

Resolution: Invalid
Status: Resolved  (was: Patch Available)

Filed HADOOP-10618 to remove the document. Closing this issue as invalid. If I 
misunderstood, feel free to reopen it.

> Please update on-line documentation for hadoop 2.3
> --
>
> Key: HADOOP-10460
> URL: https://issues.apache.org/jira/browse/HADOOP-10460
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.3.0
> Environment: any
>Reporter: Darek
>Assignee: Akira AJISAKA
>  Labels: newbie
> Attachments: HADOOP-10460.patch
>
>
> Documentation on page:
> http://hadoop.apache.org/docs/r2.3.0/hadoop-project-dist/hadoop-common/SingleNodeSetup.html
> contains steps like:
>  $ cp conf/*.xml input
> but after checked out repository "conf" does not exists (I quess it was moved 
> to etc/hadoop)
> Few lines below in section "Execution" there are steps:
>   $ bin/hadoop namenode -format  - OK
>   $ bin/start-all.sh  - this file has been removed



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (HADOOP-10460) Please update on-line documentation for hadoop 2.3

2014-05-18 Thread Akira AJISAKA (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-10460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira AJISAKA updated HADOOP-10460:
---

Assignee: (was: Akira AJISAKA)

> Please update on-line documentation for hadoop 2.3
> --
>
> Key: HADOOP-10460
> URL: https://issues.apache.org/jira/browse/HADOOP-10460
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 2.3.0
> Environment: any
>Reporter: Darek
>  Labels: newbie
> Attachments: HADOOP-10460.patch
>
>
> Documentation on page:
> http://hadoop.apache.org/docs/r2.3.0/hadoop-project-dist/hadoop-common/SingleNodeSetup.html
> contains steps like:
>  $ cp conf/*.xml input
> but after checked out repository "conf" does not exists (I quess it was moved 
> to etc/hadoop)
> Few lines below in section "Execution" there are steps:
>   $ bin/hadoop namenode -format  - OK
>   $ bin/start-all.sh  - this file has been removed



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (HADOOP-10618) Remove SingleNodeSetup.apt.vm

2014-05-18 Thread Akira AJISAKA (JIRA)
Akira AJISAKA created HADOOP-10618:
--

 Summary: Remove SingleNodeSetup.apt.vm
 Key: HADOOP-10618
 URL: https://issues.apache.org/jira/browse/HADOOP-10618
 Project: Hadoop Common
  Issue Type: Improvement
  Components: documentation
Affects Versions: 2.4.0
Reporter: Akira AJISAKA
Assignee: Akira AJISAKA
Priority: Minor


http://hadoop.apache.org/docs/r2.4.0/hadoop-project-dist/hadoop-common/SingleNodeSetup.html
 is deprecated and not linked from the left side page.
We should remove the document and use 
http://hadoop.apache.org/docs/r2.4.0/hadoop-project-dist/hadoop-common/SingleCluster.html
 instead.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HADOOP-10602) Documentation has broken "Go Back" hyperlinks.

2014-05-18 Thread Akira AJISAKA (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-10602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001384#comment-14001384
 ] 

Akira AJISAKA commented on HADOOP-10602:


Attached a patch to remove all the "Go Back" links.

> Documentation has broken "Go Back" hyperlinks.
> --
>
> Key: HADOOP-10602
> URL: https://issues.apache.org/jira/browse/HADOOP-10602
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 3.0.0, 2.4.0
>Reporter: Chris Nauroth
>Assignee: Akira AJISAKA
>Priority: Trivial
>  Labels: newbie
> Attachments: HADOOP-10602.2.patch, HADOOP-10602.patch
>
>
> Multiple pages of our documentation have "Go Back" links that are broken, 
> because they point to an incorrect relative path.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (HADOOP-10602) Documentation has broken "Go Back" hyperlinks.

2014-05-18 Thread Akira AJISAKA (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-10602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akira AJISAKA updated HADOOP-10602:
---

Attachment: HADOOP-10602.2.patch

> Documentation has broken "Go Back" hyperlinks.
> --
>
> Key: HADOOP-10602
> URL: https://issues.apache.org/jira/browse/HADOOP-10602
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 3.0.0, 2.4.0
>Reporter: Chris Nauroth
>Assignee: Akira AJISAKA
>Priority: Trivial
>  Labels: newbie
> Attachments: HADOOP-10602.2.patch, HADOOP-10602.patch
>
>
> Multiple pages of our documentation have "Go Back" links that are broken, 
> because they point to an incorrect relative path.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HADOOP-10602) Documentation has broken "Go Back" hyperlinks.

2014-05-18 Thread Akira AJISAKA (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-10602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001380#comment-14001380
 ] 

Akira AJISAKA commented on HADOOP-10602:


Thanks [~cnauroth] for the comment. The approach of the v1 patch was to delete 
the only "dead" links.
bq. we have all the direct links in the left nav, and the user always has the 
browser back button too.
Now I agree with you. I'll update the patch to remove all the "Go Back" links.

By the way, removing all the "Go Back" links makes 
hadoop-yarn/hadoop-yarn-site/index.html not linked from anywhere. I think we 
can remove the document because hadoop-yarn/hadoop-yarn-site/YARN.html is a 
superset of it.

> Documentation has broken "Go Back" hyperlinks.
> --
>
> Key: HADOOP-10602
> URL: https://issues.apache.org/jira/browse/HADOOP-10602
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 3.0.0, 2.4.0
>Reporter: Chris Nauroth
>Assignee: Akira AJISAKA
>Priority: Trivial
>  Labels: newbie
> Attachments: HADOOP-10602.patch
>
>
> Multiple pages of our documentation have "Go Back" links that are broken, 
> because they point to an incorrect relative path.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HADOOP-10613) Potential Resource Leaks in FileSystem.CACHE

2014-05-18 Thread Tsz Wo Nicholas Sze (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-10613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001359#comment-14001359
 ] 

Tsz Wo Nicholas Sze commented on HADOOP-10613:
--

> ... If every time i use a new UGI object to invoke FileSystem.get(conf) and 
> never invoke FileSystem's close method,this issue will raise.
 ...

Is it similar to if an application open a lot of (local) files but not closing 
them, or open a lot of sockets but not closing them?  I think the application 
is responsible to call close() for releasing the resource in such cases.

> Potential Resource Leaks in FileSystem.CACHE 
> -
>
> Key: HADOOP-10613
> URL: https://issues.apache.org/jira/browse/HADOOP-10613
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: fs
>Affects Versions: 2.4.0
>Reporter: Nemon Lou
>
> There is no size limit of the hashmap in  FileSystem.CACHE, which can cause a 
> potential memory leak.
> If every time i use a new UGI object to invoke FileSystem.get(conf)  and 
> never invoke FileSystem's close method,this issue will raise.
> If there is a size limit of the hashmap or changing fileSystem instances to 
> soft reference,then user's code don't need to consider too much about the 
> cache leak issues.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (HADOOP-10051) winutil.exe is not included in 2.2.0 bin tarball

2014-05-18 Thread Ali S (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-10051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ali S updated HADOOP-10051:
---

Affects Version/s: 2.4.0

> winutil.exe is not included in 2.2.0 bin tarball
> 
>
> Key: HADOOP-10051
> URL: https://issues.apache.org/jira/browse/HADOOP-10051
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: bin
>Affects Versions: 2.2.0, 2.4.0
>Reporter: Tsuyoshi OZAWA
>
> I don't have Windows environment, but one user who tried 2.2.0 release
> on Windows reported that released tar ball doesn't contain
> "winutil.exe" and cannot run any commands. I confirmed that winutil.exe is 
> not included in 2.2.0 bin tarball surely.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HADOOP-10051) winutil.exe is not included in 2.2.0 bin tarball

2014-05-18 Thread Ali S (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-10051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001347#comment-14001347
 ] 

Ali S commented on HADOOP-10051:


does not seem to be fixed in 2.4 either

> winutil.exe is not included in 2.2.0 bin tarball
> 
>
> Key: HADOOP-10051
> URL: https://issues.apache.org/jira/browse/HADOOP-10051
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: bin
>Affects Versions: 2.2.0, 2.4.0
>Reporter: Tsuyoshi OZAWA
>
> I don't have Windows environment, but one user who tried 2.2.0 release
> on Windows reported that released tar ball doesn't contain
> "winutil.exe" and cannot run any commands. I confirmed that winutil.exe is 
> not included in 2.2.0 bin tarball surely.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HADOOP-10481) Fix new findbugs warnings in hadoop-auth

2014-05-18 Thread Haohui Mai (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-10481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001276#comment-14001276
 ] 

Haohui Mai commented on HADOOP-10481:
-

{code}
+  public String verifyAndExtract(String signedStr, Charset encoding) throws 
SignerException {
+  protected String computeSignature(String str, Charset encoding) {
{code}

It looks to me that these two functions are unnecessary, you can safely assume 
that the code always gets the representation of the UTF-8 string.

> Fix new findbugs warnings in hadoop-auth
> 
>
> Key: HADOOP-10481
> URL: https://issues.apache.org/jira/browse/HADOOP-10481
> Project: Hadoop Common
>  Issue Type: Sub-task
>Reporter: Haohui Mai
>Assignee: Swarnim Kulkarni
>  Labels: newbie
> Attachments: HADOOP-10481.1.patch.txt, HADOOP-10481.2.patch.txt
>
>
> The following findbugs warnings need to be fixed:
> {noformat}
> [INFO] --- findbugs-maven-plugin:2.5.3:check (default-cli) @ hadoop-auth ---
> [INFO] BugInstance size is 2
> [INFO] Error size is 0
> [INFO] Total bugs: 2
> [INFO] Found reliance on default encoding in 
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.init(FilterConfig):
>  String.getBytes() 
> ["org.apache.hadoop.security.authentication.server.AuthenticationFilter"] At 
> AuthenticationFilter.java:[lines 76-455]
> [INFO] Found reliance on default encoding in 
> org.apache.hadoop.security.authentication.util.Signer.computeSignature(String):
>  String.getBytes() ["org.apache.hadoop.security.authentication.util.Signer"] 
> At Signer.java:[lines 34-96]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HADOOP-10474) Move o.a.h.record to hadoop-streaming

2014-05-18 Thread Haohui Mai (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-10474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001169#comment-14001169
 ] 

Haohui Mai commented on HADOOP-10474:
-

I'm okay putting it back to branch-2. I have two related questions:

# What is the effort of fixing it in Hive directly?
# It does not look that this patch can be directly reverted. Is it easier if we 
revert HADOOP-10485 (which actually deletes the classes) in branch-2? Correct 
me if I'm wrong, these classes are for the hadoop-streaming project, and Hive 
has already depended on hadoop-streaming already.

> Move o.a.h.record to hadoop-streaming
> -
>
> Key: HADOOP-10474
> URL: https://issues.apache.org/jira/browse/HADOOP-10474
> Project: Hadoop Common
>  Issue Type: Improvement
>Reporter: Haohui Mai
>Assignee: Haohui Mai
> Fix For: 2.5.0
>
> Attachments: HADOOP-10474.000.patch, HADOOP-10474.001.patch, 
> HADOOP-10474.002.patch
>
>
> The classes in o.a.h.record have been deprecated for more than a year and a 
> half. They should be removed. As the first step, the jira moves all these 
> classes into the hadoop-streaming project, which is the only user of these 
> classes.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HADOOP-10607) Create an API to Separate Credentials/Password Storage from Applications

2014-05-18 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-10607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001149#comment-14001149
 ] 

Hadoop QA commented on HADOOP-10607:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12645438/10607-5.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-common-project/hadoop-common.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/3955//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/3955//console

This message is automatically generated.

> Create an API to Separate Credentials/Password Storage from Applications
> 
>
> Key: HADOOP-10607
> URL: https://issues.apache.org/jira/browse/HADOOP-10607
> Project: Hadoop Common
>  Issue Type: New Feature
>  Components: security
>Reporter: Larry McCay
>Assignee: Larry McCay
> Fix For: 3.0.0
>
> Attachments: 10607-2.patch, 10607-3.patch, 10607-4.patch, 
> 10607-5.patch, 10607.patch
>
>
> As with the filesystem API, we need to provide a generic mechanism to support 
> multiple credential storage mechanisms that are potentially from third 
> parties. 
> We need the ability to eliminate the storage of passwords and secrets in 
> clear text within configuration files or within code.
> Toward that end, I propose an API that is configured using a list of URLs of 
> CredentialProviders. The implementation will look for implementations using 
> the ServiceLoader interface and thus support third party libraries.
> Two providers will be included in this patch. One using the credentials cache 
> in MapReduce jobs and the other using Java KeyStores from either HDFS or 
> local file system. 
> A CredShell CLI will also be included in this patch which provides the 
> ability to manage the credentials within the stores.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (HADOOP-10617) Tests for Crypto input and output streams using fake streams implementing Hadoop streams interfaces.

2014-05-18 Thread Yi Liu (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-10617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yi Liu updated HADOOP-10617:


Description: Tests for Crypto input and output streams using fake input and 
output streams implementing Hadoop streams interfaces. To cover functionality 
of Hadoop streams with crypto.  (was: 1. Test crypto reading with different 
buffer size.
2. Test hflush/hsync of crypto output stream, and with different buffer size.
3. Test positioned read.
4. Test seek to different position.
5. Test get position.
6. Test skip.
7. Test byte buffer read with different buffer size.)

> Tests for Crypto input and output streams using fake streams implementing 
> Hadoop streams interfaces.
> 
>
> Key: HADOOP-10617
> URL: https://issues.apache.org/jira/browse/HADOOP-10617
> Project: Hadoop Common
>  Issue Type: Test
>  Components: security
>Affects Versions: fs-encryption (HADOOP-10150 and HDFS-6134)
>Reporter: Yi Liu
>Assignee: Yi Liu
> Fix For: fs-encryption (HADOOP-10150 and HDFS-6134)
>
>
> Tests for Crypto input and output streams using fake input and output streams 
> implementing Hadoop streams interfaces. To cover functionality of Hadoop 
> streams with crypto.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (HADOOP-10603) Crypto input and output streams implementing Hadoop stream interfaces

2014-05-18 Thread Yi Liu (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-10603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yi Liu updated HADOOP-10603:


Attachment: HADOOP-10603.4.patch

1. Support counter not start from zero.
2. Add javadoc for code.
3. Refine and few bug fix.
The patch is ready for review. Thanks all.

> Crypto input and output streams implementing Hadoop stream interfaces
> -
>
> Key: HADOOP-10603
> URL: https://issues.apache.org/jira/browse/HADOOP-10603
> Project: Hadoop Common
>  Issue Type: Sub-task
>  Components: security
>Affects Versions: fs-encryption (HADOOP-10150 and HDFS-6134)
>Reporter: Alejandro Abdelnur
>Assignee: Yi Liu
> Fix For: fs-encryption (HADOOP-10150 and HDFS-6134)
>
> Attachments: HADOOP-10603.1.patch, HADOOP-10603.2.patch, 
> HADOOP-10603.3.patch, HADOOP-10603.4.patch, HADOOP-10603.patch
>
>
> A common set of Crypto Input/Output streams. They would be used by 
> CryptoFileSystem, HDFS encryption, MapReduce intermediate data and spills. 
> Note we cannot use the JDK Cipher Input/Output streams directly because we 
> need to support the additional interfaces that the Hadoop FileSystem streams 
> implement (Seekable, PositionedReadable, ByteBufferReadable, 
> HasFileDescriptor, CanSetDropBehind, CanSetReadahead, 
> HasEnhancedByteBufferAccess, Syncable, CanSetDropBehind).



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (HADOOP-10617) Tests for Crypto input and output streams using fake streams implementing Hadoop streams interfaces.

2014-05-18 Thread Yi Liu (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-10617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yi Liu updated HADOOP-10617:


Attachment: HADOOP-10617.patch

1. Test crypto reading with different buffer size.
2. Test hflush/hsync of crypto output stream, and with different buffer size.
3. Test positioned read.
4. Test seek to different position.
5. Test get position.
6. Test skip.
7. Test byte buffer read with different buffer size.

> Tests for Crypto input and output streams using fake streams implementing 
> Hadoop streams interfaces.
> 
>
> Key: HADOOP-10617
> URL: https://issues.apache.org/jira/browse/HADOOP-10617
> Project: Hadoop Common
>  Issue Type: Test
>  Components: security
>Affects Versions: fs-encryption (HADOOP-10150 and HDFS-6134)
>Reporter: Yi Liu
>Assignee: Yi Liu
> Fix For: fs-encryption (HADOOP-10150 and HDFS-6134)
>
> Attachments: HADOOP-10617.patch
>
>
> Tests for Crypto input and output streams using fake input and output streams 
> implementing Hadoop streams interfaces. To cover functionality of Hadoop 
> streams with crypto.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (HADOOP-10617) Tests for Crypto input and output streams using fake streams implementing Hadoop streams interfaces.

2014-05-18 Thread Yi Liu (JIRA)
Yi Liu created HADOOP-10617:
---

 Summary: Tests for Crypto input and output streams using fake 
streams implementing Hadoop streams interfaces.
 Key: HADOOP-10617
 URL: https://issues.apache.org/jira/browse/HADOOP-10617
 Project: Hadoop Common
  Issue Type: Test
  Components: security
Affects Versions: fs-encryption (HADOOP-10150 and HDFS-6134)
Reporter: Yi Liu
Assignee: Yi Liu
 Fix For: fs-encryption (HADOOP-10150 and HDFS-6134)


1. Test crypto reading with different buffer size.
2. Test hflush/hsync of crypto output stream, and with different buffer size.
3. Test positioned read.
4. Test seek to different position.
5. Test get position.
6. Test skip.
7. Test byte buffer read with different buffer size.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Work started] (HADOOP-10617) Tests for Crypto input and output streams using fake streams implementing Hadoop streams interfaces.

2014-05-18 Thread Yi Liu (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-10617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on HADOOP-10617 started by Yi Liu.

> Tests for Crypto input and output streams using fake streams implementing 
> Hadoop streams interfaces.
> 
>
> Key: HADOOP-10617
> URL: https://issues.apache.org/jira/browse/HADOOP-10617
> Project: Hadoop Common
>  Issue Type: Sub-task
>  Components: security
>Affects Versions: fs-encryption (HADOOP-10150 and HDFS-6134)
>Reporter: Yi Liu
>Assignee: Yi Liu
> Fix For: fs-encryption (HADOOP-10150 and HDFS-6134)
>
> Attachments: HADOOP-10617.patch
>
>
> Tests for Crypto input and output streams using fake input and output streams 
> implementing Hadoop streams interfaces. To cover functionality of Hadoop 
> streams with crypto.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (HADOOP-10617) Tests for Crypto input and output streams using fake streams implementing Hadoop streams interfaces.

2014-05-18 Thread Yi Liu (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-10617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yi Liu updated HADOOP-10617:


Issue Type: Sub-task  (was: Test)
Parent: HADOOP-10150

> Tests for Crypto input and output streams using fake streams implementing 
> Hadoop streams interfaces.
> 
>
> Key: HADOOP-10617
> URL: https://issues.apache.org/jira/browse/HADOOP-10617
> Project: Hadoop Common
>  Issue Type: Sub-task
>  Components: security
>Affects Versions: fs-encryption (HADOOP-10150 and HDFS-6134)
>Reporter: Yi Liu
>Assignee: Yi Liu
> Fix For: fs-encryption (HADOOP-10150 and HDFS-6134)
>
> Attachments: HADOOP-10617.patch
>
>
> Tests for Crypto input and output streams using fake input and output streams 
> implementing Hadoop streams interfaces. To cover functionality of Hadoop 
> streams with crypto.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HADOOP-10603) Crypto input and output streams implementing Hadoop stream interfaces

2014-05-18 Thread Yi Liu (JIRA)

[ 
https://issues.apache.org/jira/browse/HADOOP-10603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001126#comment-14001126
 ] 

Yi Liu commented on HADOOP-10603:
-

The tests for crypto input and output streams are in HADOOP-10617 and HDFS-6405.

> Crypto input and output streams implementing Hadoop stream interfaces
> -
>
> Key: HADOOP-10603
> URL: https://issues.apache.org/jira/browse/HADOOP-10603
> Project: Hadoop Common
>  Issue Type: Sub-task
>  Components: security
>Affects Versions: fs-encryption (HADOOP-10150 and HDFS-6134)
>Reporter: Alejandro Abdelnur
>Assignee: Yi Liu
> Fix For: fs-encryption (HADOOP-10150 and HDFS-6134)
>
> Attachments: HADOOP-10603.1.patch, HADOOP-10603.2.patch, 
> HADOOP-10603.3.patch, HADOOP-10603.4.patch, HADOOP-10603.patch
>
>
> A common set of Crypto Input/Output streams. They would be used by 
> CryptoFileSystem, HDFS encryption, MapReduce intermediate data and spills. 
> Note we cannot use the JDK Cipher Input/Output streams directly because we 
> need to support the additional interfaces that the Hadoop FileSystem streams 
> implement (Seekable, PositionedReadable, ByteBufferReadable, 
> HasFileDescriptor, CanSetDropBehind, CanSetReadahead, 
> HasEnhancedByteBufferAccess, Syncable, CanSetDropBehind).



--
This message was sent by Atlassian JIRA
(v6.2#6252)