-
Notifications
You must be signed in to change notification settings - Fork 232
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
Invalid JSON when trying to create a bucket type with custom properties #1885
Comments
Which OS is this on? Just done this on Ubuntu:
However, I know we had issues with riak admin commands for bucket creation (with JSON) on OSX in test. Is this related? |
Just double-checked and the problem is that the riak admin script relies on this escape function: The There are a couple of workarounds. Use a bash shell, or you can set the bucket properties directly from riak remote_console (i.e. the erlang shell):
|
The long term answer might be to swap @hmmr - I think though that there is some history here about why |
This all seemed familiar ... and now I remember why ... and its because a PR was raised by @aef- for this last year: I approved it at the time, but deferred merging as we were not due to release a new version of 3.2, as the focus was on 3.0 updates. @nsaadouni, @bet365-bspencer - as this has come up multiple times now, could you look at the PR? |
Yes -- |
Hi, PRETTY_NAME="Ubuntu 22.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.1 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
root@d-riak-coord-jrc:/#
|
In Riak 3.2.0 I'm trying to create the following bucket type:
riak admin bucket-type create sessions_v1 '{"props":{"n_val":3 }}'
I'm getting this error
Cannot create bucket type sessions_v1: invalid json
error
As you can see, JSON is valid, not suere what's going on..
The text was updated successfully, but these errors were encountered: