Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vertex details committed to storage despite the failure from Cassandra, and Rollback didn't help #3996

Open
sumandas0 opened this issue Sep 20, 2023 Discussed in #3978 · 0 comments

Comments

@sumandas0
Copy link

Discussed in #3978

Originally posted by sumandas0 September 13, 2023
We use a string as a composite index in our primary storage, Cassandra. However, when we send a large string, we encounter the following error: "Caused by: java.util.concurrent.ExecutionException: com.datastax.oss.driver.api.core.servererrors.InvalidQueryException: Key length of 67871 is longer than the maximum of 65535." This is understandable. The real issue arises afterward: even when this error is thrown, the data is still written to the graph store and becomes searchable by a few indices. The behavior is inconsistent; sometimes the data can be searched using certain attributes, and sometimes it cannot. When we attempt a rollback on the same transaction after detecting the exception, the previously written values aren't rolled back. This has significantly disrupted the indexing in our application. We understand the error, but why are incorrect indices being written?

Janusgraph Version: 6.0.0
Storage Backend: Cassandra
Index Backend: Elasticsearch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant