Skip to content
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

Wrong bucket types/names/keys PB encoding #47

Open
llelf opened this issue May 22, 2016 · 5 comments
Open

Wrong bucket types/names/keys PB encoding #47

llelf opened this issue May 22, 2016 · 5 comments

Comments

@llelf
Copy link
Contributor

llelf commented May 22, 2016

riak-haskell-client has been doing BucketType/Bucket/Key encoding
wrong basically from the beginning. I don't know the reason @bos did
it the way it is.

I'm going to fix it, but I have two questiongs to the maintainers:

  1. It won't affect ordinary ascii-only names in any way, so it'd
    prefer it to just be a backward-incompatible change. What do you
    think? Besides, there were no complaints all this time. ;)
  2. Those names are actually Text. What do you think about this
    change?
    It shouldn't affect performance since you need to traverse those
    strings to look for special characters anyway (and we do it now).
@tmcgilchrist
Copy link
Member

Thanks @llelf, could you go into more detail about how the escaping is wrong? Assuming you mean the code in Escape.hs

I'm assuming from comment 1 it's working for ASCII but not for unicode (perhaps UTF-8 specifically)

  1. I'm not sure I follow this.

@llelf
Copy link
Contributor Author

llelf commented May 26, 2016

@tmcgilchrist, it over-quotes them. It does url-escaping of, while it should only quote a '/'. Assuming the name is a proper utf-8, hence the question about Text.

  1. If you put data into bucket "ξ" (or any non-ascii), you won't be able to read it from "ξ" with the new version of riak-haskell-client. We could think about some backward compatibility scheme here, but it'd say it is unjustified and just declare it to be backward-incompatible. All ascii-only names will continue to work anyway.

@llelf
Copy link
Contributor Author

llelf commented Jun 20, 2016

ping!

@mitchellwrosen
Copy link
Contributor

Ping number 2 =)

@tmcgilchrist
Copy link
Member

This is slowly bubbling to the top of my stack. I'd like to get some of the
other or changes in first before tackling this.

On Wednesday, 5 October 2016, Mitchell Rosen notifications@github.com
wrote:

Ping number 2 =)


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#47 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKbuaUMaITSW8mKebCHUtIfU849SUvWks5qwmS3gaJpZM4Ij-nS
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants