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

Option to prevent splitting graphs in the SPARQL constuct component #461

Open
rorlic opened this issue Jan 23, 2024 · 0 comments
Open

Option to prevent splitting graphs in the SPARQL constuct component #461

rorlic opened this issue Jan 23, 2024 · 0 comments
Assignees
Labels
component: core Issues related to LDI Building Blocks enhancement New feature or request

Comments

@rorlic
Copy link
Contributor

rorlic commented Jan 23, 2024

Currently, the behavior of the SPARQL constuct LDIO component is: check if resulting triples contains a named graph and,
if one or more named graphs is found, split the triples into the named graph, adding the default graph to each named graph before pushing it into the rest of the pipeline, else send the triples as-is in the rest of the pipeline.

This behavior is fine for splitting a message into multiple messages for individual handling. However, sometimes you actually want to keep the named graph(s) as a whole and send it further downstream, e.g. when creating a data client pipeline outputtng to a graphdb you want to keep the named graph so that you can replace the named graph as a whole.

So, please add an option to prevent splitting by named graph keeping the current behavior as the default.

@rorlic rorlic added the needs triage Issue needs to be evaluated by team label Jan 23, 2024
@Yalz Yalz added component: core Issues related to LDI Building Blocks enhancement New feature or request and removed needs triage Issue needs to be evaluated by team labels Jan 25, 2024
@github-project-automation github-project-automation bot moved this to 📋 Backlog in VSDS Backlog Jan 25, 2024
@Yalz Yalz moved this from 📋 Backlog to 🔖 To be picked up in VSDS Backlog Jan 25, 2024
@Yalz Yalz assigned Yalz and unassigned Yalz Dec 2, 2024
@jobulcke jobulcke self-assigned this Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: core Issues related to LDI Building Blocks enhancement New feature or request
Projects
Status: 🔖 To be picked up
Development

No branches or pull requests

3 participants