You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After much frustration fussing, and a post to stack overflow, I finally found a syntax that would work:
"^.*(/[^/]+/),'$1'"
It turns out that you have to both wrap the whole thing in double quotes, and ALSO wrap the replacement string in single quotes. That's in a config file. I never got it working on the command line.
The error message is anything but helpful.
To me it looks like a bug, but in any case it should be documented properly, which it is not. A working example of regular expression replacement should be included in the documentation.
The above is a very simple expression that should be useful to discard everything up to the directory below, which is probably a very common use case. It shouldn't be so difficult to do that, and I shouldn't be forced to spell out the explicit path, as that solution is not portable.
After much frustration fussing, and a post to stack overflow, I finally found a syntax that would work:
"^.*(/[^/]+/),'$1'"
It turns out that you have to both wrap the whole thing in double quotes, and ALSO wrap the replacement string in single quotes. That's in a config file. I never got it working on the command line.
The error message is anything but helpful.
To me it looks like a bug, but in any case it should be documented properly, which it is not. A working example of regular expression replacement should be included in the documentation.
The above is a very simple expression that should be useful to discard everything up to the directory below, which is probably a very common use case. It shouldn't be so difficult to do that, and I shouldn't be forced to spell out the explicit path, as that solution is not portable.
Please see the stackoverflow issue for more details:
https://stackoverflow.com/questions/72946854/marklogic-mlcp-output-uri-replace-fail
The text was updated successfully, but these errors were encountered: