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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
