[
https://issues.apache.org/jira/browse/BEAM-6772?focusedWorklogId=223451&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-223451
]
ASF GitHub Bot logged work on BEAM-6772:
----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Apr/19 05:36
Start Date: 05/Apr/19 05:36
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-480154077
@kanterov I went ahead and changed array and map selects to distribute the
select. This preserves the invariant that the field name selected is always the
one that appears in the resulting schema, and I believe is closer to what Spark
does.
I still think we should have a thread on the dev list to discuss the
detailed semantics, as we still might want to change them. However I think with
this last commit, we are probably closer to where we want to end up.
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 223451)
Time Spent: 11h 40m (was: 11.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: 11h 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)
