Skip to content

Commit 579a00f

Browse files
xianwillrtyler
authored andcommitted
Fix OReilly tick
1 parent 4f44486 commit 579a00f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

_posts/2021-05-19-kafka-delta-ingest.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ This scenario is likely fairly relatable to a lot of folks:
1313

1414
* I'm using Kafka to ingest data from my application that I want to analyze later.
1515
* I want my Kafka data to land in my data warehouse and be queryable pretty soon after ingestion, but I'm fine with some seconds or minutes worth of latency before data lands in my warehouse and becomes queryable.
16-
* I haven't found a blog post or O`Reilly book excerpt yet that makes me feel super confident about my current approach for moving my Kafka streams into my data warehouse. Things I've tried so far _work_ but either cost a lot, are really complicated to setup and maintain, or both.
16+
* I haven't found a blog post or O'Reilly book excerpt yet that makes me feel super confident about my current approach for moving my Kafka streams into my data warehouse. Things I've tried so far _work_ but either cost a lot, are really complicated to setup and maintain, or both.
1717

1818

1919
Scribd is in exactly this position. We use Spark Structured Streaming jobs running in Databricks to write data ingested on Kafka topics into Delta Lake tables. Our monthly AWS bill keeps reminding us that there _should_ be a better solution for this common ETL need.

0 commit comments

Comments
 (0)