StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POSet hadoop system user for client embedded in Java webapp
primarykey
Id
11041253
data
AcceptedAnswerId
11062529
AnswerCount
3
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-06-14T20:59:13.250
FavoriteCount
8
LastActivityDate
2014-01-30T16:38:41.630
LastEditDate
2012-06-16T10:12:26.577
LastEditorUserId
51016
OwnerUserId
51016
ParentId
0
PostTypeId
1
Score
26
ViewCount
26317
LastEditorDisplayName
text
Body
I would like to submit MapReduce jobs from a java web application to a remote Hadoop cluster but am unable to specify which user the job should be submitted for. I would like to configure and use a system user which should be used for all MapReduce jobs. Currently I am unable to specify any user and no matter what the hadoop job runs under the username of the currently logged in user of the client system. This causes an error with the message <pre><code>Permission denied: user=alice, access=WRITE, inode="staging":hduser:supergroup:rwxr-xr-x </code></pre> ... where "alice" is the local, logged in user on the client machine. I have tried <ol> <li>various combinations of creating <code>UserGroupInformation</code> instances (both proxies and normal user) and</li> <li>setting the Java System property with <code>-Duser.name=hduser</code>, changing the <code>USER</code> envar and as a hard coded <code>System.setProperty("user.name", "hduser")</code> call.</li> </ol> ... to no avail. Regarding 1) I admit to having no clue on how these classes are supposed to be used. Also please note that changing the Java System property is obviously not a real solution for use in the web application. Does any body know how you specify which user Hadoop uses to connect to a remote system? PS/ Hadoop is using the default configuration meaning that no authentication is used when connecting to the cluster and that Kerberos is not used in communicating with the remote machines.
Tags
<hadoop><cluster-computing>
Title
Set hadoop system user for client embedded in Java webapp
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USChristoffer Soop
UserOwnerUserId
1. USChristoffer Soop
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POSet hadoop system user for client embedded in Java webapp
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POSet hadoop system user for client embedded in Java webapp
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POSet hadoop system user for client embedded in Java webapp
 UserUserId
 USpensz
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.