Doug Cutting wrote:
Frédéric Bertin wrote:
*// Set the user's name and working directory*
String user = System.getProperty(user.name);
job.setUser(user != null ? user : Dr Who);
if (job.getWorkingDirectory() == null) {
Frédéric Bertin wrote:
This should run clientside, since it depends on the username, which is
different on the server.
then, what about passing the username as a parameter to the
JobSubmissionProtocol.submitJob(...) ? This avoids loading the whole
JobConf clientside just to set the username.
On Aug 31, 2006, at 9:48 AM, Frédéric Bertin wrote:
Doug Cutting wrote:
Frédéric Bertin wrote:
*// Set the user's name and working directory*
String user = System.getProperty(user.name);
job.setUser(user != null ? user : Dr Who);
if
Interesting thread.
This relates to HADOOP-288.
Also the thread I started last week on using URLs in general for
input arguments. Seems like we should just take a URL for the jar,
which could be file: or hdfs:
Thoughts?
On Aug 31, 2006, at 10:54 AM, Doug Cutting wrote:
Frédéric Bertin
Eric Baldeschwieler wrote:
Also the thread I started last week on using URLs in general for input
arguments. Seems like we should just take a URL for the jar, which
could be file: or hdfs:
That would work. The jobclient could automatically copy file: urls to
the jobtracker's native fs.
On URIs:
I had to learn more about URIs while looking at WebDAV code...
I am starting to like them.
Below scheme file: is really for local files
Hadoop Path-s would use scheme hdfs:
Some developers like named pipes.
You can write to an existing named pipe from Java.
But this is not supported
