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
Is it OK that parameters related to unreleased features are returned? For example in the result of SHOW CREATE SPACE basketballplayer, atomic_edge and ON default are displayed, but the corresponding features are not ready and not release in any Nebula Graph version.
Shouldn't there be rules to regulate such cases?
nebula) [basketballplayer]> SHOW CREATE SPACE basketballplayer;
+--------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Space | Create Space |
+--------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| "basketballplayer" | "CREATE SPACE `basketballplayer` (partition_num = 10, replica_factor = 1, charset = utf8, collate = utf8_bin, vid_type = FIXED_STRING(32), atomic_edge = false) ON default" |
+--------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
Users won't know what theses parameters are here for unless they dig into the source code. This kind of experience is really not good.
The text was updated successfully, but these errors were encountered:
Nebula Graph version: v2.5.0
Is it OK that parameters related to unreleased features are returned? For example in the result of
SHOW CREATE SPACE basketballplayer
,atomic_edge
andON default
are displayed, but the corresponding features are not ready and not release in any Nebula Graph version.Shouldn't there be rules to regulate such cases?
Users won't know what theses parameters are here for unless they dig into the source code. This kind of experience is really not good.
The text was updated successfully, but these errors were encountered: