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 be
Log errors getting Unix UGI
---
Key: HADOOP-6400
URL: https://issues.apache.org/jira/browse/HADOOP-6400
Project: Hadoop Common
Issue Type: Improvement
Components: security
Affects Versions: 0.20.1, 0.21.
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
Looking it the patch it isn't obvious that this port should create any extra
verification effort from the quality standpoint. Thus, it won't delay 0.21
release, IMO.
+1 to back port it.
--
With best regards,
Konstantin Boudnik (aka Cos)
Yahoo! Grid Computing
+1 (408) 34
> 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 reason
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)" > wrote:
Can I build Hadoop on Sun Solaris. The documentation says it is only
supported on Linux, Op
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
[
https://issues.apache.org/jira/browse/HADOOP-6398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved HADOOP-6398.
Resolution: Fixed
Which apparently has been done already according to
http://svn.
[
https://issues.apache.org/jira/browse/HADOOP-6398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley reopened HADOOP-6398:
---
This needs to be fixed in 0.21 and made consistent with map/reduce. Just
changing trunk is not
[
https://issues.apache.org/jira/browse/HADOOP-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Loddengaard resolved HADOOP-4901.
--
Resolution: Fixed
Done. Please reopen if appropriate. Thanks!
Alex
> Upgrade to JU
[
https://issues.apache.org/jira/browse/HADOOP-6398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved HADOOP-6398.
Resolution: Fixed
Fix Version/s: 0.22.0
Thanks for the review Nichilas.
I'
Build is broken after HADOOP-6395 patch has been applied
Key: HADOOP-6398
URL: https://issues.apache.org/jira/browse/HADOOP-6398
Project: Hadoop Common
Issue Type: Bug
Repo
I had to hard code the os name in the build.xml file to get the native
compression codec shared libraries to build for hadoop 19
On Mon, Nov 30, 2009 at 7:09 AM, Daniel Templeton wrote:
> I'm using it on Solaris without any problem. Of course, I'm just using the
> provided JAR files. As long as
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 s
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
15 matches
Mail list logo
