Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Need to restart for collation changes to server #125

Closed
mustard57 opened this issue Aug 20, 2013 · 2 comments
Closed

Need to restart for collation changes to server #125

mustard57 opened this issue Aug 20, 2013 · 2 comments

Comments

@mustard57
Copy link

I've found that if I change server collation in ml-config.xml I need to do a restart for it to be effective. However, if I do this directly in the admin console I do not. The best way to test is to put a simple module in place like

xdmp:set-response-content-type("text/html"),
"Checking comparisons ...",
"A" = "a"

and then toggle your collation to case sensitive and back via the collation field in ml-config.xml and ml local bootstrap and see whether the boolean returned from the above changes. For ease of reference ...

http://marklogic.com/collation//S1 - case insensitive

http://marklogic.com/collation/codepoint - case sensitive

@grtjn
Copy link
Contributor

grtjn commented Jun 13, 2017

I think this is more an issue in MarkLogic itself. If restart is required, the admin save-config(-without-restart) function should respond accordingly. We rely on how these functions behave.

I also tested against latest ML, and no longer observed the issue. The collation was changed just fine..

Closing as won't fix..

@grtjn grtjn closed this as completed Jun 13, 2017
@grtjn grtjn self-assigned this Jun 13, 2017
@grtjn grtjn added this to the July 2017 milestone Jun 13, 2017
@mustard57
Copy link
Author

mustard57 commented Jun 14, 2017 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants