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

Making Neo4J remote provider work #157

Open
steotia opened this issue Jun 1, 2018 · 1 comment
Open

Making Neo4J remote provider work #157

steotia opened this issue Jun 1, 2018 · 1 comment
Labels
legacy Issues reported on the legacy implementations

Comments

@steotia
Copy link
Contributor

steotia commented Jun 1, 2018

No description provided.

@steotia
Copy link
Contributor Author

steotia commented Jun 1, 2018

It seems the queries are OLAP in nature, due to which performance will be poor and more importantly, the remote Neo4J driver does not support OLAP optimizations.
Converting the way we ID and putting in ability to run OLTP queries against an indexed system.

steotia added a commit that referenced this issue Jul 5, 2018
@indrajra indrajra added the legacy Issues reported on the legacy implementations label Dec 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
legacy Issues reported on the legacy implementations
Projects
None yet
Development

No branches or pull requests

2 participants