[
https://issues.apache.org/jira/browse/APEXMALHAR-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279690#comment-15279690
]
ASF GitHub Bot commented on APEXMALHAR-1953:
--------------------------------------------
Github user bhupeshchawda commented on a diff in the pull request:
https://github.com/apache/incubator-apex-malhar/pull/215#discussion_r62801169
--- Diff:
library/src/main/java/com/datatorrent/lib/db/jdbc/AbstractJdbcPOJOOutputOperator.java
---
@@ -63,22 +58,18 @@
* @since 2.1.0
*/
@org.apache.hadoop.classification.InterfaceStability.Evolving
-public class JdbcPOJOOutputOperator extends
AbstractJdbcTransactionableOutputOperator<Object>
- implements Operator.ActivationListener<OperatorContext>
+public abstract class AbstractJdbcPOJOOutputOperator extends
AbstractJdbcTransactionableOutputOperator<Object>
{
- @NotNull
- private List<FieldInfo> fieldInfos;
+ private List<JdbcFieldInfo> fieldInfos;
--- End diff --
Yes, fieldInfos can be null if the statement is an insert statement. In
that case, it is generated by the operator code. I have inserted checks for
this in the concrete POJO output operator.
> Add generic (insert, update, delete) support to JDBC Output Operator
> --------------------------------------------------------------------
>
> Key: APEXMALHAR-1953
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-1953
> Project: Apache Apex Malhar
> Issue Type: Task
> Reporter: Bhupesh Chawda
> Assignee: Bhupesh Chawda
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
