[
https://issues.apache.org/jira/browse/IGNITE-26505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-26505:
--------------------------------------
Labels: IEP-119 (was: )
> IEP-119 Binary configuration improvement
> ----------------------------------------
>
> Key: IGNITE-26505
> URL: https://issues.apache.org/jira/browse/IGNITE-26505
> Project: Ignite
> Issue Type: Improvement
> Reporter: Nikolay Izhikov
> Priority: Major
> Labels: IEP-119
>
> Essentially, binary subsystem must have one "interface" implementation
> This interface must provide a way to deal with binary meta and marshaller
> information
> * CRUD for binary types.
> * CRUD for marshaller mappings
> Default implementation must works with IGNITE_WORK/binary_meta,
> IGNITE_WORK/marshaller directories content.
> Looks like this can be independent from other code and don't require kernal
> context.
> Having those kind of abstraction will simplify tools code - cdc, wal reader,
> dump reader, etc.
>
> Thin client implementation must query this information from cluster.
>
> Currently, this abstraction hidden in core and thin client code.
> In this ticket we want to provide clear abstraction on binary infrastructure
> initialization and runtime behavior.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
