-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XQConnection problems #62
Comments
My solution was to create a BaseXClient class taken from here |
I would vote to look for an alternative to the map function
|
I tried but it turns out to be unwieldy: the only thing i can think of is to export an XML string directly, something like this:
Is this a good solution? It seems very unwieldy to me, compared to adding one class |
I'm looking forward to process the same xquery expressions with flink i.e. a special flink library that is currently being developed. I can barly imagine that they'd support xquery 3.1. |
* Add additional API with XQuery v3.1 support (BaseXClient) (see #62) * Implement new NTCIR footer to output hit XML directly (Benchmark) * Parse XML using XMLEventReader and write to string (Client) * Replace Formula class with an option to write an XML string directly to the Hit class (Results) * Add unit test to test new XML qvar output Change-Id: I704ea2a12421b2194a289c7514307eae40618826
* Add additional API with XQuery v3.1 support (BaseXClient) (see #62) * Implement new NTCIR footer to output hit XML directly (Benchmark) * Parse XML using XMLEventReader and write to string (Client) * Replace Formula class with an option to write an XML string directly to the Hit class (Results) * Add unit test to test new XML qvar output Change-Id: I704ea2a12421b2194a289c7514307eae40618826
XQJ API only supports XQuery v3.0, not XQuery v3.1, so the map{} implementation is not supported.
This means that either we 1) switch APIs just for search highlighting or 2) figure out a different method of exporting the qvar map
The text was updated successfully, but these errors were encountered: