microsoft / microsoft/fabric-cli

[BUG] bulk-export errors with "[NotSupported] Only supported for Lakehouse/Files"

Open Beginner friendly
#287 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ai:bug-triage:unable-to-process bug
Dominant language
Python
Stars
173
Forks
63
Avg merge
2d 19h
Merged PRs (30d)
4

Description

Bug Description

When attempting to do a bulk export of items from any workspace or folder I get the error

"x bulk-export: [NotSupported] Only supported for Lakehouse/Files"

The error is actually regarding the output filepath parameter

fab bulk-export <workspace>/<folder> -o ./ --recursive

.. fails

fab bulk-export <workspace>/<folder> -o ./temp --recursive

.. succeeds.

fabric-cli version

1.7.0

Python version

Python 3.12.0

Operating System

Windows

CLI Mode

Command line mode

Authentication Method

Interactive browser login

Steps to Reproduce
  1. Go to a local temporary folder.
  2. Command

fab bulk-export / -o ./ --recursive

(redacted)

Expected Behavior

Users would reasonably assume the path resolution should work for any valid filesystem path

Actual Behavior

Cli immediately errors with
"x bulk-export: [NotSupported] Only supported for Lakehouse/Files"

Bulk export aborts with no items exported.

Additional Context

No response

Possible Solution

Either the path resolver needs updating to allow os-aware filepath formats, or the docs need to be more explicit about the path requirements

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing fab bulk-export <workspace>/<folder> -o ./ --recursive and compare it with the successful -o ./temp command. Trace the bulk-export output path validation or documentation for filesystem path requirements; done means a valid current-directory path no longer produces the Lakehouse/Files error and recursive export completes.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.