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

add elementID in apoc.convert.toTree output as key-value pair (_elementId) #3886

Open
dorn-gerhard opened this issue Jan 1, 2024 · 1 comment
Labels
core-functionality Adding new procedure, function or signature to APOC core

Comments

@dorn-gerhard
Copy link

Feature description (Mandatory)

As the use of ID is not recommended and instead elementId should be used in future it would be convenient to have an additional key-value pair _elementId in the output of the apoc.convert.toTree method.

In addition it would be convenient to make _id, _elementId and _type suppressable via the config:
{ nodes: {'Labelname': ['-_id', ...]}}

Considered alternatives

Alternatives would be to work with ID or to add a unique ID to all nodes.

@gem-neo4j
Copy link
Contributor

Hi! Thank you for writing in, I have added this suggestion to our work on migrating APOC to be more elementId friendly

@jexp jexp moved this to Todo in APOC Extended Larus Jan 11, 2024
@vga91 vga91 moved this from Todo to In Progress in APOC Extended Larus Jan 30, 2024
@vga91 vga91 moved this from In Progress to Blocked in APOC Extended Larus Jan 30, 2024
@vga91 vga91 added the core-functionality Adding new procedure, function or signature to APOC core label Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core-functionality Adding new procedure, function or signature to APOC core
Projects
Status: Blocked
Development

No branches or pull requests

3 participants