Hi Thad,

Thanks for the question. I’ll address the question to the best of my ability, but a more technically savvy person from my team can correct me if I get the details wrong.

Is it still the case that the team is unable to kill a problematic query?

Problematic queries can lock up Blazegraph, causing it to be unresponsive. In this case, the only solution is to restart Blazegraph, as we are unable to ask it to kill the problematic query. Unfortunately, restarting Blazegraph does not guarantee that the user agent can simply resend that same query again, causing the cycle to continue. This is one of the contexts in which we talk about authentication providing our team with more tools to handle problematic queries bringing down the query service.

I noted the discussion also about “authentication” with WCQS Beta 2 coming Feb. 2.

Small correction (might have been a typo), but WCQS beta 2 is scheduled to be live in Tues Feb 1.

Hope that helps answer your question!

Best,
Mike