Hello
We are currently evaluating ML, first as a XML database supporting
XQuery. We already have one and a complex but not large set of data and
would like to benefit from ML rich features.
ML seems an amazing database and functionally bring a lot to the table.
But I have two main concerns :
1)
The recent communications around ML 8 and the evolutions in the recent
versions are making me question the support of standard XQuery.
More precisely the absence of support of XQuery 3.0 beyond the prefix is
a bit puzzling (I am thinking mostly about group_by clauses).
Said otherwise this post http://markmail.org/message/fpsimswbt3gteooj
from 2012 seems to still be relevant and did not get any "answer" ;).
I fully understand and appreciate that ML needs to "move forward into
buzzland" from JSON (good) to haddoop and BIgData (who really has a
truly 'big data' dataset ? ;) ), even throwing that abomination that is
javascript into the mix ( ;) ) but does that mean that XML and XQUERY
support will stop evolving and be "engine level /internals stuff"
(because I understand that ML is still at its score a XML/document
database ) ?
2)
I am also a bit troubled by the constant "cts/xdmp:hack" that seems to
be the only way of getting performance out of ML.
I know that this kind of "custom methods" is supported by the W3C specs
but my problem is that it seems to be the complete and constant
substitute for FLOWER.
I can understand such an escape hatch for specific optimizations (the
last 20% perf ;)) or to access functionality outside of the standard
XML/XQuery/XPATH specs (like state injection or the temporal stuff or
the rest stuff) but it really seems like it goes way beyond that and
that, in fact, ML support its own query langage based on an XQuery like
syntax, much more than XQuery with some extensions. :)
Is this a wrong impression and is it possible to use ML with good
performance with "standard" XQuery. ?
I am not just being "theorical" there, we do have XML data and a
previous database and existing queries, and we intend to publish query
abilities "to the world ('company' wide and worldwide) " in some
specific cases. It is not feasible or acceptable for us to have to
impose the ML query language and I really don't like the idea of
rewriting most of my queries around proprietary stuff and have to
expose that stuff outside the application internals.
To sum it up:
1) is xquery support stuck in its current state (mostly 1.0)
2) is the XML support by ML still "first party"
3) is is possible to have good performance using standard XQuery syntax
for requests.
Thanks a lot for your time.
PS : sorry for posting this on a "dev" mailling list but there does not
seem to be a "general" mailling list, and I trust fellow developers more
than anyone to tell me the reality (even the bitter one ) of such things.
________________________________________________________________
Ce message, ainsi que les pièces jointes, sont établis, sous la
seule responsabilité de l'expéditeur, à l'intention exclusive
de ses destinataires ; ils peuvent contenir des informations
confidentielles. Toute publication, utilisation ou diffusion
doit être autorisée préalablement.
Ce message a fait l'objet d'un traitement anti-virus.
Il est rappelé que tout message électronique est susceptible
d'altération au cours de son acheminement sur Internet.
________________________________________________________________
Vous pouvez consulter le site de l'Assemblée nationale à
l'adresse suivante : http://www.assemblee-nationale.fr
_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general
