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

[jira] [Work logged] (BEAM-5918) Add Cast transform for Rows

     [ https://issues.apache.org/jira/browse/BEAM-5918?focusedWorklogId=162615&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-162615 ]

ASF GitHub Bot logged work on BEAM-5918:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 05/Nov/18 17:46
            Start Date: 05/Nov/18 17:46
    Worklog Time Spent: 10m 
      Work Description: kanterov commented on issue #6888: [BEAM-5918] Add Cast transform for Rows
URL: https://github.com/apache/beam/pull/6888#issuecomment-435967943
 
 
   @kennknowles Gentle ping, or, perhaps, there is somebody else who can help with the review? @akedin 

----------------------------------------------------------------
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:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 162615)
    Time Spent: 3h 40m  (was: 3.5h)

> Add Cast transform for Rows
> ---------------------------
>
>                 Key: BEAM-5918
>                 URL: https://issues.apache.org/jira/browse/BEAM-5918
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Gleb Kanterov
>            Assignee: Gleb Kanterov
>            Priority: Major
>          Time Spent: 3h 40m
>  Remaining Estimate: 0h
>
> There is a need for a generic transform that given two Row schemas will convert rows between them. There must be a possibility to opt-out from certain kind of conversions, for instance, converting ints to shorts can cause overflow. Another example, a schema could have a nullable field, but never have NULL value in practice, because it was filtered out.
> What is needed:
> - widening values (e.g., int -> long)
> - narrowwing (e.g., int -> short)
> - runtime check for overflow while narrowing
> - ignoring nullability (nullable=true -> nullable=false)
> - weakening nullability (nullable=false -> nullable=true)
> - projection (Schema(a: Int32, b: Int32) -> Schema(a: Int32))



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)