Github user sachingoel0101 commented on the pull request:
https://github.com/apache/flink/pull/1031#issuecomment-132871675
Was there a specific reason to not generate fresh environments in the first
place? Or was it just to minimize object creations?
Here's what I propose though: Since there is already a `clearSinks`
argument to `createProgramPlan`, we can use that as an indicator that the cache
file list has to be cleared too, since it indicates a new Execution.
Further, instead of throwing an exception in case a `name` is
re-registered, we check if the `filePath` is actually the same. If not, then we
throw an exception, otherwise just silently ignore it.
---
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.
---
