You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Marios Trivyzas (Jira)" <ji...@apache.org> on 2022/03/16 13:52:00 UTC

[jira] [Created] (FLINK-26686) Use a junit temp folder for TestingTaskManagerRuntimeInfo tmpWorkingDirectory

Marios Trivyzas created FLINK-26686:
---------------------------------------

             Summary: Use a junit temp folder for TestingTaskManagerRuntimeInfo tmpWorkingDirectory
                 Key: FLINK-26686
                 URL: https://issues.apache.org/jira/browse/FLINK-26686
             Project: Flink
          Issue Type: Improvement
          Components: Runtime / Configuration
            Reporter: Marios Trivyzas


Following FLINK-26418, maybe it's a good idea to not expose a constructor without the *tmpWorkingDirectory* as this ends up in creating the ROCKSDB folders inside */tmp* (which at least is an improvement over having them created in the given {*}CWD{*}, ending up in the root folder of each given module (i.e: {*}flink-table/flink-table-planner{*}).

If the *tmpWorkingDirectory* is a mandatory argument then the consumers (IT tests) would have to provide this directory and they can use the standard junit *TemporaryFolder.newFolder()* so that the directories are automatically deleted after the tests are run, and devs can find those directories under the build/test folder of each module and not in an unorganized structure in */tmp* (or windows user's tmp folder).



--
This message was sent by Atlassian Jira
(v8.20.1#820001)