Yes, sys.queue(), sorry.
A couple of clarifications. The cookbook shows mclient, but we're using the API and we assume you can do the same thing from the API as well. Also, we use autogenerated queries that can be hundreds if not thousands of characters long. Matching in a case independent way would be very resource intensive.
It's fairly clear from the documentation that MonetDB doesn't stop immediately in the middle of whatever it is doing, so that's understood. But cancelling queries …
[View More]has to be part of a robust database system. My model of how this might work is that the handle that’s returned when we issue a query could be used to associate with some data returned by sys.queue(), preferably tag or start time since those should be unique and fairly short. Then we stash then in some structure, and if a cancel request comes in, we do a much simpler search of the sys.queue() table that's guaranteed to work.
JONATHAN ZINGMAN | Manager – TrueCall Data | DIRECT: 510.809.0423 | CELL: 510.823.5638 | www.netscout.com
-----Original Message-----
From: users-list <users-list-bounces+jonathan.zingman=netscout.com(a)monetdb.org> On Behalf Of Martin Kersten
Sent: Tuesday, June 11, 2019 1:56 PM
To: users-list(a)monetdb.org
Subject: Re: Cancel query
This message originated outside of NETSCOUT. Do not click links or open attachments unless you recognize the sender and know the content is safe.
On 11/06/2019 22:38, Ying (Jennie) Zhang wrote:
>
>
>> On 11 Jun 2019, at 00:58, Zingman, Jonathan <Jonathan.Zingman(a)netscout.com> wrote:
>>
>> In the cookbook, you give a good way to find out the status of queries by using the sys.query() call,
>
> Hai, Jonathan,
>
> MonetDB doesn’t have a function called sys.query(). Did you mean sys.queue() instead?
>
>> which returns the list of queries tagged in various ways. Our question is whether there is any way to access, e.g., the tag value. In our application, we need to occasionally cancel queries from our UI. The UI has no direct knowledge of the query. While we might be able to find the query we want to cancel by comparing the query text, our automatically generated queries can be very long, and if there’s some internal reformatting by Monetdb, we might not get an exact match. So is there anything in the handle or elsewhere that we can use to identify the query we want to cancel?
>
> Correct me if I’m wrong, but I’m not aware of a feature with which you can query the qtag of a query. Some code study will be needed to see if it’s feasible to add such feature, and how.
>
> You can probably get away with string matching, since MonetDB doesn’t do much/any reformatting next to to-lowercase. Not sure how much text the “query” field of sys.queue() holds.
>
> In addition, please be aware that
> i) sys.queue() is originally develop for debugging purpose…
> ii) the minimal cancellation entity is a function, i.e., when MonetDB is busy executing a very long running function, a cancellation will only take effect *after* that function has finished => then MonetDB won’t continue executing the next function.
Small correction here, with function we mean a MAL function call. So, if the system is executing a very time consuming join, it will
*not* be interrupted, but rather at the end of it the query in which is rans is terminated.
>
> Regards,
> Jennie
>
>>
>> JONATHAN ZINGMAN
>> Manager – TrueCall Data
>>
>> <image001.png>
>> 2855 Telegraph Ave, Suite 200
>> Berkeley, CA, 94705-1169
>>
>> DIRECT: 510.809.0423
>> CELL: 510.823.5638
>> http://www.netscout.com
>>
>>
>> _______________________________________________
>> users-list mailing list
>> users-list(a)monetdb.org
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.monetdb.org_mailma…
>
> _______________________________________________
> users-list mailing list
> users-list(a)monetdb.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.monetdb.org_mailma…
>
_______________________________________________
users-list mailing list
users-list(a)monetdb.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.monetdb.org_mailma…
[View Less]
In the cookbook, you give a good way to find out the status of queries by using the sys.query() call, which returns the list of queries tagged in various ways. Our question is whether there is any way to access, e.g., the tag value. In our application, we need to occasionally cancel queries from our UI. The UI has no direct knowledge of the query. While we might be able to find the query we want to cancel by comparing the query text, our automatically generated queries can be very long, and …
[View More]if there's some internal reformatting by Monetdb, we might not get an exact match. So is there anything in the handle or elsewhere that we can use to identify the query we want to cancel?
JONATHAN ZINGMAN
Manager - TrueCall Data
[logos]
2855 Telegraph Ave, Suite 200
Berkeley, CA, 94705-1169
DIRECT: 510.809.0423
CELL: 510.823.5638
www.netscout.com<http://www.netscout.com/>
[View Less]
Hi,
I am new to the MonetDB and interested to know about its case sensitivity. We noticed that objects are being created in lower case if they are not specified in quotes so it appears to me that default case for objects created in Monet is LOWERCASE. But, we got a requirement that objects should be created in upper case even though they are not specified in quotes in DDL statements. In other words, can we make the default to UPPERCASE for all the objects when they created. Please …
[View More]let us know if that is possible.
Your early response is very much appreciated.
~Suresh D
[View Less]
Hello,
I'm trying to install MonetDB on AWS Linux.
The first command succeeds:
sudo yum install
https://dev.monetdb.org/downloads/epel/MonetDB-release-epel.noarch.rpm
The second command fails:
sudo yum install MonetDB-SQL-server5 MonetDB-client
Error:
*[ec2-user@ip-172-31-23-149 ~]$ sudo yum install MonetDB-SQL-server5
MonetDB-clientLoaded plugins: extras_suggestions, langpacks, priorities,
update-motdhttps://dev.monetdb.org/downloads/
<https://dev.monetdb.org/downloads/&…
[View More]gt;epel/2/x86_64/repodata/repomd.xml:
[Errno 14] HTTPS Error 404 - Not FoundTrying other mirror. One of the
configured repositories failed (MonetDB 2 - x86_64), and yum doesn't have
enough cached data to continue. At this point the only safe thing yum can
do is fail. There are a few ways to work "fix" this:*
It seems to me there's a reference to epel/2 which is out of date. Should
that be epel/7? Is it possible to get an updated rpm?
Thanks,
Gerald
[View Less]