Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Wed, 1 Jun 2016 16:46:59 +0000 (UTC)
From: "Shawn Lavelle (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.12972203.1464038417000.3864.1464799619306@Atlassian.JIRA>
In-Reply-To: <JIRA.12972203.1464038417000@Atlassian.JIRA>
References: <JIRA.12972203.1464038417000@Atlassian.JIRA> <JIRA.12972203.1464038417218@arcas>
Subject: [jira] [Commented] (HIVE-13824) NOSUCHMethodFound
 org.fusesource.jansi.internal.Kernel32.GetConsoleOutputCP()I
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 01 Jun 2016 16:47:01 -0000


    [ https://issues.apache.org/jira/browse/HIVE-13824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310613#comment-15310613 ] 

Shawn Lavelle commented on HIVE-13824:
--------------------------------------

What resolved this for me was making sure I had the right version of jline in the classpath (2.12).

> NOSUCHMethodFound org.fusesource.jansi.internal.Kernel32.GetConsoleOutputCP()I
> ------------------------------------------------------------------------------
>
>                 Key: HIVE-13824
>                 URL: https://issues.apache.org/jira/browse/HIVE-13824
>             Project: Hive
>          Issue Type: Bug
>          Components: Beeline, Hive
>         Environment: WIndows 8, HADOOP 2.7, HIVE 1.2.1, SPARK 1.6.1
>            Reporter: Ekta Paliwal
>
> 0
> down vote
> favorite
> I have been trying to install hive on windows. I have 64 bit windows 8 on which HADOOP and SPARK are running. I have
> 1.HADOOP_HOME
> 2.HIVE_HOME
> 3.SPARK_HOME
> 4.Platform
> 5.PATH
> all these variables set up on my system. Also, I was getting these error before
> Missing Hive Execution Jar: C:\hadoop1\hadoop-2.7.2\apache-hive-1.2.1-bin/lib/hive-exec-*.jar
> I solved these error by editing the Hive file inside bin folder of HIVE. These errors are because of the forward slash"/" in environment variables in HIVE file. I replace them with "\" and those errors are gone. But now I am facing another problem. I am getting these error
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in [jar:file:/C:/spark/spark-1.6.1-bin-hadoop2.6/lib/spark-assembly-1.6.1-hadoop2.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in [jar:file:/C:/hadoop2.7/hadoop-2.7.1/share/hadoop/common/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> Beeline version 1.6.1 by Apache Hive
> Exception in thread "main" java.lang.NoSuchMethodError: org.fusesource.jansi.internal.Kernel32.GetConsoleOutputCP()I
>     at jline.WindowsTerminal.getConsoleOutputCodepage(WindowsTerminal.java:293)
>     at jline.WindowsTerminal.getOutputEncoding(WindowsTerminal.java:186)
>     at jline.console.ConsoleReader.<init>(ConsoleReader.java:230)
>     at jline.console.ConsoleReader.<init>(ConsoleReader.java:221)
>     at jline.console.ConsoleReader.<init>(ConsoleReader.java:209)
>     at org.apache.hive.beeline.BeeLine.getConsoleReader(BeeLine.java:834)
>     at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:770)
>     at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:484)
>     at org.apache.hive.beeline.BeeLine.main(BeeLine.java:467)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke(Method.java:606)
>     at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
>     at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> I have searched alot on these. Also I have posted these question on HIVE User mailing List but got no response. Please help me with this. Not even getting results when google this error.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)