Github user HeartSaVioR commented on the issue:
https://github.com/apache/flink/pull/6253
Seeking for some guides on this PR:
1. Maybe we could replace the implementation of ExistingField with the
implementation of IsoDateStringAwareExistingField since the implementation is
on top of ExistingField. Would we think replacing is better?
2. ExistingField has no test so I also don't add test for
IsoDateStringAwareExistingField: I guess adding test might require more
understanding of Table API. Would it be OK to skip adding test for
IsoDateStringAwareExistingField?
cc. @fhueske
---
