opwvhk commented on PR #356: URL: https://github.com/apache/avro/pull/356#issuecomment-2107284969
The nasty bit about generics is that they make the data definition fluid. This is a good thing in code: it allows you to create a template and apply it multiple times without duplication. For data however, it creates problems: your code can only cater to the lowest common denominator, but must keep all data intact as well. Usually, it's a more resilient approach to create a list of typed records (what an Avro `map` internally is as well). This is also why I second the comment of @martin-g: "It seems like RecordSchema is almost capable to cover the need.". In fact, with only little adjustment I think it is capable of covering almost all needs. -- 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: issues-unsubscr...@avro.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
