Hi Linkis Community,

**Date:** April 03, 2026
**Topic:** Engine Plugin Expansion
**Participants:** 林晓升, 格物谷, 汉雨唐落, 清晨
**Discussion Period:** 2026-04-03 14:30 - 17:24

---

**[14:30] 汉雨唐落:**
Thinking about expanding our engine plugin ecosystem. Currently seeing interest 
in:

- ClickHouse (fast OLAP queries)
- Apache Hudi (streaming data lake)
- StarRocks (real-time analytics)
- Apache Kylin (massive-scale OLAP)
- Doris (easy-to-use MPP)

Which engine would bring the most value to the community right now?

**[14:48] 林晓升:**
We have been evaluating ClickHouse for our ad-hoc query needs. The performance 
looks promising. Would be great to have native Linkis support.

**[15:07] 清晨:**
Hudi integration would unlock a lot of streaming use cases for us. Happy to 
share our integration experience if helpful.

**[15:21] 格物谷:**
What are the key features you would expect from a new engine plugin?

**[15:30] 汉雨唐落:**
Our team uses StarRocks daily. The query performance is impressive. If we can 
connect it through Linkis, it would simplify our architecture.

**[15:52] 林晓升:**
From a user perspective, having more engine options is always good. The key is 
making sure the integration is solid and well-documented.

**[16:17] 清晨:**
Would a reference implementation help speed up adoption?

**[16:23] 格物谷:**
Count me in for testing or feedback.

**[17:24] 汉雨唐落:**
Great discussion! Here is what we have so far:

✅ Engine Plugin Expansion - Community feedback collected
✅ More discussion needed - Continue on dev list
✅ Volunteers welcome - Join the conversation

Sending this to the dev mailing list to get more community input.
Everyone is welcome to chime in!


---
Best regards,
Apache Linkis Community Member

Note: This is an automated discussion starter to engage community members.
Reply to this email to continue the discussion on the dev mailing list.

Apache Linkis - https://linkis.apache.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to