I would like to file an RFE for this features. So here is the challenge at current I am facing. I have loaded a search configuration called "all". Currently there are no oob apis to access that configuration outside of the built-in apis.
I have several custom APIs/transforms that enhance or interact with the query component. So I need to be able to parse the qtext form and the internally from query components in json format. The code Geert shared does most of the plumbing hooks into the internal API's, so my recommendation is to expose those api's that allow for following: 1. get search options by name through rest utility which I can get name from param, then I can call get the textual portion of the query resolved 2. ability parse the json representation of the query to cts.query without any requirement of having access to original options node. Thanks Geert for snippet to get resolved. Regards, Gary Vidal
_______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
