You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gora.apache.org by "Lewis John McGibbney (Created) (JIRA)" <ji...@apache.org> on 2012/01/21 18:21:40 UTC
[jira] [Created] (GORA-85) Implement "Usage" messages for
SpecificCompiler and LogAnalytics
Implement "Usage" messages for SpecificCompiler and LogAnalytics
----------------------------------------------------------------
Key: GORA-85
URL: https://issues.apache.org/jira/browse/GORA-85
Project: Gora
Issue Type: Improvement
Components: storage
Affects Versions: 0.1.1-incubating, 0.2-incubating
Reporter: Lewis John McGibbney
Fix For: 0.2-incubating
Currently when attempting to run both of the above classes respectively we get the following output
{code}
lewis@lewis-01:~/ASF/gora$ bin/gora specificcompiler
Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 0
at org.apache.avro.specific.SpecificCompiler.main(SpecificCompiler.java:383)
{code}
{code}
lewis@lewis-01:~/ASF/gora$ bin/gora loganalytics
12/01/21 17:16:18 ERROR conf.Configuration: Failed to set setXIncludeAware(true) for parser org.apache.xerces.jaxp.DocumentBuilderFactoryImpl@ca8327:java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null"
java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null"
at javax.xml.parsers.DocumentBuilderFactory.setXIncludeAware(DocumentBuilderFactory.java:590)
at org.apache.hadoop.conf......
huge stack trace
{code}
These classes should implement a "Usage" message as it is currently unclear to people how these classes should be executed and which arguements should be provided as parameters.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GORA-85) Implement "Usage" messages for
SpecificCompiler and LogAnalytics
Posted by "Lewis John McGibbney (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GORA-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lewis John McGibbney updated GORA-85:
-------------------------------------
Fix Version/s: (was: 0.2)
0.3
Bumping to 0.3 as Avro needs to be updated along with Hadoop dependencies, therefore if separate work needs to be contributed to Avro this will hold up this issue significantly.
> Implement "Usage" messages for SpecificCompiler and LogAnalytics
> ----------------------------------------------------------------
>
> Key: GORA-85
> URL: https://issues.apache.org/jira/browse/GORA-85
> Project: Apache Gora
> Issue Type: Improvement
> Components: storage
> Affects Versions: 0.1.1-incubating, 0.2
> Reporter: Lewis John McGibbney
> Fix For: 0.3
>
>
> Currently when attempting to run both of the above classes respectively we get the following output
> {code}
> lewis@lewis-01:~/ASF/gora$ bin/gora specificcompiler
> Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 0
> at org.apache.avro.specific.SpecificCompiler.main(SpecificCompiler.java:383)
> {code}
> {code}
> lewis@lewis-01:~/ASF/gora$ bin/gora loganalytics
> 12/01/21 17:16:18 ERROR conf.Configuration: Failed to set setXIncludeAware(true) for parser org.apache.xerces.jaxp.DocumentBuilderFactoryImpl@ca8327:java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null"
> java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null"
> at javax.xml.parsers.DocumentBuilderFactory.setXIncludeAware(DocumentBuilderFactory.java:590)
> at org.apache.hadoop.conf......
> huge stack trace
> {code}
> These classes should implement a "Usage" message as it is currently unclear to people how these classes should be executed and which arguements should be provided as parameters.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira