Four system streams with _0 generated after upgrading

[kuiliu88]

Steps to reproduce:
deploy the previous version to k8s:

$ helm -n system-test install --wait --wait-for-jobs -f values-3.0.yaml timeplus timeplus-enterprise-v10.0.9.tgz
I0225 09:33:10.357335    2453 warnings.go:110] "Warning: BCID failed open: BCID Constraint disabled by Giraffe"
NAME: timeplus
LAST DEPLOYED: Wed Feb 25 09:33:04 2026
NAMESPACE: system-test
STATUS: deployed
REVISION: 1
DESCRIPTION: Install complete
TEST SUITE: None
NOTES:
Your Timeplus Enterprise stack is deployed! It may take a few minutes before all the services are up and running.

do upgrade

$ helm -n system-test upgrade --wait --wait-for-jobs -f values-3.0.yaml timeplus timeplus-enterprise-v11.0.4.tgz
wait-for-jobs -f values-3.0.yaml timeplus timeplus-enterprise-v11.0.4.tgz       
Release "timeplus" has been upgraded. Happy Helming!
NAME: timeplus
LAST DEPLOYED: Wed Feb 25 09:02:19 2026
NAMESPACE: system-test
STATUS: deployed
REVISION: 2
DESCRIPTION: Upgrade complete
TEST SUITE: None
NOTES:
Your Timeplus Enterprise stack is deployed! It may take a few minutes before all the services are up and running.

[ye11ow]

@yuzifeng1984 this seems to be a timeplusd issue as well. Can you please check?
@kuiliu88 can you please list the timeplusd version before and after upgrade?

[yuzifeng1984]

@kuiliu88 can you attach the logs?

This is expected behavior when the stream DDL is changed. Can you run 'SHOW CREATE STREAM' before and after the upgrade? And paste the DDLs. These streams are defined in server config.yaml while I did not find any recent changes on these.

[yuzifeng1984]

timeplusd log should have something like below in renaming the stream

Existing table {} for system log has obsolete or different structure. Renaming it to {}.\nOld: {}\nNew: {}\n