Rajat Venkatesh created ZEPPELIN-628:
----------------------------------------
Summary: JDBC Interpreter mangles SQL
Key: ZEPPELIN-628
URL: https://issues.apache.org/jira/browse/ZEPPELIN-628
Project: Zeppelin
Issue Type: Bug
Components: Interpreters
Affects Versions: 0.6.0
Reporter: Rajat Venkatesh
Priority: Critical
Reproducer:
{code}
%jdbc
select max(ss_promo_sk), ss_customer_sk from qhive.tpcds_orc_500.store_sales
where ss_sold_date_sk >= 2452640 and ss_customer_sk > 3 and ss_customer_sk < 20
group by ss_customer_sk
{code}
Actually runs
{code}
_promo_sk), ss_customer_sk from qhive.tpcds_orc_500.store_sales where
ss_sold_date_sk >= 2452640 and ss_customer_sk > 3 and ss_customer_sk < 20 group
by ss_customer_sk'
{code}
It looks like it is trying to find a property key which is a feature I do not
understand.
Logs:
{code}
INFO [2016-01-22 19:16:02,306] ({pool-2-thread-3}
JDBCInterpreter.java[interpret]:344) - Run SQL command 'select
max(ss_promo_sk), ss_customer_sk from qhive.tpcds_orc_500.store_sales where
ss_sold_date_sk >= 2452640 and ss_customer_sk > 3 and ss_customer_sk < 20 group
by ss_customer_sk'
INFO [2016-01-22 19:16:02,307] ({pool-2-thread-3}
JDBCInterpreter.java[interpret]:355) - PropertyKey: ss_promo_sk, SQL command:
'_promo_sk), ss_customer_sk from qhive.tpcds_orc_500.store_sales where
ss_sold_date_sk >= 2452640 and ss_customer_sk > 3 and ss_customer_sk < 20 group
by ss_customer_sk'
{code}
The workaround is to run:
{code}
(default) select max(ss_promo_sk), ss_customer_sk from
qhive.tpcds_orc_500.store_sales where ss_sold_date_sk >= 2452640 and
ss_customer_sk > 3 and ss_customer_sk < 20 group by ss_customer_sk
{code}
If you can explain why a propertyKey is required, I can try to provide a patch.
I do not understand the intention behind propertyKeys.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
