Connect parameters not considered in cycleReferences cache

[carlesarnal]

In AvroData with a struct like the following

{
        "type" : "struct",
        "fields" : [ {
          "type" : "int32",
          "optional" : false,
          "field" : "scale"
        }, {
          "type" : "bytes",
          "optional" : false,
          "field" : "value"
        } ],
        "optional" : true,
        "name" : "io.debezium.data.VariableScaleDecimal",
        "version" : 1,
        "doc" : "Variable scaled decimal",
        "parameters" : {
          "precision" : "10"
        },
        "field" : "VAL_F_10"
 }

There will be a cache hit in fromConnectContext.cycleReferences even if the parameters value is different. We must investigate using a different key (maybe the entire schema?).

[rk3rn3r]

Hey @carlesarnal, may I ask you what's the status of this one? We are getting some more complaints about this issue from Debezium users and while I am working on a temporary workaround it would be good if that could be fixed soon. I might be able to look into it myself after I finished the workaround, but maybe you have a pointer for me? I think I look for fromConnectContext.cycleReferences() for the cache acccess?

[carlesarnal]

Hey,

No status, sorry. This is acknowledged but we haven't had the time to go through it yet. What you mention is the perfect start, unfortunately, I don't have any other insight into this one.