Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Manage ComplexType both into the engine and in serializers #445

@masesdevelopers

Description

@masesdevelopers

Is your feature request related to a problem? Please describe.
Current behavior does not differentiate between Entity, Owned and Complex types. For the first two types the system works well, however ComplexTypes are not managed as expected (extra columns in the schema associated to the main Entity type).
This kind of type shall be managed as pure nested type i.e. their serialized value shall be the value of the property they belongs.

Describe the solution you'd like
When the entity is analyzed to identify the referenced entities the engine shall search for Complex types and avoid the generation of a distinct Kafka topic.
When serializer identify the property is a complex type they shall define:

  • the ManagedType associated to the property shall be a new value like ComplexType
  • an inner IValueContainer shall be associated to the Value property and its content shall be deducted from the properties of the ComplexType
  • and this shall be made recursively.

Add a callback on serializers, so when this kind of type are encountered it is possible to receive a serialization request outside the main one described above,

Describe alternatives you've considered
N/A

Additional context
This feature shall be made available for KNetOPC since OPC-UA comes from rich type system, however each type is managed with specialized serializer offered from OPC-UA itself.

Metadata

Metadata

Labels

.NETPull requests that update .net codeKEFCoreThe issue is releated to KEFCoreKEFCore SerDesThe issue is releated to KEFCore SerDesenhancementNew feature or request
No fields configured for Feature.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions