[
https://issues.apache.org/jira/browse/BEAM-6772?focusedWorklogId=212728&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-212728
]
ASF GitHub Bot logged work on BEAM-6772:
----------------------------------------
Author: ASF GitHub Bot
Created on: 13/Mar/19 22:14
Start Date: 13/Mar/19 22:14
Worklog Time Spent: 10m
Work Description: kennknowles commented on issue #8006: [BEAM-6772]
Change Select semantics to match what a user expects
URL: https://github.com/apache/beam/pull/8006#issuecomment-472626943
I'm curious about this one:
```
CREATE TABLE IF NOT EXISTS test.test (
userId STRING,
location STRUCT<latitude FLOAT64, longtitude FLOAT64>
);
INSERT INTO test.test (userId, location) VALUES ("abc", (123.0, 234.0));
SELECT location FROM test.test;
-- Row location.latitude location.longtitude
-- 1 123.0 234.0
SELECT location.latitude FROM gleb_test.test;
-- Row latitude
-- 1 123.0
```
The output when you `SELECT location` is flattened. It should be one column
containing a row with the two fields. Is it just for display purposes?
----------------------------------------------------------------
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: 212728)
Time Spent: 4h (was: 3h 50m)
> 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: 4h
> 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)
