You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Sudheesh Katkam (JIRA)" <ji...@apache.org> on 2015/08/20 06:31:45 UTC
[jira] [Closed] (DRILL-3674) RuntimeException - Unknown variable or
type "logger"
[ https://issues.apache.org/jira/browse/DRILL-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sudheesh Katkam closed DRILL-3674.
----------------------------------
Resolution: Duplicate
Assignee: Sudheesh Katkam (was: Daniel Barclay (Drill))
> RuntimeException - Unknown variable or type "logger"
> ----------------------------------------------------
>
> Key: DRILL-3674
> URL: https://issues.apache.org/jira/browse/DRILL-3674
> Project: Apache Drill
> Issue Type: Bug
> Components: Client - CLI, SQL Parser
> Affects Versions: 1.1.0
> Environment: OSX 10.9.5 Java 8, build 20, embedded mode
> Reporter: Edmon Begoli
> Assignee: Sudheesh Katkam
> Priority: Minor
>
> I execute a query (details removed given the project nature) with a wrong placement of distinct statement :
> select distinct columns[1] as payer, sum(columns[4]) as charge, sum(columns[5]) as payment from dfs.`<PATH TO VALID FILE>` group by columns[1];
> I get an exception:
> java.lang.RuntimeException: java.sql.SQLException: SYSTEM ERROR: CompileException: Line 75, Column 177: Unknown variable or type "logger"
> Fragment 3:0
> [Error Id: 952f78ef-9a30-4060-a857-40960648fc24 on 192.168.1.16:31010]
> at sqlline.IncrementalRows.hasNext(IncrementalRows.java:73)
> at sqlline.TableOutputFormat$ResizingRowsProvider.next(TableOutputFormat.java:87)
> at sqlline.TableOutputFormat.print(TableOutputFormat.java:118)
> at sqlline.SqlLine.print(SqlLine.java:1583)
> at sqlline.Commands.execute(Commands.java:852)
> at sqlline.Commands.sql(Commands.java:751)
> at sqlline.SqlLine.dispatch(SqlLine.java:738)
> at sqlline.SqlLine.begin(SqlLine.java:612)
> at sqlline.SqlLine.start(SqlLine.java:366)
> at sqlline.SqlLine.main(SqlLine.java:259)
> In some previous logs, I have seen that the Log4J might not have been properly configured by the system (out of the box).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)