RasqlServlet - web interface for rasql queries

[Dimitar Misev]

We need a RasqlServlet in petascope which would expose rasql on the web.

The WCPSServer can be mostly copied, special care is needed regarding user credentials however.

[Peter Baumann]

first idea for a GET/KVP binding:

…?user=xxx&password=xxx&query=select…

with a multipart return type.

[abeccati]

I'd say to keep it out of petascope since its on a different level: petascope implements OWS-based endpoints and WCPS should not be applicable for direct rasdaman query.

Why not have it as a separate servlet into applications which produces its own deployable war?

This will also improve on endpoints consolidation for petascope

[Dimitar Misev]

That doesn't sound good to me

• it's not worth maintaining a separate project that would be more or less one servlet of 100 lines of code
• we can easily reuse a lot of established functionality in petascope, separate project would mean a lot of code duplication

This endpoint would be separate from WCPS and the rest, could be available at /petascope/rasql or /petascope/rasdaman, so I don't see interference.

[Peter Baumann]

…and the insert/update/delte functionality is guarded by the login (still, we might have a configuration parameter which disables it by default, for security).

[abeccati]

Code duplication, if any, should then be factored out to a jar to be put into tomcat libs so that all deployed servlets can use it. Can we make a quick estimate on that?

More importantly, we have to keep clear scope definition and separation of functionality if we aim at a clean and maintainable design. I just not see factoring in that feature to fit with petascope's aim of being a WCS/WCPS implementation.

Same reason here: ​http://rasdaman.eecs.jacobs-university.de/trac/rasdaman/ticket/270

[Dimitar Misev]

Replying to abeccati:

I just not see factoring in that feature to fit with petascope's aim of being a WCS/WCPS implementation.

When did we define that aim, sounds a bit restricting? So far I thought of petascope as a web-frontend of rasdaman (be it via OGC standards or something else).

The RasqlServlet will be around 100 lines or so. A separate war will require

• refactor common functionality between the two projects into a separate jar (third project)
• set up Makefiles for building
• probably introduce new configuration files

The differences between separate project vs. within petascope implementation

• servlet available at /rasql vs /petascope/rasql (or similar), which to the end user makes no difference whatsoever
• separate project linked via common jar, vs. separate package (petascope.rasql) using directly petascope code, again making no difference

[Dimitar Misev]

I submitted an initial version of this and will most likely work some more on it.

[Dimitar Misev]

Initial version provided in changeset:f0e48ec

TODO: uploading data, for doing insert and partial updates via the web interface.

TODO2: add tests to source:systemtest/testcases_petascope

[Peter Baumann]

where can I find material for documentation?

[Dimitar Misev]

I think Vlad worked last on it, and could provide information for the documentation.

[Bang Pham Huu]

at the point when Dimitar closed this ticket, there is a RasqlServlet class in petascope which I see the code can support to return the data (text/binary) from Rasql Query, so we need to add some test cases in systemtest for this servlet

(this servlet is documented in rasql query guide page 113), however the example is not correct, it should be:

domain:[port]/rasdaman/rasql?query

http://www.acme.com/rasdaman?
query=select%20rgb.red+rgb.green%20from%20rgb
&username=rasguest
&password=rasguest

[Peter Baumann]

good idea to provide solid tests!
BTW, I am still lacking documentation input.

[Bang Pham Huu]

Replying to pbaumann:

good idea to provide solid tests!
BTW, I am still lacking documentation input.

I added the documentation for Rasql Servlet here ​http://rasdaman.org/wiki/Clients#Rasqlquerylanguageaccess (with the submitted patch, it can support to upload file to collection)

[Peter Baumann]

excellent, well done!