Github user twalthr commented on a diff in the pull request:
https://github.com/apache/flink/pull/3318#discussion_r101299257
--- Diff:
flink-core/src/main/java/org/apache/flink/api/java/typeutils/TypeExtractor.java
---
@@ -1723,20 +1720,17 @@ private boolean isValidPojoField(Field f, Class<?>
clazz, ArrayList<Type> typeHi
// return type is void.
m.getReturnType().equals(Void.TYPE)
) {
- if(hasSetter) {
- throw new
IllegalStateException("Detected more than one setter");
- }
hasSetter = true;
}
}
if(hasGetter && hasSetter) {
return true;
} else {
if(!hasGetter) {
- LOG.debug(clazz+" does not contain a
getter for field "+f.getName() );
+ LOG.info(clazz+" does not contain a
getter for field "+f.getName() );
--- End diff --
I would say yes. It is very hard for users to figure out why a object is
not a POJO. Information about the problematic field is helpful. This message
will occur as often as `clazz is not a valid POJO.`, so one output per non-POJO.
---
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.
---
