[
https://issues.apache.org/jira/browse/BEAM-4461?focusedWorklogId=144963&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-144963
]
ASF GitHub Bot logged work on BEAM-4461:
----------------------------------------
Author: ASF GitHub Bot
Created on: 17/Sep/18 17:15
Start Date: 17/Sep/18 17:15
Worklog Time Spent: 10m
Work Description: akedin commented on issue #6316: [BEAM-4461] Add Unnest
transform.
URL: https://github.com/apache/beam/pull/6316#issuecomment-422097268
I am not sure what is the correct thing to do here. I think that we should
prevent users from explicitly adding duplicate fields (as far as I remember BQ
SQL disallows duplicate fields, don't know about standard). But I don't know if
this can be a valid thing to do internally. For example, when implementing a
join there potentially can exist an intermediary joined schema that combines
left and right side of the join. Ambiguities should be dealt with by projection
which is applied after that. Does this sound like something that can happen?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 144963)
Time Spent: 9h 50m (was: 9h 40m)
> Create a library of useful transforms that use schemas
> ------------------------------------------------------
>
> Key: BEAM-4461
> URL: https://issues.apache.org/jira/browse/BEAM-4461
> Project: Beam
> Issue Type: Sub-task
> Components: sdk-java-core
> Reporter: Reuven Lax
> Assignee: Reuven Lax
> Priority: Major
> Time Spent: 9h 50m
> Remaining Estimate: 0h
>
> e.g. JoinBy(fields). Project, Filter, etc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
