[
https://issues.apache.org/jira/browse/IGNITE-6611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253200#comment-16253200
]
Sergey Kalashnikov commented on IGNITE-6611:
--------------------------------------------
In order to facilitate the implementation of SQL "ALTER TABLE DROP COLUMN"
functionality the following changes are proposed to the binary metadata.
1) Add special metadata type and an API to explicitly add/remove fields rather
than implictly pull in every new field occurring in data.
This API will be utilized by the DDL.
2) Changes in this new metadata type shall be tracked on per-cache basis. Each
change is to be assigned a version.
3) Serialization/deserialization shall transform the old data so that it is
complying to the current metadata version.
4) The metadata version can be attributed to the binary object with the help of
schema id (i.e. version is to be stored in binary schema)
> Optionally disable binary metadata for type
> -------------------------------------------
>
> Key: IGNITE-6611
> URL: https://issues.apache.org/jira/browse/IGNITE-6611
> Project: Ignite
> Issue Type: Task
> Components: binary, sql
> Affects Versions: 2.3
> Reporter: Vladimir Ozerov
> Assignee: Sergey Kalashnikov
> Fix For: 2.4
>
>
> We need to introduce special metadata mode for type - without metadata. This
> way we will have a kind of "flexible" type with no restrictions. This will be
> especially useful for SQL-related types where schema changes are possible
> (e.g. ADD COLUMN -> DROP COLUMN).
> Public part should be exposed to:
> 1) {{BinaryTypeConfiguration}}
> 2) {{BinaryType}} - add a flag here.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
