When compiling source against the latest trunk in common repository,
it throws fop exception, I can't found where to add this lib e.g fop
v1.0. Any config file needed to be altered so that the compilation
would work?
Thanks.
[exec] Exception in thread "main" java.lang.NoClassDefFoundError:
o
Use of TestingGroups by tests causes subsequent tests to fail
-
Key: HADOOP-7389
URL: https://issues.apache.org/jira/browse/HADOOP-7389
Project: Hadoop Common
Issue Type: Bug
Remove definition of HADOOP_HOME and HADOOP_PREFIX from hadoop-env.sh.template
--
Key: HADOOP-7388
URL: https://issues.apache.org/jira/browse/HADOOP-7388
Project: Hadoop Commo
Change rpm to ignore configuration files when uninstalling
--
Key: HADOOP-7387
URL: https://issues.apache.org/jira/browse/HADOOP-7387
Project: Hadoop Common
Issue Type: Improvement
Support concatenated bzip2 files
Key: HADOOP-7386
URL: https://issues.apache.org/jira/browse/HADOOP-7386
Project: Hadoop Common
Issue Type: Improvement
Reporter: Allen Wittenauer
HADOOP-6835 add
On Jun 13, 2011, at 2:24 PM, Chris Douglas wrote:
> Yes to both. I haven't tested the concat bzip2 support, but I've heard
> it's broken. The commit log and release note for the issue are correct
> on HADOOP-6835.
OK, thanks. I was looking for a double-check in case I missed
something
Yes to both. I haven't tested the concat bzip2 support, but I've heard
it's broken. The commit log and release note for the issue are correct
on HADOOP-6835.
You'll make me regret saying this, but always feel free to edit JIRA
titles that don't accurately reflect the content of the issue. -C
On M
Am I correct in thinking that we should:
a) change the description of this JIRA to just say gzip?
b) file a new JIRA to add bzip2 concat support?
Right now, it seems a bit misleading
> On 2011-06-13 18:23:35, Matt Foley wrote:
> > Sorry if this is out of context, but is it really best to also return a
> > null here? Shouldn't it check for null result from getSerialization(),
> > then throw a (non-NPE) exception? Or do you prefer to do that check and
> > throw at a higher
> On 2011-06-13 18:23:35, Matt Foley wrote:
> > Sorry if this is out of context, but is it really best to also return a
> > null here? Shouldn't it check for null result from getSerialization(),
> > then throw a (non-NPE) exception? Or do you prefer to do that check and
> > throw at a higher
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/884/#review817
---
Sorry if this is out of context, but is it really best to also return a
Remove StringUtils.stringifyException(ie) in logger functions
-
Key: HADOOP-7385
URL: https://issues.apache.org/jira/browse/HADOOP-7385
Project: Hadoop Common
Issue Type: Bug
Af
12 matches
Mail list logo