microsoft / microsoft/fabric-cli

[FEATURE] table load with schema enabled lakehouses

Open
#279 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Use Case / Problem

I gave command fab table load ..., but I get error "table load: [UnsupportedOperationForSchemasEnabledLakehouse] The operation is not supported for Lakehouse with schemas enabled".
I believe schema enabled lakehouses are the majority nowadays, so it would be nice to be able to do this with fab command instead of manually.

Proposed Solution

Not my expertise

Alternatives Considered

Manual upload

Impact Assessment
  • This would help me personally
  • This would help my team/organization
  • This would help the broader fabric-cli community
  • This aligns with Microsoft Fabric roadmap items
Implementation Attestation
  • I understand this feature should maintain backward compatibility with existing commands
  • I confirm this feature request does not introduce performance regressions for existing workflows
  • I acknowledge that new features must follow fabric-cli's established patterns and conventions
Implementation Notes

No response

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 the fab table load error against a schema-enabled lakehouse and trace the table-load command entry point. Determine the supported upload path for schema-enabled lakehouses while preserving existing behavior for other lakehouses; done means the command succeeds in both cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, data-engineering
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.