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

Deprecation warnings from neo4j: "The query used a deprecated function: id" #291

Open
dotsdl opened this issue Aug 20, 2024 · 0 comments · May be fixed by #302
Open

Deprecation warnings from neo4j: "The query used a deprecated function: id" #291

dotsdl opened this issue Aug 20, 2024 · 0 comments · May be fixed by #302
Assignees

Comments

@dotsdl
Copy link
Member

dotsdl commented Aug 20, 2024

It appears that our use of neo4j 5.18+ yields a ton of deprecation warnings similar to:

WARNING  neo4j.notifications:result.py:321 Received notification from DBMS server: {severity: WARNING} {code: Neo.ClientNotification.Statement.FeatureDeprecationWarning} {category: DEPRECATION} {title: This feature is deprecated and will be removed in future versions.} {description: The query used a deprecated function: `id`.} {position: line: 5, column: 8, offset: 130} for query: "UNWIND $data AS r\nMERGE (_:GufeTokenizable {_scoped_key:r['_scoped_key']})\nSET _ += r\nSET _:DummyProtocolB:GufeTokenizable\nRETURN id(_)"

The complaint comes from the use of id(_) at the end of the query, and likely originates from our subgraph machinery in alchemiscale.storage.subgraph.

Is there an alternative to using this function that still gives us what we need for SubGraph behavior?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Sprint - Available
2 participants