microsoft / microsoft/fabricnotes
[Note] Event-driven consumption & writing to delta tables
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 118
- Forks
- 31
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 1
Description
What concept do you need more clarity on?
Event-driven architecture using Event Hub as the source
Any reference explaining that concept
Event Hub integration: using Spark to ingest Event Hub payloads into Delta tables, using Spark to create Event Hub messages
Have you checked the list of issues to see if there is a similar suggestion?
- Yes, I have checked (please check this box)
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
Start by reviewing the issue description and the repository's existing drawings about Microsoft Fabric concepts. Clarify the intended scope for illustrating Event Hub as a source, Spark ingestion into Delta tables, and Spark-created Event Hub messages. Done should be an accepted, understandable illustration covering the agreed concepts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- spark
- Domain
- data-engineering, documentation, stream-processing
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100