Jeremy, We're sorry you ran into this! Please file a bug report or or send a pull-request to the Github project: https://github.com/basho/riak-erlang-client/issues. We will be working to resolve inconsistencies like these in the next dev cycle, across all our supported clients.
On Fri, Jan 20, 2012 at 9:51 AM, Jeremy Raymond <jeraym...@gmail.com> wrote: > The Erlang PB client gives and takes secondary index information as > binaries in some places and strings in others. For example > riakc_pb_socket:get_index/4 wants the Index and Key as binaries. > Retrieving the index information from the meta data of an object read > out of Riak gives the Index and Key as strings. > > Can strings and binaries be used interchangeable for indexes > throughout the API? Or is is such that the representation inside of a > riak_obj is a strings, but API functions want it as binaries? > > The inconsistency is a bit of a nuisance. In testing of some of my > application's logic I'm setting an index on a new object using binary > values, I query the index using the binary values, but when I read it > back they're strings. > > -- > Jeremy > > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > -- Sean Cribbs <s...@basho.com> Software Engineer Basho Technologies, Inc. http://basho.com/
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
