[ 
https://issues.apache.org/jira/browse/BEAM-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17145618#comment-17145618
 ] 

Beam JIRA Bot commented on BEAM-960:
------------------------------------

This issue was marked "stale-P2" and has not received a public comment in 14 
days. It is now automatically moved to P3. If you are still affected by it, you 
can comment and move it back to P2.

> JdbcIO should infer coder when possible (such as via RowMapper)
> ---------------------------------------------------------------
>
>                 Key: BEAM-960
>                 URL: https://issues.apache.org/jira/browse/BEAM-960
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-jdbc
>            Reporter: Kenneth Knowles
>            Priority: P3
>
> There are a few ways that we typically do this:
> # Inspect the static args of the class implementing {{RowMapper}} to 
> determine the output type, then consult the coder registry. This method is 
> more limited and not lambda-friendly.
> # For the a "functional interface" version, like {{RowMapper}} that allows 
> setting the output type descriptor.
> # Also provide an abstract class-based version, for example accepting a 
> {{SimpleFunction}} that will automatically have a rich output type descriptor.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to