[
https://issues.apache.org/jira/browse/BEAM-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132122#comment-17132122
]
Beam JIRA Bot commented on BEAM-960:
------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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: P2
> Labels: stale-P2
>
> 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)
