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
{{ message }}
Repository navigation
[Bug] Inconsistent driver version null error in Cassandra 4.x #2282
@imbajin ok I found the root cause and some workaround:
root cause is that I called clearGraph() function in the code, so that I can clean up the graph and start from scratch.
however the clearGraph() function also truncated the cassandra table m which holds the meta info like version. hugeClient.graphs().clearGraph("hugegraph", "I'm sure to delete all data")
then to fix this I did: insert into m(name, value) values ('VERSION', '1.11');
this repopulates the version to the version that driver expected.
and now my servers start up with no issue.
the proper fix would be exclude table m in the purge procedure.
@imbajin ok I found the root cause and some workaround:
root cause is that I called clearGraph() function in the code, so that I can clean up the graph and start from scratch.
however the clearGraph() function also truncated the cassandra table m which holds the meta info like version. hugeClient.graphs().clearGraph("hugegraph", "I'm sure to delete all data")
then to fix this I did: insert into m(name, value) values ('VERSION', '1.11');
this repopulates the version to the version that driver expected.
and now my servers start up with no issue.
the proper fix would be exclude table m in the purge procedure.
@linehrr thanks for the useful feedback/details, we'll add the truncate case in unit-test & enhance the clear/drop graph logic(also it's good task for the new contributor)
Activity
[-][Bug] describe the main problem[/-][+][Bug] Inconsistent driver version null error in Cassandra 4.x[/+]linehrr commentedon Apr 18, 2024
same issue encountered also in server version 1.3.0.
imbajin commentedon Apr 18, 2024
@linehrr Thanks for your feedback, could u provide the minimum reproduction process for us? (we could fix it soon)
And if it restarts the server when it does not import data, it will return to OK/normal?
linehrr commentedon Apr 18, 2024
@imbajin ok I found the root cause and some workaround:
root cause is that I called clearGraph() function in the code, so that I can clean up the graph and start from scratch.
however the clearGraph() function also truncated the cassandra table
mwhich holds the meta info like version.hugeClient.graphs().clearGraph("hugegraph", "I'm sure to delete all data")then to fix this I did:
insert into m(name, value) values ('VERSION', '1.11');this repopulates the version to the version that driver expected.
and now my servers start up with no issue.
the proper fix would be exclude table
min the purge procedure.imbajin commentedon Apr 18, 2024
@linehrr thanks for the useful feedback/details, we'll add the truncate case in unit-test & enhance the clear/drop graph logic(also it's good task for the new contributor)
@dosu-bot could u response for this legacy issue?
Pengzna commentedon May 14, 2025
In newest version, we remove the support for using Cassandra as backend, see #2746
The problem of the old version is waiting for the user to PR repair and submit it to a specific branch (like
1.3.0)