[
https://issues.apache.org/jira/browse/PIG-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853603#action_12853603
]
Alan Gates commented on PIG-1331:
---------------------------------
Given that hudson can't apply this patch (because it's a .tgz file) I've run
the parts of the patch test manually. There are issues with ant test, javadoc,
and findbugs.
When I try to do "ant test" I get:
{code}
war:
[war] Building war:
/home/gates/src/pig/owl/trunk/contrib/owl/build/owl-0.8.0-dev.war
jetty-stop:
BUILD FAILED
/home/gates/src/pig/owl/trunk/contrib/owl/build.xml:908: Execute failed:
java.io.IOException: Cannot run program
"/home/gates/src/pig/owl/trunk/contrib/owl/ci//jetty_stop.sh":
java.io.IOException: error=13, Permission denied
{code}
I see ten warnings when I build. These are all in the parser so it looks like
they're ok.
javadoc generates five warnings, which need to be addressed.
findbugs generates one warning:
{code}
Se org.apache.hadoop.owl.protocol.OwlSchema$OwlColumnSchemaComparable
implements Comparator but not Serializable
Bug type SE_COMPARATOR_SHOULD_BE_SERIALIZABLE (click for details)
In class org.apache.hadoop.owl.protocol.OwlSchema$OwlColumnSchemaComparable
At OwlSchema.java:[lines 180-185]
Details
SE_COMPARATOR_SHOULD_BE_SERIALIZABLE: Comparator doesn't implement Serializable
This class implements the Comparator interface. You should consider whether or
not it should also implement the Serializable interface. If a comparator is
used to construct an ordered collection such as a TreeMap, then the TreeMap
will be serializable only if the comparator is also serializable. As most
comparators have little or no state, making them serializable is generally easy
and good defensive programming.
{code}
Rat only complains about files produced by javacc, so that should be fine.
> Owl Hadoop Table Management Service
> -----------------------------------
>
> Key: PIG-1331
> URL: https://issues.apache.org/jira/browse/PIG-1331
> Project: Pig
> Issue Type: New Feature
> Affects Versions: 0.8.0
> Reporter: Jay Tang
> Attachments: build.log, ivy_version.patch, owl.contrib.3.tgz
>
>
> This JIRA is a proposal to create a Hadoop table management service: Owl.
> Today, MapReduce and Pig applications interacts directly with HDFS
> directories and files and must deal with low level data management issues
> such as storage format, serialization/compression schemes, data layout, and
> efficient data accesses, etc, often with different solutions. Owl aims to
> provide a standard way to addresses this issue and abstracts away the
> complexities of reading/writing huge amount of data from/to HDFS.
> Owl has a data access API that is modeled after the traditional Hadoop
> !InputFormt and a management API to manipulate Owl objects. This JIRA is
> related to Pig-823 (Hadoop Metadata Service) as Owl has an internal metadata
> store. Owl integrates with different storage module like Zebra with a
> pluggable architecture.
> Initially, the proposal is to submit Owl as a Pig contrib project. Over
> time, it makes sense to move it to a Hadoop subproject.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
