Re: ColumnLineageGraph.java Compile Error in Frontend

[huangquanl...@gmail.com]

Got it. Thanks!

On 2017-10-04 07:55, Jeszy  wrote: 
> Hello Quanlong,
> 
> This is https://issues.apache.org/jira/browse/IMPALA-6009, there's
> already a fix (but see follow up talk on jira).
> 
> HTH
> 
> On 4 October 2017 at 01:53, 黄权隆  wrote:
> > Hi all,
> >
> > I encountered a compile error when I try to recompile impala yesterday. The
> > error is in Frontend:
> >
> > [ERROR] COMPILATION ERROR :
> >
> > [INFO] -
> >
> > [ERROR]
> > /mnt/volume1/impala-orc/incubator-impala/fe/src/main/java/org/apache/impala/analysis/ColumnLineageGraph.java:[593,11]
> > no suitable method found for putString(java.lang.String)
> >
> > method
> > com.google.common.hash.Hasher.putString(java.lang.CharSequence,java.nio.charset.Charset)
> > is not applicable
> >
> >   (actual and formal argument lists differ in length)
> >
> > method
> > com.google.common.hash.PrimitiveSink.putString(java.lang.CharSequence,java.nio.charset.Charset)
> > is not applicable
> >
> >   (actual and formal argument lists differ in length)
> >
> >
> > I also found this in the jenkins builds. It seems that
> > com.google.common.hash.Hasher exists in both guava-*.jar and
> > hive-exec-*.jar. Are there any changes in
> > hive-exec-1.1.0-cdh5.14.0-SNAPSHOT.jar recently? What can I do to recover
> > from this?
> >
> >
> > Thanks,
> >
> > Quanlong
> 

Re: ColumnLineageGraph.java Compile Error in Frontend

[Jeszy]

Hello Quanlong,

This is https://issues.apache.org/jira/browse/IMPALA-6009, there's
already a fix (but see follow up talk on jira).

HTH

On 4 October 2017 at 01:53, 黄权隆  wrote:
> Hi all,
>
> I encountered a compile error when I try to recompile impala yesterday. The
> error is in Frontend:
>
> [ERROR] COMPILATION ERROR :
>
> [INFO] -
>
> [ERROR]
> /mnt/volume1/impala-orc/incubator-impala/fe/src/main/java/org/apache/impala/analysis/ColumnLineageGraph.java:[593,11]
> no suitable method found for putString(java.lang.String)
>
> method
> com.google.common.hash.Hasher.putString(java.lang.CharSequence,java.nio.charset.Charset)
> is not applicable
>
>   (actual and formal argument lists differ in length)
>
> method
> com.google.common.hash.PrimitiveSink.putString(java.lang.CharSequence,java.nio.charset.Charset)
> is not applicable
>
>   (actual and formal argument lists differ in length)
>
>
> I also found this in the jenkins builds. It seems that
> com.google.common.hash.Hasher exists in both guava-*.jar and
> hive-exec-*.jar. Are there any changes in
> hive-exec-1.1.0-cdh5.14.0-SNAPSHOT.jar recently? What can I do to recover
> from this?
>
>
> Thanks,
>
> Quanlong

ColumnLineageGraph.java Compile Error in Frontend

[黄权隆]

Hi all,

I encountered a compile error when I try to recompile impala yesterday. The
error is in Frontend:

[ERROR] COMPILATION ERROR :

[INFO] -

[ERROR]
/mnt/volume1/impala-orc/incubator-impala/fe/src/main/java/org/apache/impala/analysis/ColumnLineageGraph.java:[593,11]
no suitable method found for putString(java.lang.String)

method
com.google.common.hash.Hasher.putString(java.lang.CharSequence,java.nio.charset.Charset)
is not applicable

  (actual and formal argument lists differ in length)

method
com.google.common.hash.PrimitiveSink.putString(java.lang.CharSequence,java.nio.charset.Charset)
is not applicable

  (actual and formal argument lists differ in length)


I also found this in the jenkins builds. It seems that
com.google.common.hash.Hasher exists in both guava-*.jar and
hive-exec-*.jar. Are there any changes in
hive-exec-1.1.0-cdh5.14.0-SNAPSHOT.jar recently? What can I do to recover
from this?


Thanks,

Quanlong

upcoming Jira downtime

[Michael Brown]

This was sent to committ...@apache.org et al:

Please be advised:


Sun, 08 Oct 2017 00:45:00 GMT - Sun, 08 Oct 2017 06:45:00 GMT:

Jira - issues.apache.org will be down for approximately 6 hours while the
database is exported and reloaded to correct a database collation/encoding
issue. This is necessary in preparation for the 7.x upgrade (to be
scheduled soon.)

-Chris
ASF Infra