Daniel is exactly correct: for data, Riak is happy to store exactly what is supplied. This extends to bucket and bucket type names as well.
There are places where non-ASCII characters can be problematic: for example, to the best of my recollection it is not recommended to try to run JavaScript MapReduce against Unicode data. It's also easy to make mistakes at the client layer: for example, when using the Erlang client, the language requires that UTF-8 data be flagged as such, and it can be quite confusing when data stored in the <<"відро">> bucket cannot be retrieved from the <<"відро"/utf8>> bucket. -John Daily [email protected] On Thu, Nov 26, 2015 at 3:10 AM, Fasil K <[email protected]> wrote: > Thanks Daniel. This means a lot > > With Regards, > > Fasil K > > On Thu, Nov 26, 2015 at 1:10 PM, Daniel Abrahamsson < > [email protected]> wrote: > >> Hi Fasil. >> >> Riak stores data as binary blobs. It does not consider encodings at all. >> That way "riak supports data in any language". >> >> //Daniel >> >> On Thu, Nov 26, 2015 at 7:15 AM, Fasil K <[email protected]> wrote: >> >>> Hello, >>> >>> I have small doubt regarding the riak character encoding. >>> >>> Do we have to configure anything so that riak supports data in any >>> language (for eg: french,chinese etc) ? >>> >>> Thanks in advance >>> >>> >>> With Regards, >>> >>> Fasil K >>> >>> _______________________________________________ >>> riak-users mailing list >>> [email protected] >>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >>> >>> >> > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
