[
https://issues.apache.org/jira/browse/BEAM-6674?focusedWorklogId=258529&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-258529
]
ASF GitHub Bot logged work on BEAM-6674:
----------------------------------------
Author: ASF GitHub Bot
Created on: 12/Jun/19 08:49
Start Date: 12/Jun/19 08:49
Worklog Time Spent: 10m
Work Description: charithe commented on issue #8725: [BEAM-6674] Add
schema support to JdbcIO read
URL: https://github.com/apache/beam/pull/8725#issuecomment-501180367
If the user provides their own row mapper to convert the resultset to some
type `T`, then I don't see why the schema of `T` should be compatible with the
inferred schema of the resultset. For example, the query might have separate
fields to hold `first_name` and `last_name` but during the mapping the user
might choose to combine those two fields to create a single field named
`full_name`.
----------------------------------------------------------------
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: 258529)
Time Spent: 3h 10m (was: 3h)
> The JdbcIO source should produce schemas
> ----------------------------------------
>
> Key: BEAM-6674
> URL: https://issues.apache.org/jira/browse/BEAM-6674
> Project: Beam
> Issue Type: Sub-task
> Components: io-java-jdbc
> Reporter: Reuven Lax
> Assignee: Shehzaad Nakhoda
> Priority: Major
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
