[
https://issues.apache.org/jira/browse/CALCITE-6908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18081628#comment-18081628
]
Stamatis Zampetakis commented on CALCITE-6908:
----------------------------------------------
[~caicancai] Who is using (or planning to use) this adapter? We can certainly
introduce adapters over many engines/platforms/APIs but we can obviously cannot
do it for everything. I see two motivations for introducing a new adapter:
1. Popular system used by many companies/products/projects that requires a SQL
interface
2. Novel integration work that highlights/exposes Calcite APIs not extensively
used by existing code/adapters.
Does the proposed adapter fall into one of the aforementioned categories? Who
is going to benefit it from it? What's the major novelty/difference compared to
the Redis adapter?
> Apache Kvrocks adapter
> ----------------------
>
> Key: CALCITE-6908
> URL: https://issues.apache.org/jira/browse/CALCITE-6908
> Project: Calcite
> Issue Type: New Feature
> Reporter: Caican Cai
> Assignee: Caican Cai
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.42.0
>
>
> Apache Kvrocks is a distributed key value NoSQL database that uses RocksDB as
> storage engine and is compatible with Redis protocol and And kvrocks also
> supports querying data through sql , we can adapt it, maybe most of it is
> similar to the redis adapter. But I may want to write a new module and
> refactor and solve some problems of the current redis adapter, such as
> adapting redis sql and compatibility with more redis commands.
> https://github.com/apache/kvrocks
> https://kvrocks.apache.org/docs/supported-commands#search-commands
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
