Hudi 1.0 is the most powerful release to date for data lakehouses. Read the blog for details:. Secondary Indexing, Expression Indexes, Partial Updates, Non-blocking Concurrency Control, New LSM timeline, +more: #datalakehouse #opentableformat.

💼 We've changed the schedule of office hours to cater for different timezones! . 🌎 America-friendly time: Every Wednesday, 9 AM Pacific Time.🌏 Asia-friendly time: Every Thursday, 10 AM Indian Standard Time. 🔗 Check out the office hours page for meeting links to join!

RT @_xushiyan: ✍️ [Blog] Part 2 of building a RAG-based AI recommender 🤖. A reliable, efficient data lakehouse isn't just a prerequisite—it….

Read more about the support implementation from the RFC:

💡 Using SQL 𝐂𝐀𝐋𝐋 𝐩𝐫𝐨𝐜𝐞𝐝𝐮𝐫𝐞𝐬 can be a great help with inspecting and managing Hudi tables. Back in 2022, Hudi Spark integration added support for CALL procedures. You can perform a wide range of operations:. ✅ 𝐅𝐞𝐭𝐜𝐡 𝐭𝐚𝐛𝐥𝐞 𝐢𝐧𝐟𝐨: show table properties,

🚀 Exciting news for the #ApacheHudi community!. We’ve enabled GitHub Discussions 🎉.A dedicated space to ask questions, share ideas & collaborate. Join the conversation 👉

After each write commit to your Hudi table, you can configure a callback function to be invoked, sending commit metadata to Kafka, Pulsar, or a custom HTTP endpoint to trigger downstream processing tailored to your business needs!. 👉Learn from the docs

💡 You can configure 𝐏𝐨𝐬𝐭-𝐜𝐨𝐦𝐦𝐢𝐭 𝐜𝐚𝐥𝐥𝐛𝐚𝐜𝐤 with @apachekafka , @apache_pulsar , and HTTP endpoints. 👇 More in the reply

👉 Follow instructions with more details in the release notes:

2️⃣ Upgrade and resume table service runners with the 1.x jar.3️⃣ Upgrade readers with the 1.x jar.4️⃣ Now turn on 𝗵𝗼𝗼𝗱𝗶𝗲.𝘄𝗿𝗶𝘁𝗲.𝗮𝘂𝘁𝗼.𝘂𝗽𝗴𝗿𝗮𝗱𝗲 in writer config, and the migration is done! Time to profit.

1️⃣ Restart your writer jobs with Hudi 1.x jar. Don't worry—it'll backward-compatible write to existing 0.x tables as long as you set 𝗵𝗼𝗼𝗱𝗶𝗲.𝘄𝗿𝗶𝘁𝗲.𝗮𝘂𝘁𝗼.𝘂𝗽𝗴𝗿𝗮𝗱𝗲=false; if you're using metadata table or running async table services, disable them first.

💡 𝐘𝐨𝐮 𝐜𝐚𝐧 𝐞𝐚𝐬𝐢𝐥𝐲 𝐦𝐢𝐠𝐫𝐚𝐭𝐞 𝐭𝐨 𝐇𝐮𝐝𝐢 𝟏.𝐱 𝐭𝐨 𝐠𝐚𝐢𝐧 𝐦𝐚𝐣𝐨𝐫 𝐩𝐞𝐫𝐟𝐨𝐫𝐦𝐚𝐧𝐜𝐞 𝐛𝐨𝐨𝐬𝐭 🚀. Steps 👇

By default, /𝗲𝘁𝗰/𝗵𝘂𝗱𝗶/𝗰𝗼𝗻𝗳/ will be the directory to place the file. Or you can set env var 𝗛𝗨𝗗𝗜_𝗖𝗢𝗡𝗙_𝗗𝗜𝗥 to choose another directory. Happy lakehousing!.

✅ Perfect for configs like "hoodie.parquet.compression.codec" or "hoodie.datasource.write.hive_style_partitioning" for example, so you can reduce some repeating configs, and easily manage some standardized table setup across your data lakes.

💡 𝗧𝗶𝗽 𝗼𝗳 𝘁𝗵𝗲 𝗱𝗮𝘆: Having some globally shared Hudi configs used by every job? .Set Hudi's global config directory and put those into 𝗵𝘂𝗱𝗶-𝗱𝗲𝗳𝗮𝘂𝗹𝘁𝘀.𝗰𝗼𝗻𝗳 !. #apachehudi #lakehouse #dataengineering

RT @Onehousehq: 🎉 A new chapter "Running Hudi in Production" is now available in the early release of "Apache Hudi™: The Definitive Guide"….

Join this month's developer sync call with PMC member @_xushiyan on July 23, 5 PM PT to learn about the Rust implementation of @apachehudi with API bindings in Python and C++ !. ⭐️ GitHub repo: 👉 Joining instructions:

RT @_xushiyan: 💡 𝗛𝗼𝘄 𝗱𝗼𝗲𝘀 𝗱𝗮𝘁𝗮-𝘀𝗸𝗶𝗽𝗽𝗶𝗻𝗴 𝘄𝗼𝗿𝗸 𝗶𝗻 @apachehudi ?. The metadata table (a multi-modal index system) located within your Hudi tab….

RT @_xushiyan: 🚀 New Blog: Building a RAG-based AI Recommender (Part 1/2). 👉 📚 What's inside: .✦ How RAG works end….

Interested in contributing to the next release? Explore starter issues here:

What's more, the 0.4.0 Hudi-rs artifacts are being added to @raydistributed and @daftengine to unlock additional query engine support such as incremental query, time-travel query, and reading MOR tables!.