Roy Dahan
Roy Dahan
@avelanarius we need someone to look at it, this is failing in 2024.1 and we need to know why and how severe it is.
> Please assign someone to review the upgrade procedure. 6.0 wasn’t branched yet and not tested yet, so we can’t provide any feedback yet on the procedure.
I think that the fix from @dkropachev was not merged in the upstream but was merged for scylla (or at least that was the plan).
@dkropachev assuming we are ok with the diverge between the two, how hard would it be to support the nested structures?
@dkropachev do you think you'll be able to fit this task sometime soon?
Thanks @dkropachev, it may become high priority for us at the moment, I'll check our options around that.
> > Should the fix be sent to https://github.com/gocql/gocql first? > > Not sure about that. It looks like the upstream is not actively maintained, and this change is not...
@dkropachev how easy to fix?
@enaydanov IIUC it reproduced the issue?
In general I agree, but the problem is that it repeats itself in many places, appearing as an ERROR to the users who are bothered with it and report it...