beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (BEAM-3437) Support schema in PCollections
Date Wed, 04 Apr 2018 18:18:00 GMT


ASF GitHub Bot logged work on BEAM-3437:

                Author: ASF GitHub Bot
            Created on: 04/Apr/18 18:17
            Start Date: 04/Apr/18 18:17
    Worklog Time Spent: 10m 
      Work Description: reuvenlax commented on a change in pull request #4964: [BEAM-3437]
Introduce Schema class, and use it in BeamSQL

 File path: sdks/java/extensions/sql/src/test/java/org/apache/beam/sdk/extensions/sql/impl/parser/
 @@ -163,13 +164,13 @@ private static Table mockTable(String name, String type, String comment,
-                .coder(INTEGER)
+                .typeDescriptor(TypeName.INT32.type())
-                .coder(VARCHAR)
+                .typeDescriptor(CalciteUtils.toFieldType(SqlTypeName.VARCHAR))
 Review comment:
   <!--thread_id:cc_179026015_t; commit:9fe3a6d29a348e46ff2f5ca9e4396bf667e28046; resolved:0-->
   > **akedin** wrote:
   > I don't think that CalciteUtils should be used here, even if it's temporary. I'd rather
have our own `SqlType.VARCHAR = TypeName.STRING.withMetadata("VARCHAR")`.
   Done. Added it to RowSqlTypes (so we can later remove the builder class there, but leave
the defined types.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 87701)
    Time Spent: 7h 20m  (was: 7h 10m)

> Support schema in PCollections
> ------------------------------
>                 Key: BEAM-3437
>                 URL:
>             Project: Beam
>          Issue Type: Wish
>          Components: beam-model
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>          Time Spent: 7h 20m
>  Remaining Estimate: 0h
> As discussed with some people in the team, it would be great to add schema support in
{{PCollections}}. It will allow us:
> 1. To expect some data type in {{PTransforms}}
> 2. Improve some runners with additional features (I'm thinking about Spark runner with
data frames for instance).
> A technical draft document has been created: 
> I also started a PoC on a branch, I will update this Jira with a "discussion" PR.

This message was sent by Atlassian JIRA

View raw message