json.Unmarshal error on migrating_slot field

[greatsharp]

{"level":"error","timestamp":"2025-05-10T10:32:12.921+0800","caller":"controller/cluster.go:289","msg":"Failed to get the clusterName info from the clusterStore","namespace":"test","clusterName":"test","error":"cluster: json: cannot unmarshal number into Go struct field .Alias.shards.migrating_slot of type string","stacktrace":"github.com/apache/kvrocks-controller/controller.(*ClusterChecker).probeLoop\n\t/opt/go-src/kvrocks-controller/controller/cluster.go:289"}

[greatsharp]

[greatsharp]

The new processing logic is not compatible with the old data.

[greatsharp]

@bseto take a look please

[PragmaTwice]

So it's a breaking change in API? cc @git-hulk

[bseto]

Hmm I might have missed something. Sorry about that. Do you have a repeatable workflow?

The migrating slot used to be an int, so it will be compatible with the slot struct, but I might have missed something somewhere.

Il take a look when I'm home later!

[git-hulk]

The new processing logic is not compatible with the old data.

@greatsharp Thanks for your catch.

So it's a breaking change in API? cc @git-hulk

We can be compatible with the old data when unmarshaling the data.

The migrating slot used to be an int, so it will be compatible with the slot struct, but I might have missed something somewhere.

Don't worry about this; we don't have a test case for now. I also missed this part.

[git-hulk]

Closed by #310