[
https://issues.apache.org/jira/browse/BEAM-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946434#comment-15946434
]
Kenneth Knowles commented on BEAM-1773:
---------------------------------------
I am not really in favor of forcing the caller of {{validate}} to catch and
wrap an {{Exception}}, which is I think the only thing they can do. It is OK,
though. There are more IO authors than runner authors, and it is the runner
authors who have to add boilerplate. So that makes sense.
> Consider allowing Source#validate() to throw exception
> ------------------------------------------------------
>
> Key: BEAM-1773
> URL: https://issues.apache.org/jira/browse/BEAM-1773
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Ted Yu
> Assignee: Jean-Baptiste Onofré
>
> In HDFSFileSource.java :
> {code}
> @Override
> public void validate() {
> ...
> } catch (IOException | InterruptedException e) {
> throw new RuntimeException(e);
> }
> {code}
> Source#validate() should be allowed to throw exception so that we don't
> resort to using RuntimeException.
> Here was related thread on mailing list:
> http://search-hadoop.com/m/Beam/gfKHFOwE0uETxae?subj=Re+why+Source+validate+is+not+declared+to+throw+any+exception
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
