Replies: 1 comment 1 reply
-
changing INTEGER to VARCHAR may take time - TimeBase will rewrite all messages (since we have strict schema for each message) You will have to wait, progress only visible in Web Administrator. Best recommendation for you - do not kill TimeBase, unless you cannot connect to it. Could you please send me TimeBase logs to see what was happened? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I was changing the data type of a stream field from INTEGER to VARCHAR using MODIFY with CONFIRM CONVERT_DATA.
TimeBase got stuck and shell got hanged. APIs were failing for ALL streams.
Note: Stream has 2 spaces with each 500mb of data( TimeBase memory)
So I killed all the process ids. Then restarted TimeBase. ALL stream were present, but I lost my few most recent spaces(loaded 3 4 days ago) for multiple streams.
Can you please let me know is it expected/known behavior of TimeBase? What could be possible way out of retaining the data and why this is happenning?
Is it not possible to change the stream field data type with that much size of data?
Beta Was this translation helpful? Give feedback.
All reactions