[FLINK-26686] Use a junit temp folder for TestingTaskManagerRuntimeInfo tmpWorkingDirectory

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Runtime / Configuration
• Assignee: Unassigned
• Reporter: Marios Trivyzas
• Created: 16/Mar/22 13:51
• Updated: 05/Apr/22 07:51

Description

Following FLINK-26418, maybe it's a good idea to not expose a constructor for TestingTaskManagerRuntimeInfo 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).