Open Bob-The-Marauder opened 4 years ago
@Bob-The-Marauder Did anything happen with this issue? Is it still an issue?
I assume the problem is that gset is not an existing atom until the set bucket type is created ... but I don't know why it isn't, and why creating the set type makes it one.
If you have a brand new cluster with no data whatsoever, gsets cannot be created. This can currently be worked around by creating a set first and then the gset. Example underneath where I fail multiple times to create a gset, successfully create a set and then create my gset with the exact same command that was failing earlier:-
The above is on CentOS 6 with a vanilla install of Riak KV 2.2.6.