[
https://issues.apache.org/jira/browse/BEAM-6772?focusedWorklogId=212557&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-212557
]
ASF GitHub Bot logged work on BEAM-6772:
----------------------------------------
Author: ASF GitHub Bot
Created on: 13/Mar/19 17:42
Start Date: 13/Mar/19 17:42
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-472531210
The new behavior better matches how SQL works (Select a.b return an int if
b is an int. It doesn't return a nested row). However we could also make it
an option on the Select transform so the user can pick which behavior they
want.
On Wed, Mar 13, 2019 at 10:39 AM Gleb Kanterov <[email protected]>
wrote:
> I've started looking, the code makes sense, however, I need more time to
> think about the idea of automatic unnesting. I'm wondering if we can make
> it less implicit.
>
> As for me, I would expect the previous behavior, that's how, for instance,
> Spark data frames work, IIRC.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/beam/pull/8006#issuecomment-472529785>, or mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/AUGE1dwShANQpi5Q1EIyg-1oQY1XdHKEks5vWTfMgaJpZM4bh_oa>
> .
>
----------------------------------------------------------------
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: 212557)
Time Spent: 40m (was: 0.5h)
> 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: 40m
> 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)
