I read the CALCITE-6908. KVRocks is compatible with the Redis protocol. Does this mean existing Redis adapters can be adapted to KVRocks without needing to implement a new one? Because currently, having too many redundant adapters doesn't seem to offer much value. I'm unsure how many of the adapters Calcite currently has are actually used in production.
Best regards, Zhen ---- Replied Message ---- | From | Cancai Cai<[email protected]> | | Date | 5/16/2026 10:22 | | To | <[email protected]> | | Subject | Re: Release 1.42 | There's actually another new adapter available for review: https://issues.apache.org/jira/browse/CALCITE-6908. If the community accepts this proposal, I can ask the kvrocks community to help review it. Best wishes, Cancai On 2026/05/15 13:19:55 Stamatis Zampetakis wrote: Thanks to Francis Avatica 1.28.0 is out and Calcite is already upgraded! A few minutes ago, I reviewed the tickets marked for 1.42.0 release [1] and requested feedback to see how many of them we can include. For most of these, I think we will converge easily in the coming days. However, CALCITE-7353 [2] proposes a new adapter for the project and so far we haven't provided any feedback to the contributor. I am not familiar with Milvus, so I wanted to see how people feel about adding the adapter to our code base. Please share your thoughts on the ticket. Best, Stamatis [1] https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333950 [2] https://issues.apache.org/jira/browse/CALCITE-7353 On Tue, Apr 28, 2026 at 10:43 AM Francis Chuang <[email protected]> wrote: I will start a thread for releasing Avatica 1.28.0, so we can get a release out before Calcite 1.42.0 Francis On 28/04/2026 4:30 pm, Stamatis Zampetakis wrote: Hey everyone, I was planning to take on the Calcite 1.43.0 release but given that we have no volunteers for 1.42.0 I can switch to that one. Regarding timing, I can cut the first release candidate sometime during the week of May 18. This allows a little over 2 weeks for finalizing and merging pending PRs to main. We currently have over 200 unreleased commits in main so if we don't have any significant blockers or regressions, I would suggest not to push the release cut too much in the future. I see a few pending issues in the release dashboard [1] but nothing is very urgent. Please set the Fix Version accordingly for anything that must be in the next release. Although not mandatory, releasing Avatica before then would be beneficial since it has been a while since the last release. Best, Stamatis [1] https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333950 On Mon, Apr 27, 2026 at 1:19 PM ткаленко кирилл <[email protected]> wrote: Any news?
