Skip to content
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

Open
jimmyli97 opened this issue Jun 15, 2015 · 4 comments
Open

XQConnection problems #62

jimmyli97 opened this issue Jun 15, 2015 · 4 comments
Assignees
Labels
Milestone

Comments

@jimmyli97
Copy link
Contributor

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

@jimmyli97 jimmyli97 added the bug label Jun 15, 2015
@jimmyli97 jimmyli97 added this to the urgent milestone Jun 15, 2015
@jimmyli97
Copy link
Contributor Author

My solution was to create a BaseXClient class taken from here

@physikerwelt
Copy link
Member

I would vote to look for an alternative to the map function
On Jun 15, 2015 7:50 PM, "Jimmy Li" [email protected] wrote:

My solution was to create a BaseXClient class taken from here
https://github.com/BaseXdb/basex/blob/master/basex-examples/src/main/java/org/basex/examples/api/BaseXClient.java


Reply to this email directly or view it on GitHub
#62 (comment)
.

@jimmyli97
Copy link
Contributor Author

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:

let $q := "<qvar for... />\n<qvar for.../>"

Is this a good solution? It seems very unwieldy to me, compared to adding one class

@physikerwelt
Copy link
Member

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.
I guess xquery 3.1 is just too new. But go ahead for now. We can care about backwards compatibility later by adding a xquery version attribute to MathML query generator later.

jimmyli97 added a commit that referenced this issue Jun 21, 2015
* 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
jimmyli97 added a commit that referenced this issue Oct 16, 2015
* 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants