Make exportTable command volume aware
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 487
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 13
Description
**Is your feature request related to a problem? Please describe.**
When using `exportTable` command, it does not take into consideration of multiple volumes and creates a single distcp.txt file. The file does not differentiate between volumes and the file must be post-processed to separate the files by volume(s) for feeding to individual distcp commands for each volume when exporting a table that uses more than one volume.
**Describe the solution you'd like**
Have the command generate a single file (distcp) list per volume. The solution should play nice with `importTable` command. It may also be useful if the exported metadata and the distcp file lists are preserved after the import table process to allow for post-processing validation.
**Additional context**
This is a follow on to #2869, #2871 and #2849 (offline option) which implement work-arounds for `exportTable` and `importTable` not being volume aware. Inspired by changes submitted by @drewfarris for `importTable` to handle multiple directories.
Contributor guide
Assessment
This issue has not been assessed yet.