Fixed asyncMemory importing from incorrect Memorygraph class making m…

[thestumonkey]

trafficstars

…emgraph not work

Description

Currently with AsyncMemory and memgraph it imports the neo4j version of the graph memeory and consequently fails because it expects a database, and you can't give it a database.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

I have not tested this as I have not successfully managed to get a locally built instance to work with my infra. I have just followed the pattern which exists in Memory and applied to AsyncMemory.

To reproduce issue:

• Setup memgraph as described in docs
• Create an AsyncMemory with a config that includes a memgraph config
• config["graph_store"] = { "provider": "memgraph", "config": { "url": "bolt://memgraph:7687", } }
• Build the container / project
• Observe it complains about database not being a valid attribute

Please delete options that are not relevant.

• [ ] Unit Test
• [ ] Test Script (please provide)

Checklist:

• [ ] My code follows the style guidelines of this project
• [ ] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] New and existing unit tests pass locally with my changes
• [ ] Any dependent changes have been merged and published in downstream modules
• [ ] I have checked my code and corrected any misspellings

Maintainer Checklist

• [ ] closes #xxxx (Replace xxxx with the GitHub issue number)
• [ ] Made sure Checks passed

[CLAassistant]

All committers have signed the CLA.