ugh I expected compatibility
>> issues with something. Base 64 encoding the binary value is a nice
>> compromise for me, and takes 22 characters (if you drop the padding)
>> instead of the usual 36 for the hyphenated hex format.
>>
>> It would still require re encoding
s, but it's a partial solutions.
>
> From: Eric Redmond
> Sent: Monday, 11 August 2014 9:15 AM
> To: David James
> Cc: riak-users
> Subject: Re: Using UUID as keys is problematic for Riak Search
>
> You're correct that yokozuna only supports utf8, because the
ugust 2014 9:15 AMTo: David JamesCc: riak-usersSubject: Re: Using UUID as keys is problematic for Riak Search
You're correct that yokozuna only supports utf8, because the Solr interface only supports utf8 (note that the failure happens when attempting to build a non-utf8 JSON add document c
usual 36 for the hyphenated hex format.
>
> It would still require re encoding all the keys, but it's a partial
> solutions.
>
>*From: *Eric Redmond
> *Sent: *Monday, 11 August 2014 9:15 AM
> *To: *David James
> *Cc: *riak-users
> *Subject: *Re: Using UUID
I like UUIDs for everything as well, although I expected compatibility issues with something. Base 64 encoding the binary value is a nice compromise for me, and takes 22 characters (if you drop the padding) instead of the usual 36 for the hyphenated hex format.It would still require re encoding all
You're correct that yokozuna only supports utf8, because the Solr interface only supports utf8 (note that the failure happens when attempting to build a non-utf8 JSON add document command). There's not much we can do here at the moment, since we've yet to (if ever) support a custom interface to Sol
