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
Bootstrap of range-field-index fails after upgrade to 1.7.5 (due to missing invalid-values in ml-config) #733
Comments
Easy fix is to add the invalid-values, but that param is optional, so would be nice if Roxy would not fail like this if it is omitted. Docs unfortunately don't really tell what the default value is, at first look.. |
Crud. In most cases, I specified |
We should add this scenario to our self-test. |
The default behavior for MarkLogic is to use |
Crud. I should probably change it to reject, then. |
dmcassel
added a commit
to dmcassel/roxy
that referenced
this issue
Feb 14, 2017
RobertSzkutak
added a commit
that referenced
this issue
Feb 21, 2017
#733 corrected invalid-values default; addressed missed case
divino
added a commit
to divino/roxy-1
that referenced
this issue
Apr 28, 2017
…verify-issue * 'dev' of https://github.com/marklogic/roxy: implemented based on review points implement review points fix comments add feature to load multiple custom configuration files marklogic-community#733 corrected invalid-values default; addressed missed case issue marklogic-community#740: make -EXT work from modules and filesystem removed unneeded FLWOR statements, fixed indent fixed mistake in validate-roles/users retrieval of existing roles/users outside loop issue marklogic-community#736: fix CTRL-EXT from a filesystem modules DB Update version
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
With a range-field-index like:
bootstrap fails with:
Culprit is the missing
invalid-values
.The text was updated successfully, but these errors were encountered: