Re: stable version

2009-02-16 Thread Steve Loughran

Anum Ali wrote:

The parser problem is related to jar files , can be resolved not a bug.

Forwarding link for its solution


http://www.jroller.com/navanee/entry/unsupportedoperationexception_this_parser_does_not



this site is  down; cant see it

It is a bug, because I view all operations problems as defects to be 
opened in the bug tracker, stack traces stuck in, the problem resolved. 
That's software or hardware -because that issue DB is your searchable 
history of what went wrong. Given on my system I was seeing a 
ClassNotFoundException for loading FSConstants, there was no easy way to 
work out what went wrong, and its cost me a couple of days work.


furthermore, in the OSS world, every person who can't get your app to 
work is either going to walk away unhappy (=lost customer, lost 
developer and risk they compete with you), or they are going to get on 
the email list and ask questions, questions which may get answered, but 
it will cost them time.


Hence
* happyaxis.jsp: axis' diagnostics page, prints out useful stuff and 
warns if it knows it is unwell (and returns 500 error code so your 
monitoring tools can recognise this)
* ant -diagnostics: detailed look at your ant system including xml 
parser experiments.


Good open source tools have to be easy for people to get started with, 
and that means helpful error messages. If we left the code alone, 
knowing that the cause of a ClassNotFoundException was the fault of the 
user sticking the wrong XML parser on the classpath -and yet refusing to 
add the four lines of code needed to handle this- then we are letting 
down the users





On 2/13/09, Steve Loughran ste...@apache.org wrote:

Anum Ali wrote:

 This only occurs in linux , in windows its  fine.

do a java -version for me, and an ant -diagnostics, stick both on the bugrep

https://issues.apache.org/jira/browse/HADOOP-5254

It may be that XInclude only went live in java1.6u5; I'm running a
JRockit JVM which predates that and I'm seeing it (linux again);

I will also try sticking xerces on the classpath to see what happens next





Re: stable version

2009-02-16 Thread Anum Ali
That's awkward , the site went down!

and ok, I note these points ,for future.


Thanks.




On 2/16/09, Steve Loughran ste...@apache.org wrote:
 Anum Ali wrote:
 The parser problem is related to jar files , can be resolved not a bug.

 Forwarding link for its solution


 http://www.jroller.com/navanee/entry/unsupportedoperationexception_this_parser_does_not


 this site is  down; cant see it

 It is a bug, because I view all operations problems as defects to be
 opened in the bug tracker, stack traces stuck in, the problem resolved.
 That's software or hardware -because that issue DB is your searchable
 history of what went wrong. Given on my system I was seeing a
 ClassNotFoundException for loading FSConstants, there was no easy way to
 work out what went wrong, and its cost me a couple of days work.

 furthermore, in the OSS world, every person who can't get your app to
 work is either going to walk away unhappy (=lost customer, lost
 developer and risk they compete with you), or they are going to get on
 the email list and ask questions, questions which may get answered, but
 it will cost them time.

 Hence
 * happyaxis.jsp: axis' diagnostics page, prints out useful stuff and
 warns if it knows it is unwell (and returns 500 error code so your
 monitoring tools can recognise this)
 * ant -diagnostics: detailed look at your ant system including xml
 parser experiments.

 Good open source tools have to be easy for people to get started with,
 and that means helpful error messages. If we left the code alone,
 knowing that the cause of a ClassNotFoundException was the fault of the
 user sticking the wrong XML parser on the classpath -and yet refusing to
 add the four lines of code needed to handle this- then we are letting
 down the users



 On 2/13/09, Steve Loughran ste...@apache.org wrote:
 Anum Ali wrote:
  This only occurs in linux , in windows its  fine.
 do a java -version for me, and an ant -diagnostics, stick both on the
 bugrep

 https://issues.apache.org/jira/browse/HADOOP-5254

 It may be that XInclude only went live in java1.6u5; I'm running a
 JRockit JVM which predates that and I'm seeing it (linux again);

 I will also try sticking xerces on the classpath to see what happens next





Re: stable version

2009-02-13 Thread Steve Loughran

Anum Ali wrote:

yes


On Thu, Feb 12, 2009 at 4:33 PM, Steve Loughran ste...@apache.org wrote:


Anum Ali wrote:


Iam working on Hadoop SVN version 0.21.0-dev. Having some problems ,
regarding running its examples/file from eclipse.


It gives error for

Exception in thread main java.lang.UnsupportedOperationException: This
parser does not support specification null version null  at

javax.xml.parsers.DocumentBuilderFactory.setXIncludeAware(DocumentBuilderFactory.java:590)

Can anyone reslove or give some idea about it.



You are using Java6, correct?






I'm seeing this too, filed the bug

https://issues.apache.org/jira/browse/HADOOP-5254

Any stack traces you can add on will help. Probable cause is 
https://issues.apache.org/jira/browse/HADOOP-4944


Re: stable version

2009-02-13 Thread Anum Ali
 This only occurs in linux , in windows its  fine.




On Fri, Feb 13, 2009 at 7:11 AM, Steve Loughran ste...@apache.org wrote:

  Anum Ali wrote:

 yes


 On Thu, Feb 12, 2009 at 4:33 PM, Steve Loughran ste...@apache.org
 wrote:

 Anum Ali wrote:

 Iam working on Hadoop SVN version 0.21.0-dev. Having some problems ,
 regarding running its examples/file from eclipse.


 It gives error for

 Exception in thread main java.lang.UnsupportedOperationException: This
 parser does not support specification null version null  at


 javax.xml.parsers.DocumentBuilderFactory.setXIncludeAware(DocumentBuilderFactory.java:590)

 Can anyone reslove or give some idea about it.


 You are using Java6, correct?




 I'm seeing this too, filed the bug

 https://issues.apache.org/jira/browse/HADOOP-5254

 Any stack traces you can add on will help. Probable cause is
 https://issues.apache.org/jira/browse/HADOOP-4944



Re: stable version

2009-02-13 Thread Steve Loughran

Anum Ali wrote:

 This only occurs in linux , in windows its  fine.


do a java -version for me, and an ant -diagnostics, stick both on the bugrep

https://issues.apache.org/jira/browse/HADOOP-5254

It may be that XInclude only went live in java1.6u5; I'm running a 
JRockit JVM which predates that and I'm seeing it (linux again);


I will also try sticking xerces on the classpath to see what happens next


Re: stable version

2009-02-13 Thread Anum Ali
The parser problem is related to jar files , can be resolved not a bug.

Forwarding link for its solution


http://www.jroller.com/navanee/entry/unsupportedoperationexception_this_parser_does_not



On 2/13/09, Steve Loughran ste...@apache.org wrote:
 Anum Ali wrote:
  This only occurs in linux , in windows its  fine.

 do a java -version for me, and an ant -diagnostics, stick both on the bugrep

 https://issues.apache.org/jira/browse/HADOOP-5254

 It may be that XInclude only went live in java1.6u5; I'm running a
 JRockit JVM which predates that and I'm seeing it (linux again);

 I will also try sticking xerces on the classpath to see what happens next



Re: stable version

2009-02-12 Thread Anum Ali
Iam working on Hadoop SVN version 0.21.0-dev. Having some problems ,
regarding running its examples/file from eclipse.


It gives error for

Exception in thread main java.lang.UnsupportedOperationException: This
parser does not support specification null version null  at
javax.xml.parsers.DocumentBuilderFactory.setXIncludeAware(DocumentBuilderFactory.java:590)

Can anyone reslove or give some idea about it.



Thanks.

2009/2/12 Raghu Angadi rang...@yahoo-inc.com

 Vadim Zaliva wrote:

 The particular problem I am having is this one:

 https://issues.apache.org/jira/browse/HADOOP-2669

 I am observing it in version 19. Could anybody confirm that
 it have been fixed in 18, as Jira claims?

 I am wondering why bug fix for this problem might have been committed
 to 18 branch but not 19. If it was commited to both, then perhaps the
 problem was not completely solved and downgrading to 18 will not help
 me.


 If you read through the comments, it will see that the the root cause was
 never found. The patch just fixes one of the suspects. If you are still
 seeing this, please file another jira and link it HADOOP-2669.

 How easy is it for you reproduce this? I guess one of the reasons for
 incomplete diagnosis is that it is not simple to reproduce.

 Raghu.


  Vadim

 On Wed, Feb 11, 2009 at 00:48, Rasit OZDAS rasitoz...@gmail.com wrote:

 Yes, version 18.3 is the most stable one. It has added patches,
 without not-proven new functionality.

 2009/2/11 Owen O'Malley omal...@apache.org:

 On Feb 10, 2009, at 7:21 PM, Vadim Zaliva wrote:

  Maybe version 0.18
 is better suited for production environment?

 Yahoo is mostly on 0.18.3 + some patches at this point.

 -- Owen



 --
 M. Raşit ÖZDAŞ





Re: stable version

2009-02-12 Thread Steve Loughran

Anum Ali wrote:

Iam working on Hadoop SVN version 0.21.0-dev. Having some problems ,
regarding running its examples/file from eclipse.


It gives error for

Exception in thread main java.lang.UnsupportedOperationException: This
parser does not support specification null version null  at
javax.xml.parsers.DocumentBuilderFactory.setXIncludeAware(DocumentBuilderFactory.java:590)

Can anyone reslove or give some idea about it.




You are using Java6, correct?


Re: stable version

2009-02-12 Thread Anum Ali
yes


On Thu, Feb 12, 2009 at 4:33 PM, Steve Loughran ste...@apache.org wrote:

 Anum Ali wrote:

 Iam working on Hadoop SVN version 0.21.0-dev. Having some problems ,
 regarding running its examples/file from eclipse.


 It gives error for

 Exception in thread main java.lang.UnsupportedOperationException: This
 parser does not support specification null version null  at

 javax.xml.parsers.DocumentBuilderFactory.setXIncludeAware(DocumentBuilderFactory.java:590)

 Can anyone reslove or give some idea about it.



 You are using Java6, correct?



Re: stable version

2009-02-12 Thread Steve Loughran

Anum Ali wrote:

yes


On Thu, Feb 12, 2009 at 4:33 PM, Steve Loughran ste...@apache.org wrote:


Anum Ali wrote:


Iam working on Hadoop SVN version 0.21.0-dev. Having some problems ,
regarding running its examples/file from eclipse.


It gives error for

Exception in thread main java.lang.UnsupportedOperationException: This
parser does not support specification null version null  at

javax.xml.parsers.DocumentBuilderFactory.setXIncludeAware(DocumentBuilderFactory.java:590)

Can anyone reslove or give some idea about it.



You are using Java6, correct?





well, in that case something being passed down to setXIncludeAware may 
be picked up as invalid. More of a stack trace may help. Otherwise, now 
is your chance to learn your way around the hadoop codebase, and ensure 
that when the next version ships, your most pressing bugs have been fixed


Re: stable version

2009-02-11 Thread Rasit OZDAS
Yes, version 18.3 is the most stable one. It has added patches,
without not-proven new functionality.

2009/2/11 Owen O'Malley omal...@apache.org:

 On Feb 10, 2009, at 7:21 PM, Vadim Zaliva wrote:

 Maybe version 0.18
 is better suited for production environment?

 Yahoo is mostly on 0.18.3 + some patches at this point.

 -- Owen




-- 
M. Raşit ÖZDAŞ


Re: stable version

2009-02-11 Thread Vadim Zaliva
The particular problem I am having is this one:

https://issues.apache.org/jira/browse/HADOOP-2669

I am observing it in version 19. Could anybody confirm that
it have been fixed in 18, as Jira claims?

I am wondering why bug fix for this problem might have been committed
to 18 branch but not 19. If it was commited to both, then perhaps the
problem was not completely solved and downgrading to 18 will not help
me.

Vadim

On Wed, Feb 11, 2009 at 00:48, Rasit OZDAS rasitoz...@gmail.com wrote:
 Yes, version 18.3 is the most stable one. It has added patches,
 without not-proven new functionality.

 2009/2/11 Owen O'Malley omal...@apache.org:

 On Feb 10, 2009, at 7:21 PM, Vadim Zaliva wrote:

 Maybe version 0.18
 is better suited for production environment?

 Yahoo is mostly on 0.18.3 + some patches at this point.

 -- Owen




 --
 M. Raşit ÖZDAŞ



Re: stable version

2009-02-11 Thread Raghu Angadi

Vadim Zaliva wrote:

The particular problem I am having is this one:

https://issues.apache.org/jira/browse/HADOOP-2669

I am observing it in version 19. Could anybody confirm that
it have been fixed in 18, as Jira claims?

I am wondering why bug fix for this problem might have been committed
to 18 branch but not 19. If it was commited to both, then perhaps the
problem was not completely solved and downgrading to 18 will not help
me.


If you read through the comments, it will see that the the root cause 
was never found. The patch just fixes one of the suspects. If you are 
still seeing this, please file another jira and link it HADOOP-2669.


How easy is it for you reproduce this? I guess one of the reasons for 
incomplete diagnosis is that it is not simple to reproduce.


Raghu.


Vadim

On Wed, Feb 11, 2009 at 00:48, Rasit OZDAS rasitoz...@gmail.com wrote:

Yes, version 18.3 is the most stable one. It has added patches,
without not-proven new functionality.

2009/2/11 Owen O'Malley omal...@apache.org:

On Feb 10, 2009, at 7:21 PM, Vadim Zaliva wrote:


Maybe version 0.18
is better suited for production environment?

Yahoo is mostly on 0.18.3 + some patches at this point.

-- Owen




--
M. Raşit ÖZDAŞ





stable version

2009-02-10 Thread Vadim Zaliva
Hi!

Kind of novice question, but I need to know, what Hadoop version is
considered stable. I was
trying to run version 0.19, and I've seen numerous stability issues
with it. Maybe version 0.18
is better suited for production environment?

Vadim


Most stable version of Hadoop

2008-12-16 Thread Sandeep Dhawan, Noida
DISCLAIMER:
---
The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. 
It shall not attach any liability on the originator or HCL or its affiliates. 
Any views or opinions presented in 
this email are solely those of the author and may not necessarily reflect the 
opinions of HCL or its affiliates. 
Any form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of 
this message without the prior written consent of the author of this e-mail is 
strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any mail and 
attachments please check them for viruses and defect.
---