Open ryber opened 2 years ago
For right now I have made by own stub classes of the following to allow myself to exclude the glue lib and continue to use this library for my original purpose:
com.amazonaws.services.schemaregistry.common.Schema com.amazonaws.services.schemaregistry.common.configs.GlueSchemaRegistryConfiguration com.amazonaws.services.schemaregistry.serializers.GlueSchemaRegistrySerializer com.amazonaws.services.schemaregistry.serializers.GlueSchemaRegistrySerializerImpl
Some of these I had to stub out the constructors and a method or two just so I could new up KinesisProducer.
Using Lombock is sabotage - it greatly interferes with navigation through the code as well as debugging ... "invisible" getters and setters, as well as constructors! For now many AWS libraries uses this Lombock ... this is very bad...
KPL is not a product that you can take and just use. I spent many hours debugging and researching the code!
Especially this https://github.com/awslabs/amazon-kinesis-producer/issues/48 (our team freaked out from that issue)
Hello, I recently updated from amazon-kinesis-producer 0.14.1 to 0.14.12
This dramatically increases the number of transient dependencies I am now responsible for, mostly for the Glue stuff that I don't use, but I am forced to be dependent on due to new methods on IKinesisProducer
This includes such things as:
This dependency should be option and even then, within that things like scala and kotlin should also be optional. Forcing your consumers to be dependent on something as totally unnecessary as Lombock is just kind of rude.
Full list of dependencies: