Prevent SPARQL Request iterating on all graphs on EDG

27 views
Skip to first unread message

Nicolas Fouqué

unread,
Mar 8, 2022, 4:38:49 AM3/8/22
to TopBraid Suite Users
Hi, when using TopBraid Composer I usually use the parameter "Report iterations over all graphs as an error and fail gracefully"

But when using EDG deployed as a standalone it seems that this parameter is not active by default. And I can't find this setting anywhere in EDG's administration console.

How can I enable this option ? This is an important security feature for me

Thanks in advance,

Holger Knublauch

unread,
Mar 8, 2022, 7:02:33 PM3/8/22
to topbrai...@googlegroups.com

Hi Nicolas,

this make sense but fell through the cracks and is not available from EDG at the moment.

Having said this, we are just about to finalize 7.2 so I could bring it back. Would you mainly need this from the SPARQL panel? And where should the warning show up? I guess any scripts or queries that do that should never go into production, so I assume you want this for your development/test environments where it's OK to just print them to console/log?

Holger

--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/3e067980-e56f-446d-b6fe-d11c779f70c8n%40googlegroups.com.

Nicolas Fouqué

unread,
Mar 29, 2022, 3:56:31 AM3/29/22
to TopBraid Suite Users
Hi Knublauch, 

Sorry I never realized I received an answer from you. I guess I'm too late to be of use to TBC 7.2 but yes, all your assumptions were correct.
This is for testing/integration purposes, it sometimes happens that the local environment has a graph that the development environment doesn't have and when trying to use it it makes an unbound graph instead and generates these iterations, we would like to avoid that especially because of the heavy load generated on our integrations servers by this kind of operations, so having it blocked and logged as an error like on TBC 7.0 would be great, but at least showing a warning would be good enough so that it only happens once.

Nicolas

Holger Knublauch

unread,
Mar 29, 2022, 9:34:31 PM3/29/22
to topbrai...@googlegroups.com

Ok thanks, the feature makes sense and we'll try to get this into 7.3 (scheduled for end of June).

Holger

Reply all
Reply to author
Forward
0 new messages