Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1031#issuecomment-132136444
I am not sure this is solving it the right way. I find it more intuitive if
cache files stay registered. They are part of the environment and should be
"sticky", like configuration settings as well (they don't get lost after
execution).
We could add a method to clear registered cache files. But if the problem
is really only the MultiplProgramsTest base, then this should be fixed to
return a new ExecutionEnvironment from a (the) TestEnvironmentFactory every
time you call `getExecutionEnvironment()`.
---
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.
---
