[
https://issues.apache.org/jira/browse/IGNITE-15833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-15833:
---------------------------------------
Description:
During this task we need to provide minimal yet sufficient interfaces to make
extension possible. Followed aspects should be covered:
# Interface of the plugin (draft could be found in parent ticket)
# Interface to implement by relational nodes. Looks like we have to use
IgniteRel here, but it comes at cost of lost validation: IgniteConvention uses
this interface to validate the convention is set for proper rel. Need to think
about this.
# Interface of the schema. In the prototype the
org.apache.calcite.schema.SchemaPlus is used, but it doesn't look as a good
decision.
was:
During this task we need to provide minimal yet sufficient interfaces to make
extension possible. Followed aspects should be covered:
# Interface of the plugin (draft could be found in parent ticket)
# Interface to implement by relational nodes. Looks like we have to use
IgniteRel here, but it comes at cost of lost validation: IgniteConvention uses
this interface to validate the convention is set for proper rel. Need to think
about this.
# Interface for external table (IgniteExternalTable). It could be reduced
IgniteTable.
# Interface of the schema. In the prototype the
org.apache.calcite.schema.SchemaPlus is used, but it doesn't look as a good
decision.
# Currently TableDescriptor contains link to TableImpl and methods to convert
from tuple to row and vice versa, thus some refactoring is required
> Provide interfaces for SQL Extension API
> ----------------------------------------
>
> Key: IGNITE-15833
> URL: https://issues.apache.org/jira/browse/IGNITE-15833
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Konstantin Orlov
> Priority: Major
>
> During this task we need to provide minimal yet sufficient interfaces to make
> extension possible. Followed aspects should be covered:
> # Interface of the plugin (draft could be found in parent ticket)
> # Interface to implement by relational nodes. Looks like we have to use
> IgniteRel here, but it comes at cost of lost validation: IgniteConvention
> uses this interface to validate the convention is set for proper rel. Need to
> think about this.
> # Interface of the schema. In the prototype the
> org.apache.calcite.schema.SchemaPlus is used, but it doesn't look as a good
> decision.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
