[
https://issues.apache.org/jira/browse/BEAM-6772?focusedWorklogId=212759&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-212759
]
ASF GitHub Bot logged work on BEAM-6772:
----------------------------------------
Author: ASF GitHub Bot
Created on: 13/Mar/19 23:09
Start Date: 13/Mar/19 23:09
Worklog Time Spent: 10m
Work Description: kanterov commented on issue #8006: [BEAM-6772] Change
Select semantics to match what a user expects
URL: https://github.com/apache/beam/pull/8006#issuecomment-472641498
Makes sense. I tried and both BigQuery and Spark have consistent behavior
for selecting rows nested in rows:
```
df.printSchema()
root
|-- userId: string (nullable = true)
|-- position: struct (nullable = true)
| |-- location: struct (nullable = true)
| | |-- longtitude: double (nullable = true)
| | |-- latitude: double (nullable = true)
df.select("position.location").printSchema()
root
|-- location: struct (nullable = true)
| |-- longtitude: double (nullable = true)
| |-- latitude: double (nullable = true)
```
----------------------------------------------------------------
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: 212759)
Time Spent: 4.5h (was: 4h 20m)
> 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: 4.5h
> 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)
