microsoft / microsoft/fabricnotes
Error Handling/ Logging
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 118
- Forks
- 31
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 1
Description
Hello All,
I have started working on Microsoft Fabric data engineering POC using notebooks and pipelines and stuck in between, I am looking for below scenarios but did not get more details, looking for references if any please share,
-
When error occurs in PySpark notebook, what log does program output.
We need to design error handling rule and log format. -
Transaction Management -
Can PySpark manage transaction scope ?
Ex) We'd like to commit after program loads Table A and Table B. If program fails to load Table B, then program execute rollback Table A. -
Log Management - Does MS Fabric have log management function? Can we use LogAnalytics?
-
Backup/ restore function - Does MS Fabric have backup/restore function? can we use Synapse?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files, tests, or entry points. Start with the Microsoft Fabric and PySpark documentation for notebook errors, transactions, logging, and backup/restore, then document authoritative references that answer all four questions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, spark
- Domain
- cloud, data-engineering, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100