SemyonSinchenko commented on issue #707:
URL:
https://github.com/apache/incubator-graphar/issues/707#issuecomment-3138507115
> Hi @SemyonSinchenko ,
>
> I've been thinking more about these enums, and I think they represent
`type.id`, they only carry the basic type identifier without nesting
information. The nested structure is represented in the `children` field. (e.g.
`Type{id=DataType::LIST, children=Type{id=DataType::BOOL, children=NULL}}`
representes `List<Bool>`).
> I'm curious what is the intended purpose of using protobuf here? Is to
standardize how different language bindings parse type information from the
`YAML` schema?
The initial idea of using protobuf was to provide a way to work with
stabdard ser-de. In theory, protobuf can be converted to JSON and most tools
can convert JSON to YAML. And back too. Like different languages should not
maintain models of metadata files internally but just re-use these proto that
can be published as a package.
But further we are going, Im thinking that more and more the idea failed and
we should just drop these protos. For example, the whole new Java API
re-creates all the models on top of these protos anyway and protos doesnt
simplify the story but add complexity.
cc: @acezen @Thespica
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
