Github user fhueske commented on the issue:
https://github.com/apache/flink/pull/6253
It's a good question whether to add a new class or not. Right now,
extending the implementation of `ExistingField` seems like a better approach to
me. Once we add a `ParsingExistingField` extractor
Github user HeartSaVioR commented on the issue:
https://github.com/apache/flink/pull/6253
If we would like to answer 1 as "Yes, apply the change to ExistingField.",
we can rebase this PR with below branch.
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
