fix(server): switch rocksdb backend to memory when executing gremlin example #2518
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
An error occurs when using Gremlin-Console Stand-alone in offline mode:
Due to difficulty in pinpointing the cause and considering the above scenario as an example only, the RocksDB backend will be changed to the memory backend.
@imbajin Perhaps the documentation at https://hugegraph.apache.org/docs/clients/gremlin-console/ also needs corresponding adjustments. It is not recommended for users to use it in production environments and is intended for example purposes only.