Hi Boris, Could you please file this bug in a jira? It would be better to describe the procedure to reproduce it.
Thanks in advance, JL On Mon, Jul 4, 2016 at 3:45 PM, Boris Schminke <schmink...@gmail.com> wrote: > Hi, all! > I would like to see the message of SQL error thrown by JDBC Interpreter > and not something like this (which was not the case in old Hive > Interpreter): > > class java.sql.SQLException > > com.facebook.presto.jdbc.PrestoResultSet.resultsException(PrestoResultSet.java:1812) > > com.facebook.presto.jdbc.PrestoResultSet.getColumns(PrestoResultSet.java:1761) > com.facebook.presto.jdbc.PrestoResultSet.<init>(PrestoResultSet.java:141) > com.facebook.presto.jdbc.PrestoStatement.execute(PrestoStatement.java:193) > > org.apache.zeppelin.jdbc.JDBCInterpreter.executeSql(JDBCInterpreter.java:312) > > org.apache.zeppelin.jdbc.JDBCInterpreter.interpret(JDBCInterpreter.java:396) > > org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:94) > > org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:341) > org.apache.zeppelin.scheduler.Job.run(Job.java:176) > > org.apache.zeppelin.scheduler.ParallelScheduler$JobRunner.run(ParallelScheduler.java:162) > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > java.util.concurrent.FutureTask.run(FutureTask.java:266) > > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > java.lang.Thread.run(Thread.java:745) > -- 이종열, Jongyoul Lee, 李宗烈 http://madeng.net
