[
https://issues.apache.org/jira/browse/IGNITE-17684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-17684:
---------------------------------------
Description:
Right now internaly we use array of objects to represent row in SQL instead of
BinaryTuple and do unnecessary convertation.
Let's investigate possibility migration from array of objects to direct usage
of BinaryTuple in execution tree. There are possible issue for some type
execution, like a twophase aggregates and potentialy we should use different
representation of row for different parts.
Start points are:
org.apache.ignite.internal.sql.engine.exec.ArrayRowHandler
org.apache.ignite.internal.sql.engine.schema.IgniteTableImpl#toRow
As result of the task - list of issues which need to be resolved to implement
reuse BinaryTuple
was:
Right now internaly we use array of objects to represent row in SQL instead of
BinaryTuple and do unnecessary convertation.
Let's investigate possibility migration from array of objects to direct usage
of BinaryTuple in execution tree. There are possible issue for some type
execution, like a twophase aggregates and potentialy we should use different
representation of row for different parts.
Start points are:
org.apache.ignite.internal.sql.engine.exec.ArrayRowHandler
org.apache.ignite.internal.sql.engine.schema.IgniteTableImpl#toRow
As result of the task - list of issues which need to be resolved to implement
reuse BinaryTyple
> Investigate of using BinaryTuple instead of array of objects in SQL execution
> -----------------------------------------------------------------------------
>
> Key: IGNITE-17684
> URL: https://issues.apache.org/jira/browse/IGNITE-17684
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Yury Gerzhedovich
> Priority: Major
> Labels: ignite-3, tech-debt
>
> Right now internaly we use array of objects to represent row in SQL instead
> of BinaryTuple and do unnecessary convertation.
> Let's investigate possibility migration from array of objects to direct usage
> of BinaryTuple in execution tree. There are possible issue for some type
> execution, like a twophase aggregates and potentialy we should use different
> representation of row for different parts.
> Start points are:
> org.apache.ignite.internal.sql.engine.exec.ArrayRowHandler
> org.apache.ignite.internal.sql.engine.schema.IgniteTableImpl#toRow
> As result of the task - list of issues which need to be resolved to implement
> reuse BinaryTuple
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
