[
https://issues.apache.org/jira/browse/CALCITE-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17816467#comment-17816467
]
EveyWu commented on CALCITE-6257:
----------------------------------
hi [~caicancai]
Similar to Presto and Trino, I don't think it's necessary to implement two sets
of dialects at the moment.
Since Starrocks is more widely used currently, I chose to implement the
StarRocks Dialect.
> StarRocks dialect implementation
> --------------------------------
>
> Key: CALCITE-6257
> URL: https://issues.apache.org/jira/browse/CALCITE-6257
> Project: Calcite
> Issue Type: New Feature
> Reporter: EveyWu
> Priority: Minor
> Labels: pull-request-available
>
> StarRocks has an MPP architecture and is equipped with a fully vectorized
> execution engine, a columnar storage engine that supports real-time updates.
> [https://docs.starrocks.io/docs/introduction/StarRocks_intro/]
> At present, StarRocks has a wide range of applications. Implementing dialect
> in Calcite will be valuable for many bi-services.
> It closely follows MySQL but has enough differences to warrant a separate
> dialect in Calcite.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
