You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/06/27 13:21:00 UTC

[jira] [Commented] (CALCITE-2386) Support columns containing struct / nested rows

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

ASF GitHub Bot commented on CALCITE-2386:
-----------------------------------------

Github user kennknowles commented on the issue:

    https://github.com/apache/calcite-avatica/pull/62
  
    CC: @apilloud @akedin


> 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
>            Priority: Major
>
> 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)