[
https://issues.apache.org/jira/browse/AVRO-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Khrystyna Popadyuk updated AVRO-3603:
-------------------------------------
Description:
Hi Apache.Avro,
I am working with ReflectReader/Writer on my current project. It gives a lot of
benefits. However they also have some limitations and add any, even the
smallest changes,require update Apache.Avro nuget package. It is OK for me to
contribute to Apache.Avro but there are two big issue:
- very long development cycle. I am working for company that utilize CI/CD and
want to get features as soon as possible. But it is impossible to get new
Apachy.Avro package quickly.
- there are features that is very specific for concrete project (automatically
convert property names to snake_case)
As solution, I suggest that we can introduce interfaces and allow users
overload default behaviors.
Hope it would be useful for other too.
was:
Current ReflectReader/Writer use a lot of static entities (classes, methods,
fields). It is good to refactor them with interfaces and DI approach.
If do such update at once it requires massive changes and can we difficult to
review and test.
This story is created as first step for such refactoring. It will include:
- group classes by folders
- add DI
- rename and refactor ClassCash and EnumCache (avoid method refactoring in
scope of this story)
This story do not update method implementation.
This is breaking changes.
> .NET/#C: Refactor ReflectReader/Writer: add interfaces
> ------------------------------------------------------
>
> Key: AVRO-3603
> URL: https://issues.apache.org/jira/browse/AVRO-3603
> Project: Apache Avro
> Issue Type: Improvement
> Reporter: Khrystyna Popadyuk
> Assignee: Khrystyna Popadyuk
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Hi Apache.Avro,
> I am working with ReflectReader/Writer on my current project. It gives a lot
> of benefits. However they also have some limitations and add any, even the
> smallest changes,require update Apache.Avro nuget package. It is OK for me to
> contribute to Apache.Avro but there are two big issue:
> - very long development cycle. I am working for company that utilize CI/CD
> and want to get features as soon as possible. But it is impossible to get new
> Apachy.Avro package quickly.
> - there are features that is very specific for concrete project
> (automatically convert property names to snake_case)
> As solution, I suggest that we can introduce interfaces and allow users
> overload default behaviors.
> Hope it would be useful for other too.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
