You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Considering #12442, let's add a database version number concept in OAP codebase. Once we have this in place, we have a chance to do incompatible upgrade through two group.
e.g. banyandb_db_schema_v = 1, and we need some incompatible upgrade, introduced a new kind of index, but the query logic is consistent. We could do banyandb_db_schema_v=2(compatible with banyandb_db_schema_v=1).
Then, when we apply definition change through create new schema_v suffix groups.
The text was updated successfully, but these errors were encountered:
Considering #12442, let's add a database version number concept in OAP codebase. Once we have this in place, we have a chance to do incompatible upgrade through two group.
e.g. banyandb_db_schema_v = 1, and we need some incompatible upgrade, introduced a new kind of index, but the query logic is consistent. We could do banyandb_db_schema_v=2(compatible with banyandb_db_schema_v=1).
Then, when we apply definition change through create new schema_v suffix groups.
The text was updated successfully, but these errors were encountered: