You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2018/06/28 19:57:00 UTC
[jira] [Resolved] (CALCITE-2386) Support columns containing struct
/ nested rows
[ https://issues.apache.org/jira/browse/CALCITE-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser resolved CALCITE-2386.
---------------------------------
Resolution: Fixed
Fixed in [https://git-wip-us.apache.org/repos/asf?p=calcite-avatica.git;a=commit;h=4b7eee5bf430b916c7c07897b6f60d2b6b6dabb7]
Thanks for the patch, [~kenn]! Very impressive for a first-time commit to Avatica :)
> Support columns containing struct / nested rows
> -----------------------------------------------
>
> Key: CALCITE-2386
> URL: https://issues.apache.org/jira/browse/CALCITE-2386
> Project: Calcite
> Issue Type: Improvement
> Components: avatica
> Reporter: Kenneth Knowles
> Assignee: Kenneth Knowles
> Priority: Major
> Fix For: avatica-1.13.0
>
>
> Avatica row / struct support appears not quite wired up. Using sqlline with the Beam JDBC driver:
> {code}
> > select row(1, 2);
> +--------+
> | EXPR$0 |
> +--------+
> java.lang.RuntimeException: not implemented
> at org.apache.calcite.avatica.AvaticaSite.notImplemented(AvaticaSite.java:420)
> at org.apache.calcite.avatica.AvaticaSite.get(AvaticaSite.java:302)
> at org.apache.calcite.avatica.AvaticaResultSet.getObject(AvaticaResultSet.java:377)
> at sqlline.Rows$Row.<init>(Rows.java:175)
> at sqlline.IncrementalRows.hasNext(IncrementalRows.java:66)
> at sqlline.TableOutputFormat.print(TableOutputFormat.java:33)
> at sqlline.SqlLine.print(SqlLine.java:1648)
> at sqlline.Commands.execute(Commands.java:834)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {code}
> Currently Avatica 1.11.0 but checking the code it looks like the same problem exists today.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)