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-4794) Move Nexmark and SQL to use the new Schema framework
Date Tue, 17 Jul 2018 18:15:00 GMT


ASF GitHub Bot logged work on BEAM-4794:

                Author: ASF GitHub Bot
            Created on: 17/Jul/18 18:14
            Start Date: 17/Jul/18 18:14
    Worklog Time Spent: 10m 
      Work Description: akedin commented on a change in pull request #5956: [BEAM-4794] Move
SQL and SQL Nexmark to the schema framework

 File path: sdks/java/core/src/main/java/org/apache/beam/sdk/transforms/
 @@ -98,7 +98,7 @@ public void processElement(ProcessContext context) {
                       context.output(jsonToRow(objectMapper(), context.element()));
-          .setCoder(schema.getRowCoder());
+          .setSchema(schema, SerializableFunctions.identity(), SerializableFunctions.identity());
 Review comment:
   +1, some shorthand version would be helpful. Maybe default to `identity()` and have a couple
of overloads of `setSchema()` to allow customization? Or wire it up to schema registry and
default to `identity()` there? 
   And is `setSchema` the right place to specify these transforms? Isn't it just conflating
 `.apply(ToRow.withSchema())... .apply(ParDo.of(fromRow()))`? My thought is that if the transforms
are non-trivial, then they are probably better be specified as `ParDos`

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: 124158)
    Time Spent: 1h 20m  (was: 1h 10m)

> Move Nexmark and SQL to use the new Schema framework
> ----------------------------------------------------
>                 Key: BEAM-4794
>                 URL:
>             Project: Beam
>          Issue Type: Sub-task
>          Components: dsl-sql
>            Reporter: Reuven Lax
>            Assignee: Reuven Lax
>            Priority: Major
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
> This will allow SQL to accept user types. It will also allow the deletion of a lot of

This message was sent by Atlassian JIRA

View raw message