Windows paths become part of the dbfs filename.

[IMarvinTPA]

Describe the issue

When uploading a file using "databricks fs cp" if you include a windows path, the path will become part of the filename. The expected result should ignore everything before the last "" and only keep the file name.

Steps to reproduce the behavior

1. databricks fs cp ".\testfile.ext" "dbfs:/FileStore/testLocation"
2. databricks fs ls "dbfs:/FileStore/testLocation"
3. See in the files list a file named "dbfs:/FileStore/testLocation/.\testfile.ext"
4. databricks fs cp "C:\testfile.ext" "dbfs:/FileStore/testLocation"
5. databricks fs ls "dbfs:/FileStore/testLocation"
6. See in the files list a file named "dbfs:/FileStore/testLocation/C:\testfile.ext"

Expected Behavior

Both of these examples should have resulted in
"dbfs:/FileStore/testLocation/testfile.ext"

Actual Behavior

It created
"dbfs:/FileStore/testLocation/.\testfile.ext"
and
"dbfs:/FileStore/testLocation/C:\testfile.ext"
which are just garbage.
(You can delete them fortunately.)

OS and CLI version

Windows, CLI version 0.209.0 and 0.211.0 (Two different machines.)

Is this a regression?

Unknown. I did not try older versions.

[shreyas-goenka]

Thank you for reporting this issue! I have verified that this is indeed an issue with the CLI. Note we still respect unix style file paths, so to use this from windows you can run:

// For absolute paths
databricks fs cp /foo/bar.txt dbfs:/FileStore/testLocation

// For relative paths
databricks fs cp bar.txt dbfs:/FileStore/testLocation
OR
databricks fs cp apple/mango.txt dbfs:/FileStore/testLocation

However, this UX is indeed not great nor intuitive. We have taken note of this issue and filed it in our backlog as an important UX improvement.

Please let me know if this workaround does not work for you, and we can consider prioritising a patch for this.

[IMarvinTPA]

The main problem is that powershell likes to autocomplete files by adding ".\" to the beginning of the file, so it is super easy to mess up.

[shreyas-goenka]

Yeah, that's fair. I'll prioritise working on it this week and it should be patched in a week or two.

[shreyas-goenka]

Fixed in #1118. This should be out in next week's CLI release!