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

New auto index creation only works in IN_MEMORY_TRANSACTIONAL #742

Closed
gcleaves opened this issue May 4, 2024 · 2 comments · Fixed by #743
Closed

New auto index creation only works in IN_MEMORY_TRANSACTIONAL #742

gcleaves opened this issue May 4, 2024 · 2 comments · Fixed by #743
Assignees
Labels
priority: high (error) A mistake in the documentation, or information that is crucial for a correct flow

Comments

@gcleaves
Copy link

gcleaves commented May 4, 2024

Memgraph version
2.16.0

Environment
Docker

Describe the bug
The new auto indexing options only seem to work in IN_MEMORY_TRANSACTIONAL. This is not mentioned in the docs, at least as far as I can see.

To Reproduce
Start Memgraph with --storage-automatic-edge-type-index-creation-enabled=true and --storage-automatic-label-index-creation-enabled=true.
Set the storage mode to IN_MEMORY_ANALYTICAL.
Create a node with a label.
No index is created.

Expected behavior
Either documentation should specify that this scenario doesn't work, or it should work.

Logs

Additional context

Verification Environment

@antejavor antejavor transferred this issue from memgraph/memgraph May 6, 2024
@antejavor
Copy link
Contributor

antejavor commented May 6, 2024

Hi @gcleaves, I have transferred this issue from the Memgraph repo to the docs repo since it is mostly docs related.

cc @kgolubic, @gvolfing, it looks like we have some missing content around automatic index creation.

@kgolubic kgolubic self-assigned this May 6, 2024
@kgolubic kgolubic added the priority: high (error) A mistake in the documentation, or information that is crucial for a correct flow label May 6, 2024
@kgolubic kgolubic linked a pull request May 6, 2024 that will close this issue
10 tasks
@kgolubic
Copy link
Collaborator

kgolubic commented May 6, 2024

Thank you @gcleaves for reporting this. I will update the docs right away :)

#743

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: high (error) A mistake in the documentation, or information that is crucial for a correct flow
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants