TBC: SPARQLMotion script debug and run problem

[Kai Liu]

Hi,

if the script has been debugged once, the "Run SPARQLMotion script" button will always bring up the debugger, which is confusing. I restarted TBC multiple times, and this problem is reproducible. If the script hasn't been debugged, the "Run" button works properly however. The version is 7.0.3.

Could you please check?

Best regards, Kai

[Holger Knublauch]

Hello Kai,

this works OK for me. For example when I open TopBraid/Examples/CreateReportSpreadsheet.ttl and use the debug button, then the run button, it will just execute the script to the finish. HOWEVER, once you set any breakpoint, it will also run in debug mode when you press the run button. Maybe this is what you are doing? If not, please send a screenshot to make sure we are talking about the same thing.

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/0c0ebd15-f87f-4fee-ba6c-9cefeb5b9439n%40googlegroups.com.

[Kai Liu]

Hi Holger,

thanks for the clarification. Yes, you hit the point. I did select the breakpoint checkboxes. I am used to Visual Studio and Eclipse IDE and thought the "Run script..." button would just ignore all breakpoints. It seems that when breakpoints are set, the only difference between "Run" and "Debug" is that the latter will bring up the debugger at the beginning. Is there a way to let scripts run through while keeping breakpoints? I can imagine if I would have a relatively complex pipeline and I want to let the pipeline run through in normal mode, but I do want to see some predefined critical points when problem occurs. I am just thinking of a normal software debugging scenario. Perhaps this is not comparable to a pipeline debugging.

Best regards, Kai

[Holger Knublauch]

On 2021-11-09 4:54 pm, Kai Liu wrote:

Hi Holger,

thanks for the clarification. Yes, you hit the point. I did select the breakpoint checkboxes. I am used to Visual Studio and Eclipse IDE and thought the "Run script..." button would just ignore all breakpoints. It seems that when breakpoints are set, the only difference between "Run" and "Debug" is that the latter will bring up the debugger at the beginning.

Yes, we made a rather arbitrary choice back then. The design you describe certainly would make sense too.

Is there a way to let scripts run through while keeping breakpoints?

Not from these two buttons, but SM scripts can be executed as web services against the localhost server. There is some documentation at

https://www.topquadrant.com/technology/sparqlmotion/

but frankly I would say that few people are using SPARQLMotion these days, and for data processing on our platform have either moved to SWP or ADS https://datashapes.org/active/ which give you more flexibility. Unless of course you have problem spaces where exactly the visual design and flow of a pipeline language is the best fit.

Holger

I can imagine if I would have a relatively complex pipeline and I want to let the pipeline run through in normal mode, but I do want to see some predefined critical points when problem occurs. I am just thinking of a normal software debugging scenario. Perhaps this is not comparable to a pipeline debugging.

Best regards, Kai

On Tuesday, 9 November 2021 at 00:44:41 UTC+1 Holger Knublauch wrote:

Hello Kai,

this works OK for me. For example when I open TopBraid/Examples/CreateReportSpreadsheet.ttl and use the debug button, then the run button, it will just execute the script to the finish. HOWEVER, once you set any breakpoint, it will also run in debug mode when you press the run button. Maybe this is what you are doing? If not, please send a screenshot to make sure we are talking about the same thing.

Holger

On 2021-11-09 5:35 am, Kai Liu wrote:

Hi,

if the script has been debugged once, the "Run SPARQLMotion script" button will always bring up the debugger, which is confusing. I restarted TBC multiple times, and this problem is reproducible. If the script hasn't been debugged, the "Run" button works properly however. The version is 7.0.3.

Could you please check?

Best regards, Kai

--
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/0c0ebd15-f87f-4fee-ba6c-9cefeb5b9439n%40googlegroups.com.

--
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/91f2ae68-11d3-4fca-a106-1be35d111b97n%40googlegroups.com.

[Kai Liu]

Hi Holger,

I am looking for options to run ETL pipelines into KG for heterogeneous data from many different sources. The Active Data Shapes looks indeed interesting. Many thanks for pointing out this. I will look into it.

Best regards, Kai