Hey there,

Can you run a quick test for me? Could you try adding a type cast at that
line? Instead of: "return Datasets.load(uri, GenericRecord.class);", change
it to "return (Dataset<GenericRecord>)Datasets.load(uri,
GenericRecord.class);". Notice the "(Dataset<GenericRecord>)".

-Abe

On Tue, Sep 9, 2014 at 11:19 PM, Venkat Ranganathan <
[email protected]> wrote:

> Hi
>
> With the recent parquet changes, it looks like we have hit a JDK issue.   I
> encountered it in 1.6.0_32 but it may be affecting other versions also.
>
> Sqoop compilation will fail with an error something like this
> ==
>  [javac]
>
> /home/venkat/dev-work/apache-ws/sqoop/src/test/com/cloudera/sqoop/TestParquetImport.java:190:
> type parameters of <V>V cannot be determined; no unique maximal instance
> exists for type variable V with upper bounds
>
> org.kitesdk.data.Dataset<org.apache.avro.generic.GenericRecord>,org.kitesdk.data.View<E>
> [javac] return Datasets.load(uri, GenericRecord.class);
> [javac] ^
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 1 error
> [javac] 2 warnings‏
> ==
>
> With a 1.6.0_37 Java or 1.7.0 versions, the compilation went through.
>
> So, if you are running into compilation issues with Sqoop, please consider
> updating the Java version in use.
>
> We can also see if we can fix this issue such that we compile fine on all
> Java 1.6.x versions
>
>
> Thanks
>
> Venkat
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

Reply via email to