[
https://issues.apache.org/jira/browse/CALCITE-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Beikov updated CALCITE-2141:
--------------------------------------
Description:
Based on topology changes, it should be possible to dynamically update a
sharding configuration for calcite. The effect of such a configuration is, that
a query involving sharded tables is rewritten to a more optimal form possibly
targetting mutliple different datasources.
This is an interesting building block for distributed databases but also for
applications since it enables the implementation of a static sharding scheme.
Doing the shard rewriting on a client is also a lot better when using a
distributed database as that eliminates the need for a coordinator node through
which data is tunneled.
Also see [https://github.com/shardingjdbc/sharding-jdbc] for an existing
implementation.
was:
Based on topology changes, it should be possible to dynamically update a
sharding configuration for calcite. The effect of such a configuration is, that
a query involving sharded tables is rewritten to a more optimal form possibly
targetting mutliple different datasources.
This is an interesting building block for distributed databases but also for
applications since it enables the implementation of a static sharding scheme.
Doing the shard rewriting on a client is also a lot better when using a
distributed database as that eliminates the need for a coordinator node through
which data is tunneled.
> Implement query rewrite based on sharding configuration
> -------------------------------------------------------
>
> Key: CALCITE-2141
> URL: https://issues.apache.org/jira/browse/CALCITE-2141
> Project: Calcite
> Issue Type: New Feature
> Reporter: Christian Beikov
> Assignee: Julian Hyde
> Priority: Minor
>
> Based on topology changes, it should be possible to dynamically update a
> sharding configuration for calcite. The effect of such a configuration is,
> that a query involving sharded tables is rewritten to a more optimal form
> possibly targetting mutliple different datasources.
> This is an interesting building block for distributed databases but also for
> applications since it enables the implementation of a static sharding scheme.
> Doing the shard rewriting on a client is also a lot better when using a
> distributed database as that eliminates the need for a coordinator node
> through which data is tunneled.
> Also see [https://github.com/shardingjdbc/sharding-jdbc] for an existing
> implementation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
