This repository has been archived by the owner on Nov 9, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 66
setup.xqy fails to validate field range index config (most likely other range-indexes as well) #492
Comments
I thought we fixed most of these cases. Which version of Roxy? |
This was on v1.7.1, but the implementation is the same on current master: https://github.com/marklogic/roxy/blob/master/deploy/lib/xquery/setup.xqy#L2447 |
Ah yes, from the looks we forgot to fix path-index, and field-index. Will look asap.. |
Still applies.. |
joemfb
changed the title
setup.xqy fails to valid field range index config (most likely other range-indexes as well)
setup.xqy fails to validate field range index config (most likely other range-indexes as well)
Feb 12, 2016
Pushing off to the next release... |
dmcassel
added a commit
to dmcassel/roxy
that referenced
this issue
Jan 17, 2017
dmcassel
added a commit
to dmcassel/roxy
that referenced
this issue
Jan 17, 2017
dmcassel
added a commit
to dmcassel/roxy
that referenced
this issue
Jan 17, 2017
…l supported ML versions
dmcassel
added a commit
to dmcassel/roxy
that referenced
this issue
Jan 17, 2017
…ported ML versions
dmcassel
added a commit
to dmcassel/roxy
that referenced
this issue
Jan 17, 2017
dmcassel
added a commit
to dmcassel/roxy
that referenced
this issue
Jan 17, 2017
…ibute-pair indexes
dmcassel
added a commit
to dmcassel/roxy
that referenced
this issue
Jan 17, 2017
dmcassel
added a commit
to dmcassel/roxy
that referenced
this issue
Jan 17, 2017
dmcassel
added a commit
to dmcassel/roxy
that referenced
this issue
Jan 17, 2017
dmcassel
added a commit
to dmcassel/roxy
that referenced
this issue
Jan 17, 2017
dmcassel
added a commit
to dmcassel/roxy
that referenced
this issue
Jan 17, 2017
dmcassel
added a commit
to dmcassel/roxy
that referenced
this issue
Jan 17, 2017
dmcassel
added a commit
to dmcassel/roxy
that referenced
this issue
Jan 17, 2017
dmcassel
added a commit
to dmcassel/roxy
that referenced
this issue
Jan 17, 2017
…of try/catch and eval for path-namespaces
dmcassel
added a commit
to dmcassel/roxy
that referenced
this issue
Jan 17, 2017
replace eval with xdmp:value
dmcassel
added a commit
to dmcassel/roxy
that referenced
this issue
Jan 17, 2017
dmcassel
added a commit
to dmcassel/roxy
that referenced
this issue
Jan 17, 2017
RobertSzkutak
added a commit
that referenced
this issue
Jan 30, 2017
#492 verify parameters during setup
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since
setup.xqy
uses the XML snippets fromml-config.xml
directly, without validating their contents, it's possible to end up with a schema-invaliddatabases.xml
configuration. Once that happens the REST Management API throws errors for database updates.Specifically, I had a database with a
range-field-index
element containing anamespace-uri
element (from the dmlc-healthcare project). This bootstraps (and works) without issue via Roxy. When I try to configure a database using the REST Management API (using ml-gradle and OBI), the PUT to/manage/v2/databases/obi-ui-content/properties
fails with a 400 error.This may properly be a bug of the Admin API not validating it's parameters. I'm not sure what an appropriate resolution would be, but wanted to capture the problem here.
The text was updated successfully, but these errors were encountered: