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

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

                Author: ASF GitHub Bot
            Created on: 28/Mar/19 17:00
            Start Date: 28/Mar/19 17:00
    Worklog Time Spent: 10m 
      Work Description: reuvenlax commented on issue #8006: [BEAM-6772] Change 
Select semantics to match what a user expects
URL: https://github.com/apache/beam/pull/8006#issuecomment-477684178
 
 
   FYI by "distribute array selects" I mean the following:
   
   if you have { a: {b: int, c: int}[] } and someone select "a.b", "a.c" the 
result should be {b: int[], c: int[]}. The same should be true if someone 
selects a.*. However if someone selects just a, you get the original schema 
back.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


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

    Worklog Id:     (was: 220155)
    Time Spent: 10h 10m  (was: 10h)

> Select transform has non-intuitive semantics
> --------------------------------------------
>
>                 Key: BEAM-6772
>                 URL: https://issues.apache.org/jira/browse/BEAM-6772
>             Project: Beam
>          Issue Type: Sub-task
>          Components: sdk-java-core
>            Reporter: Reuven Lax
>            Assignee: Reuven Lax
>            Priority: Major
>          Time Spent: 10h 10m
>  Remaining Estimate: 0h
>
> Consider the following schema:
> User:
>     name: STRING
>     location: Location
>  
> Location:
>     latitude: DOUBLE
>     longitude: DOUBLE
>  
> If you apply Select.fieldNames("location"), most users expect to get back a 
> row matching the Location schema. Instead you get back an outer schema with a 
> single location field in it. Select should instead unnest the output up to 
> the point where multiple fields are selected.



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

Reply via email to