Github user DT-Priyanka commented on a diff in the pull request:
https://github.com/apache/apex-malhar/pull/295#discussion_r67311141
--- Diff:
contrib/src/main/java/com/datatorrent/contrib/cassandra/CassandraPOJOOutputOperator.java
---
@@ -162,35 +160,75 @@ public void activate(Context.OperatorContext context)
}
getters.add(getter);
}
+ super.activate(context);
+ }
+
+ private void populateFieldInfosFromPojo(ColumnDefinitions rsMetaData)
+ {
+ fieldInfos = Lists.newArrayList();
+ Field[] fields = pojoClass.getDeclaredFields();
+ for (int i = 0; i < rsMetaData.size(); i++) {
+ String columnName = rsMetaData.getName(i);
+ String pojoField = getMatchingField(fields, columnName);
+ if (pojoField != null && pojoField.length() != 0) {
+ fieldInfos.add(new FieldInfo(columnName, pojoField, null));
+ } else {
+ LOG.error("Couldn't find corrosponding pojo field for column: " +
columnName);
--- End diff --
I haven't tried it yet, but if not null constraint is defined it should
throw exception. Ideally the app developer should populate the fields as per
the table schema.
We can do a quick schema check and throw exception before hand but I wonder
will that do much of value addition?
---
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.
---
