Activity

Adding a patch that
1. added BlockTokenIdentifier, removed BlockAccessToken, the new block token (used to be called access token) will just be Token<BlockTokenIdentifier>.
2. Refactored AccessTokenHandler to be BlockTokenSecretManager and added BlockTokenSelector so that a block token can be used for authentication over RPC.
3. Enabled ClientDatanodeProtocol to use block token for authentication.
4. Added authorization checking based on the authenticated BlockTokenIdentifier at Datanode.

Kan Zhang
added a comment - 21/Feb/10 02:43 Adding a patch that
1. added BlockTokenIdentifier, removed BlockAccessToken, the new block token (used to be called access token) will just be Token<BlockTokenIdentifier>.
2. Refactored AccessTokenHandler to be BlockTokenSecretManager and added BlockTokenSelector so that a block token can be used for authentication over RPC.
3. Enabled ClientDatanodeProtocol to use block token for authentication.
4. Added authorization checking based on the authenticated BlockTokenIdentifier at Datanode.

ant run-test-hdfs, all passed, but one TestFiRename.java didn't compile.

compile-fault-inject:
[echo] Start weaving aspects in place
[iajc] error at public class TestRename {
[iajc] ^^^^^^^^^
[iajc] /export/crawlspace/kan/6666/hdfs/trunk/src/test/aop/org/apache/hadoop/fs/TestFiRename.java:50:0::0 The public type TestRename must be defined in its own file
[iajc] MessageHolder: (220 info) (1 error)
[iajc] [error 0]: error at public class TestRename {
[iajc] ^^^^^^^^^
[iajc] /export/crawlspace/kan/6666/hdfs/trunk/src/test/aop/org/apache/hadoop/fs/TestFiRename.java:50:0::0 The public type TestRename must be defined in its own file

ran "ant run-test-hdfs" and passed. But hdfsproxy test fails with the following message.

/Users/kan/6666/hdfs/trunk/build.xml:588: The following error occurred while executing this line:
/Users/kan/6666/hdfs/trunk/build.xml:569: The following error occurred while executing this line:
/Users/kan/6666/hdfs/trunk/src/contrib/build.xml:48: The following error occurred while executing this line:
/Users/kan/6666/hdfs/trunk/src/contrib/hdfsproxy/build.xml:292: org.codehaus.cargo.container.ContainerException: Failed to download [http://apache.osuosl.org/tomcat/tomcat-6/v6.0.18/bin/apache-tomcat-6.0.18.zip]

Kan Zhang
added a comment - 25/Feb/10 23:51 ran "ant run-test-hdfs" and passed. But hdfsproxy test fails with the following message.
/Users/kan/6666/hdfs/trunk/build.xml:588: The following error occurred while executing this line:
/Users/kan/6666/hdfs/trunk/build.xml:569: The following error occurred while executing this line:
/Users/kan/6666/hdfs/trunk/src/contrib/build.xml:48: The following error occurred while executing this line:
/Users/kan/6666/hdfs/trunk/src/contrib/hdfsproxy/build.xml:292: org.codehaus.cargo.container.ContainerException: Failed to download [http: //apache.osuosl.org/tomcat/tomcat-6/v6.0.18/bin/apache-tomcat-6.0.18.zip]

Jitendra Nath Pandey
added a comment - 19/May/10 21:14 Updated patch against the latest trunk.
Tests were run manually. All passed except TestHDFSTrash, which also fails in the latest trunk without this patch.

+1 pending test-patch results. This really should have been split into two parts: one the automatic refactoring done by Eclipse and the other the logic refactoring, to make reviewing easier and the history cleaner.

Jakob Homan
added a comment - 26/May/10 01:28 +1 pending test-patch results. This really should have been split into two parts: one the automatic refactoring done by Eclipse and the other the logic refactoring, to make reviewing easier and the history cleaner.