Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Docs Required, Release Notes Required
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
Attachments
Issue Links
- blocks
-
IGNITE-18922 Thin 3.0: Avoid BinaryTuple conversion in client SQL handler
- Open
- is a parent of
-
IGNITE-19860 Migrate SQL module to BinaryTuple
- Open