[MonetDB-users] Executing tijah query from module fails
[This is a new thread following on from "XRPC issues"]
Executing a tijah query in a module from both old and new front ends fails. Using the old front end (\g) produces the following error:
xquery>import module namespace test="tj" at "http://localhost:50001/export/tj.xq "; more>execute at {"localhost"} {test:tijahSearch("Heathrow")} more><> doLoopLiftedRPC: error occurred at localhost: MAPI = monetdb@localhost:50000 QUERY = import module namespace test="tj" at "http://localhost:50001/export/tj.x q"; ERROR = !ERROR: HTTP Error Code : 404 Bad Request !ERROR: SOAP Fault Code : env:Sender !ERROR: SOAP Fault Reason: !ERROR: Error occurred during execution. !ERROR: interpret: no matching MIL operator to 'tj_query_handler(bit, BA T[void,BAT], BAT[oid,BAT], BAT[void,BAT], BAT[oid,oid], BAT[oid,BAT], BAT[oid,ln g], BAT[oid,dbl], BAT[oid,str], void)'. !MAYBE YOU MEAN: ! tj_query_handler(bit, BAT[void,BAT], BAT[void,BAT], BAT[void,BAT ], BAT[oid,any], BAT[oid,BAT], BAT[void,lng], BAT[void,dbl], BAT[void,str], BAT[ void,BAT]) : BAT[void,BAT] ! ! !ERROR: CMDhttp_post: operation failed.
MAPI = monetdb@localhost:50000 QUERY = import module namespace test="tj" at "http://localhost:50001/export/tj.x q"; ERROR = !ERROR: doLoopLiftedRPC: execution failed at all destinations: !ERROR: localhost: !ERROR: HTTP Error Code : 404 Bad Request !ERROR: SOAP Fault Code : env:Sender !ERROR: SOAP Fault Reason: !ERROR: Error occurred during execution. !ERROR: interpret: no matching MIL operator to 'tj_query_handler(bit, BA T[void,BAT], BAT[oid,BAT], BAT[void,BAT], BAT[oid,oid], BAT[oid,BAT], BAT[oid,ln g], BAT[oid,dbl], BAT[oid,str], void)'. !MAYBE YOU MEAN: ! tj_query_handler(bit, BAT[void,BAT], BAT[void,BAT], BAT[void,BAT ], BAT[oid,any], BAT[oid,BAT], BAT[void,lng], BAT[void,dbl], BAT[void,str], BAT[ void,BAT]) : BAT[void,BAT] ! ! !ERROR: CMDhttp_post: operation failed. !ERROR: !ERROR: xquery>
Has anyone succeeded in executing a tijah query from within a module?
-- Roy
On Mon, Jul 27, 2009 at 04:22:55PM +0100, Roy Walter wrote:
[This is a new thread following on from "XRPC issues"]
Executing a tijah query in a module from both old and new front ends fails.
What is the problem when you execute the same tijah function with the default frontend?
Using the old front end (\g) produces the following error:
Would you please attach the file 'tj.xq' so that we also can run your query with both frontends (assuming the small/simplified document you sent in your previous e-mail is still sufficient to run the query).
Jennie
PS> I will find a Windows machine later (today) to try to reproduce the error you mentioned in your previous e-mail
xquery>import module namespace test="tj" at "http://localhost:50001/export/tj.xq "; more>execute at {"localhost"} {test:tijahSearch("Heathrow")} more><> doLoopLiftedRPC: error occurred at localhost: MAPI = monetdb@localhost:50000 QUERY = import module namespace test="tj" at "http://localhost:50001/export/tj.x q"; ERROR = !ERROR: HTTP Error Code : 404 Bad Request !ERROR: SOAP Fault Code : env:Sender !ERROR: SOAP Fault Reason: !ERROR: Error occurred during execution. !ERROR: interpret: no matching MIL operator to 'tj_query_handler(bit, BA T[void,BAT], BAT[oid,BAT], BAT[void,BAT], BAT[oid,oid], BAT[oid,BAT], BAT[oid,ln g], BAT[oid,dbl], BAT[oid,str], void)'. !MAYBE YOU MEAN: ! tj_query_handler(bit, BAT[void,BAT], BAT[void,BAT], BAT[void,BAT ], BAT[oid,any], BAT[oid,BAT], BAT[void,lng], BAT[void,dbl], BAT[void,str], BAT[ void,BAT]) : BAT[void,BAT] ! ! !ERROR: CMDhttp_post: operation failed. MAPI = monetdb@localhost:50000 QUERY = import module namespace test="tj" at "http://localhost:50001/export/tj.x q"; ERROR = !ERROR: doLoopLiftedRPC: execution failed at all destinations: !ERROR: localhost: !ERROR: HTTP Error Code : 404 Bad Request !ERROR: SOAP Fault Code : env:Sender !ERROR: SOAP Fault Reason: !ERROR: Error occurred during execution. !ERROR: interpret: no matching MIL operator to 'tj_query_handler(bit, BA T[void,BAT], BAT[oid,BAT], BAT[void,BAT], BAT[oid,oid], BAT[oid,BAT], BAT[oid,ln g], BAT[oid,dbl], BAT[oid,str], void)'. !MAYBE YOU MEAN: ! tj_query_handler(bit, BAT[void,BAT], BAT[void,BAT], BAT[void,BAT ], BAT[oid,any], BAT[oid,BAT], BAT[void,lng], BAT[void,dbl], BAT[void,str], BAT[ void,BAT]) : BAT[void,BAT] ! ! !ERROR: CMDhttp_post: operation failed. !ERROR: !ERROR: xquery>Has anyone succeeded in executing a tijah query from within a module?
-- Roy
MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
Ying Zhang wrote:
On Mon, Jul 27, 2009 at 04:22:55PM +0100, Roy Walter wrote:
[This is a new thread following on from "XRPC issues"]
Executing a tijah query in a module from both old and new front ends fails.
What is the problem when you execute the same tijah function with the default frontend?
Using the old front end (\g) produces the following error:
Would you please attach the file 'tj.xq' so that we also can run your query with both frontends (assuming the small/simplified document you sent in your previous e-mail is still sufficient to run the query).
Jennie
PS> I will find a Windows machine later (today) to try to reproduce the error you mentioned in your previous e-mail
xquery>import module namespace test="tj" at "http://localhost:50001/export/tj.xq "; more>execute at {"localhost"} {test:tijahSearch("Heathrow")} more><> doLoopLiftedRPC: error occurred at localhost: MAPI = monetdb@localhost:50000 QUERY = import module namespace test="tj" at "http://localhost:50001/export/tj.x q"; ERROR = !ERROR: HTTP Error Code : 404 Bad Request !ERROR: SOAP Fault Code : env:Sender !ERROR: SOAP Fault Reason: !ERROR: Error occurred during execution. !ERROR: interpret: no matching MIL operator to 'tj_query_handler(bit, BA T[void,BAT], BAT[oid,BAT], BAT[void,BAT], BAT[oid,oid], BAT[oid,BAT], BAT[oid,ln g], BAT[oid,dbl], BAT[oid,str], void)'. !MAYBE YOU MEAN: ! tj_query_handler(bit, BAT[void,BAT], BAT[void,BAT], BAT[void,BAT ], BAT[oid,any], BAT[oid,BAT], BAT[void,lng], BAT[void,dbl], BAT[void,str], BAT[ void,BAT]) : BAT[void,BAT] ! ! !ERROR: CMDhttp_post: operation failed. MAPI = monetdb@localhost:50000 QUERY = import module namespace test="tj" at "http://localhost:50001/export/tj.x q"; ERROR = !ERROR: doLoopLiftedRPC: execution failed at all destinations: !ERROR: localhost: !ERROR: HTTP Error Code : 404 Bad Request !ERROR: SOAP Fault Code : env:Sender !ERROR: SOAP Fault Reason: !ERROR: Error occurred during execution. !ERROR: interpret: no matching MIL operator to 'tj_query_handler(bit, BA T[void,BAT], BAT[oid,BAT], BAT[void,BAT], BAT[oid,oid], BAT[oid,BAT], BAT[oid,ln g], BAT[oid,dbl], BAT[oid,str], void)'. !MAYBE YOU MEAN: ! tj_query_handler(bit, BAT[void,BAT], BAT[void,BAT], BAT[void,BAT ], BAT[oid,any], BAT[oid,BAT], BAT[void,lng], BAT[void,dbl], BAT[void,str], BAT[ void,BAT]) : BAT[void,BAT] ! ! !ERROR: CMDhttp_post: operation failed. !ERROR: !ERROR: xquery>Has anyone succeeded in executing a tijah query from within a module?
-- Roy
MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
The error using the default front end (\G) is:
xquery>import module namespace test="tj" at "http://localhost:50001/export/tj.xq "; more>execute at {"localhost"} {test:tijahSearch("Heathrow")} more>^Z MAPI = monetdb@localhost:50000 QUERY = import module namespace test="tj" at "http://localhost:50001/export/tj.x q"; ERROR = !ÉsZ !.c[+(gP?d !ERROR: interpret: no matching MIL operator to 'reverse(void)'. !MAYBE YOU MEAN: ! reverse(BAT[any::1,any::2]) : BAT[any::2,any::1] !ERROR: interpret_params: sort(param 1): evaluation error. !ERROR: interpret_params: reverse(param 1): evaluation error. xquery>
The related query (in module tj.xq) is:
module namespace tj = "tj";
declare function tj:tijahSearch($term as xs:string) as node()* { for $res in tijah:queryall("//speech[about(., $term)]") return $res };
-- Roy
On Mon, Jul 27, 2009 at 05:28:10PM +0100, Roy Walter wrote:
Ying Zhang wrote:
On Mon, Jul 27, 2009 at 04:22:55PM +0100, Roy Walter wrote:
[This is a new thread following on from "XRPC issues"]
Executing a tijah query in a module from both old and new front ends fails.
What is the problem when you execute the same tijah function with the default frontend?
Using the old front end (\g) produces the following error:
Would you please attach the file 'tj.xq' so that we also can run your query with both frontends (assuming the small/simplified document you sent in your previous e-mail is still sufficient to run the query).
Jennie
PS> I will find a Windows machine later (today) to try to reproduce the error you mentioned in your previous e-mail
xquery>import module namespace test="tj" at "http://localhost:50001/export/tj.xq "; more>execute at {"localhost"} {test:tijahSearch("Heathrow")} more><> doLoopLiftedRPC: error occurred at localhost: MAPI = monetdb@localhost:50000 QUERY = import module namespace test="tj" at "http://localhost:50001/export/tj.x q"; ERROR = !ERROR: HTTP Error Code : 404 Bad Request !ERROR: SOAP Fault Code : env:Sender !ERROR: SOAP Fault Reason: !ERROR: Error occurred during execution. !ERROR: interpret: no matching MIL operator to 'tj_query_handler(bit, BA T[void,BAT], BAT[oid,BAT], BAT[void,BAT], BAT[oid,oid], BAT[oid,BAT], BAT[oid,ln g], BAT[oid,dbl], BAT[oid,str], void)'. !MAYBE YOU MEAN: ! tj_query_handler(bit, BAT[void,BAT], BAT[void,BAT], BAT[void,BAT ], BAT[oid,any], BAT[oid,BAT], BAT[void,lng], BAT[void,dbl], BAT[void,str], BAT[ void,BAT]) : BAT[void,BAT] ! ! !ERROR: CMDhttp_post: operation failed. MAPI = monetdb@localhost:50000 QUERY = import module namespace test="tj" at "http://localhost:50001/export/tj.x q"; ERROR = !ERROR: doLoopLiftedRPC: execution failed at all destinations: !ERROR: localhost: !ERROR: HTTP Error Code : 404 Bad Request !ERROR: SOAP Fault Code : env:Sender !ERROR: SOAP Fault Reason: !ERROR: Error occurred during execution. !ERROR: interpret: no matching MIL operator to 'tj_query_handler(bit, BA T[void,BAT], BAT[oid,BAT], BAT[void,BAT], BAT[oid,oid], BAT[oid,BAT], BAT[oid,ln g], BAT[oid,dbl], BAT[oid,str], void)'. !MAYBE YOU MEAN: ! tj_query_handler(bit, BAT[void,BAT], BAT[void,BAT], BAT[void,BAT ], BAT[oid,any], BAT[oid,BAT], BAT[void,lng], BAT[void,dbl], BAT[void,str], BAT[ void,BAT]) : BAT[void,BAT] ! ! !ERROR: CMDhttp_post: operation failed. !ERROR: !ERROR: xquery>Has anyone succeeded in executing a tijah query from within a module?
I ran your tijahSearch() on a windows vista 64bits, without xrpc, with both frondends, and I got similar errors. So, it looks like a Tijah related problem, not xrpc related problem. I'm not familiar with Tijah queries, so I'd like to recommend you to run your query without xrpc to see what happens exactly on your system, and report the errors, so that the tijah experts could have a look at your problem.
The error using the default front end (\G) is:
xquery>import module namespace test="tj" at "http://localhost:50001/export/tj.xq "; more>execute at {"localhost"} {test:tijahSearch("Heathrow")} more>^Z MAPI = monetdb@localhost:50000 QUERY = import module namespace test="tj" at "http://localhost:50001/export/tj.x q"; ERROR = !ÉsZ !.c[+(gP?d !ERROR: interpret: no matching MIL operator to 'reverse(void)'. !MAYBE YOU MEAN: ! reverse(BAT[any::1,any::2]) : BAT[any::2,any::1] !ERROR: interpret_params: sort(param 1): evaluation error. !ERROR: interpret_params: reverse(param 1): evaluation error. xquery>
This is because xrpc doesn't work with the default frond end.
Jennie
Ying Zhang wrote:
On Mon, Jul 27, 2009 at 05:28:10PM +0100, Roy Walter wrote:
Ying Zhang wrote:
On Mon, Jul 27, 2009 at 04:22:55PM +0100, Roy Walter wrote:
[This is a new thread following on from "XRPC issues"]
Executing a tijah query in a module from both old and new front ends fails.
What is the problem when you execute the same tijah function with the default frontend?
Using the old front end (\g) produces the following error:
Would you please attach the file 'tj.xq' so that we also can run your query with both frontends (assuming the small/simplified document you sent in your previous e-mail is still sufficient to run the query).
Jennie
PS> I will find a Windows machine later (today) to try to reproduce the error you mentioned in your previous e-mail
xquery>import module namespace test="tj" at "http://localhost:50001/export/tj.xq "; more>execute at {"localhost"} {test:tijahSearch("Heathrow")} more><> doLoopLiftedRPC: error occurred at localhost: MAPI = monetdb@localhost:50000 QUERY = import module namespace test="tj" at "http://localhost:50001/export/tj.x q"; ERROR = !ERROR: HTTP Error Code : 404 Bad Request !ERROR: SOAP Fault Code : env:Sender !ERROR: SOAP Fault Reason: !ERROR: Error occurred during execution. !ERROR: interpret: no matching MIL operator to 'tj_query_handler(bit, BA T[void,BAT], BAT[oid,BAT], BAT[void,BAT], BAT[oid,oid], BAT[oid,BAT], BAT[oid,ln g], BAT[oid,dbl], BAT[oid,str], void)'. !MAYBE YOU MEAN: ! tj_query_handler(bit, BAT[void,BAT], BAT[void,BAT], BAT[void,BAT ], BAT[oid,any], BAT[oid,BAT], BAT[void,lng], BAT[void,dbl], BAT[void,str], BAT[ void,BAT]) : BAT[void,BAT] ! ! !ERROR: CMDhttp_post: operation failed. MAPI = monetdb@localhost:50000 QUERY = import module namespace test="tj" at "http://localhost:50001/export/tj.x q"; ERROR = !ERROR: doLoopLiftedRPC: execution failed at all destinations: !ERROR: localhost: !ERROR: HTTP Error Code : 404 Bad Request !ERROR: SOAP Fault Code : env:Sender !ERROR: SOAP Fault Reason: !ERROR: Error occurred during execution. !ERROR: interpret: no matching MIL operator to 'tj_query_handler(bit, BA T[void,BAT], BAT[oid,BAT], BAT[void,BAT], BAT[oid,oid], BAT[oid,BAT], BAT[oid,ln g], BAT[oid,dbl], BAT[oid,str], void)'. !MAYBE YOU MEAN: ! tj_query_handler(bit, BAT[void,BAT], BAT[void,BAT], BAT[void,BAT ], BAT[oid,any], BAT[oid,BAT], BAT[void,lng], BAT[void,dbl], BAT[void,str], BAT[ void,BAT]) : BAT[void,BAT] ! ! !ERROR: CMDhttp_post: operation failed. !ERROR: !ERROR: xquery>Has anyone succeeded in executing a tijah query from within a module?
I ran your tijahSearch() on a windows vista 64bits, without xrpc, with both frondends, and I got similar errors. So, it looks like a Tijah related problem, not xrpc related problem. I'm not familiar with Tijah queries, so I'd like to recommend you to run your query without xrpc to see what happens exactly on your system, and report the errors, so that the tijah experts could have a look at your problem.
If I run the query from the command line within mclient using the default front end (\G) it works fine, i.e:
xquery>tijah:queryall("//speech[about(., Heathrow)]")
The error using the default front end (\G) is:
xquery>import module namespace test="tj" at "http://localhost:50001/export/tj.xq "; more>execute at {"localhost"} {test:tijahSearch("Heathrow")} more>^Z MAPI = monetdb@localhost:50000 QUERY = import module namespace test="tj" at "http://localhost:50001/export/tj.x q"; ERROR = !ÉsZ !.c[+(gP?d !ERROR: interpret: no matching MIL operator to 'reverse(void)'. !MAYBE YOU MEAN: ! reverse(BAT[any::1,any::2]) : BAT[any::2,any::1] !ERROR: interpret_params: sort(param 1): evaluation error. !ERROR: interpret_params: reverse(param 1): evaluation error. xquery>This is because xrpc doesn't work with the default frond end.
Jennie
Yes, as you stated elsewhere. I was just responding to your request for the error when using the default front end. I don't know if it's signficant but I see that the error from both the old and default front ends includes a reference to: "no matching MIL operator..."
So the state of play seems to be this: since tijah does not work using the old front end (see above), it isn't going to work via xrpc which is using the old front end.
-- Roy
So the state of play seems to be this: since tijah does not work using the old front end (see above), it isn't going to work via xrpc which is using the old front end.
If you only need to execute xquery queries via command line on local monetdb/xquery server, you don't need xrpc, because using 'execute at {localhost}' only introduce one extra communication within the same monetdb/xquery server. xrpc is more interesting if you need to execute xquery queries on (multiple) remote monetdb/xquery servers, or via a web interface.
Jennie
Ying Zhang wrote:
So the state of play seems to be this: since tijah does not work using the old front end (see above), it isn't going to work via xrpc which is using the old front end.
If you only need to execute xquery queries via command line on local monetdb/xquery server, you don't need xrpc, because using 'execute at {localhost}' only introduce one extra communication within the same monetdb/xquery server. xrpc is more interesting if you need to execute xquery queries on (multiple) remote monetdb/xquery servers, or via a web interface.
Jennie
I need to execute tijah xquery queries via a web interface. That's why I have been trying to get tijah/xrpc working. I'm only using mclient in an attempt to establish what's working and what isn't.
The performance of standard xquery queries over xrpc (non tijah) using [contains()] for example is too slow.
-- Roy
hej Roy,
I agree that it is indeed quite unfortunate that XRPC is not running in the current algebra front-end of MonetDB/Xquery. But there might be other ways to call XQueries from your web application. We use Tijah queries also in other projects within web applications for instance using the JDBC interface. This is not as elegant as XRPC calls but works fine. Also, I cannot recommend to use the out-dated milprint- summer front-end by calling the mclient with the -g option. We have noticed some bugs in that version, but since it is not supported anymore, that version will not get fixed.
cheers -Henning
On 28.07.2009, at 15:05, Roy Walter wrote:
Ying Zhang wrote:
So the state of play seems to be this: since tijah does not work using the old front end (see above), it isn't going to work via xrpc which is using the old front end.
If you only need to execute xquery queries via command line on local monetdb/xquery server, you don't need xrpc, because using 'execute at {localhost}' only introduce one extra communication within the same monetdb/xquery server. xrpc is more interesting if you need to execute xquery queries on (multiple) remote monetdb/xquery servers, or via a web interface.
Jennie
I need to execute tijah xquery queries via a web interface. That's why I have been trying to get tijah/xrpc working. I'm only using mclient in an attempt to establish what's working and what isn't.
The performance of standard xquery queries over xrpc (non tijah) using [contains()] for example is too slow.
-- Roy
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
Hi Henning
Thanks for your comments. I just made a start with the JDBC interface :-)
I downloaded the jdbcclient.jar and it's working fine and with tijah. Now to make some pages and get my head around java again!
Best regard, Roy
Henning Rode wrote:
hej Roy,
I agree that it is indeed quite unfortunate that XRPC is not running in the current algebra front-end of MonetDB/Xquery. But there might be other ways to call XQueries from your web application. We use Tijah queries also in other projects within web applications for instance using the JDBC interface. This is not as elegant as XRPC calls but works fine. Also, I cannot recommend to use the out-dated milprint-summer front-end by calling the mclient with the -g option. We have noticed some bugs in that version, but since it is not supported anymore, that version will not get fixed.
cheers -Henning
On 28.07.2009, at 15:05, Roy Walter wrote:
Ying Zhang wrote:
So the state of play seems to be this: since tijah does not work using the old front end (see above), it isn't going to work via xrpc which is using the old front end.
If you only need to execute xquery queries via command line on local monetdb/xquery server, you don't need xrpc, because using 'execute at {localhost}' only introduce one extra communication within the same monetdb/xquery server. xrpc is more interesting if you need to execute xquery queries on (multiple) remote monetdb/xquery servers, or via a web interface.
Jennie
I need to execute tijah xquery queries via a web interface. That's why I have been trying to get tijah/xrpc working. I'm only using mclient in an attempt to establish what's working and what isn't.
The performance of standard xquery queries over xrpc (non tijah) using [contains()] for example is too slow.
-- Roy
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.35/2269 - Release Date: 07/28/09 17:58:00
participants (3)
-
Henning Rode -
Roy Walter -
Ying Zhang