Hadoop on Sun Solaris
Can I build Hadoop on Sun Solaris. The documentation says it is only supported on Linux, Open Solaris and on Windows for Dev purposes. I want to build a prototype on Hadoop on our existing OS which is Sun Solaris. This is purely for proto-typing purposes only. As Hadoop is completely written in Java, I think I can install on Hadoop. Please advise. Thanks, Rajendra
Re: Hadoop on Sun Solaris
I'm using it on Solaris without any problem. Of course, I'm just using the provided JAR files. As long as you have all the right pieces, e.g. ant, javac, the libraries, you should be able to build. Daniel Palikala, Rajendra (CCL) wrote: Can I build Hadoop on Sun Solaris. The documentation says it is only supported on Linux, Open Solaris and on Windows for Dev purposes. I want to build a prototype on Hadoop on our existing OS which is Sun Solaris. This is purely for proto-typing purposes only. As Hadoop is completely written in Java, I think I can install on Hadoop. Please advise. Thanks, Rajendra
Re: Hadoop coding style guideline
Aaron Kimball wrote:
First, I've been picked on by others for using this brace style:
if (foo) {
stmt;
} else {
otherstmt;
}
and have been told to drop the braces because they look ugly if stmt or
otherstmt are only one line.
In http://java.sun.com/docs/codeconv/html/CodeConventions.doc6.html#449though,
the sun coding conventions *clearly* say that braces are always to
be used. Can we get a ruling here?
My preference is to permit both. I like to maximize the amount of
readable logic per screen, and find that close braces around one-line
expressions don't improve readability (since indentation already
indicates the nesting) and decrease the amount of per-screen logic.
However I know reasonable people who prefer to always fully-bracket
their code. I see no strong reason to force one style over the other.
And second, what's our story on tabs vs. spaces?
Spaces are preferred, since tabs are inconsistently interpreted. The
correct interpretation of a tab is to move to the next column evenly
divisible by 8, but many editors are configured differently, so tabs are
best avoided.
Doug
Re: Hadoop on Sun Solaris
Rajendra, Hadoop works fine on solaris. We have had it in production on solaris for a number of months now. Good luck! Best, Jochen On Nov 30, 2009, at 6:56, Palikala, Rajendra (CCL) rpalik...@carnival.com wrote: Can I build Hadoop on Sun Solaris. The documentation says it is only supported on Linux, Open Solaris and on Windows for Dev purposes. I want to build a prototype on Hadoop on our existing OS which is Sun Solaris. This is purely for proto-typing purposes only. As Hadoop is completely written in Java, I think I can install on Hadoop. Please advise. Thanks, Rajendra
Re: Hadoop coding style guideline
My preference is to permit both. I like to maximize the amount of readable logic per screen, and find that close braces around one-line expressions don't improve readability (since indentation already indicates the nesting) and decrease the amount of per-screen logic. However I know reasonable people who prefer to always fully-bracket their code. I see no strong reason to force one style over the other. I see a couple benefits to choosing one and being consistent: consistency makes code more readable (the main motivation for a style guide) and works well with automated tools (eg would be nice if checkstyle didn't generate huge diffs). Would also be nice to follow the Sun convention since that's what Hadoop claims it does. Thanks, Eli
[jira] Created: (HADOOP-6399) Specify a policy to defines test placements into categories: unit, functional, system, etc.
Specify a policy to defines test placements into categories: unit, functional, system, etc. --- Key: HADOOP-6399 URL: https://issues.apache.org/jira/browse/HADOOP-6399 Project: Hadoop Common Issue Type: Improvement Components: test Reporter: Konstantin Boudnik A clear guidelines are needed to define which tests are true unit tests, which are functional, systems, et cetera. Otherwise it isn't obvious to everybody why certain decisions (i.e. why this test is a unit test?) are made. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Hadoop coding style guideline
I have to weigh in strongly on the pro-braces side. I've seen too many
instances (not necessarily in Hadoop) where there was something like:
if (foo)
stmt;
otherstmt;
It's not about readability. It's about maintainability.
Daniel
Doug Cutting wrote:
Aaron Kimball wrote:
First, I've been picked on by others for using this brace style:
if (foo) {
stmt;
} else {
otherstmt;
}
and have been told to drop the braces because they look ugly if
stmt or
otherstmt are only one line.
In
http://java.sun.com/docs/codeconv/html/CodeConventions.doc6.html#449though,
the sun coding conventions *clearly* say that braces are always to
be used. Can we get a ruling here?
My preference is to permit both. I like to maximize the amount of
readable logic per screen, and find that close braces around one-line
expressions don't improve readability (since indentation already
indicates the nesting) and decrease the amount of per-screen logic.
However I know reasonable people who prefer to always fully-bracket
their code. I see no strong reason to force one style over the other.
And second, what's our story on tabs vs. spaces?
Spaces are preferred, since tabs are inconsistently interpreted. The
correct interpretation of a tab is to move to the next column evenly
divisible by 8, but many editors are configured differently, so tabs
are best avoided.
Doug
