[
https://issues.apache.org/jira/browse/BEAM-6772?focusedWorklogId=209222&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-209222
]
ASF GitHub Bot logged work on BEAM-6772:
----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Mar/19 22:59
Start Date: 06/Mar/19 22:59
Worklog Time Spent: 10m
Work Description: reuvenlax commented on pull request #8006: [BEAM-6772]
Change Select semantics to match what a user expects
URL: https://github.com/apache/beam/pull/8006
Details in the JIRA: The current Select transform provides confusing and
less-useful semantics. This PR causes the transform to remove extra levels of
nesting that are left after a Select.
----------------------------------------------------------------
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: 209222)
Time Spent: 10m
Remaining Estimate: 0h
> 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: 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)
