It does not bother just you. :) Can we bound where all this shows up? In most cases we can address compatibility concerns by making a new API and transitioning to it as the guidelines allow for breakage.
That generally means sooner is better than later; our next big effort to make sure obsolete things are deprecated will be whenever the push for 2.0 happens. So far that looks like somewhere in Aug-Dec. -- Sean On Apr 13, 2015 5:18 PM, "Dave Latham" <[email protected]> wrote: > Wish I had started this conversation 5 years ago... > > When we're using binary data, especially in row keys (and therefore > region boundaries) the output created by toStringBinary is very > painful to use: > - mix of ascii / hex representation is trouble > - it's quite long (4 characters per binary byte) > - it mixes in punctuation characters (quotes are not good when > pasting in to shell commands) > > Does this bother anyone else? Is it too late to do anything about it > due to compatibility fears? > > Can we change to something that is always binary e.g. hex? > 0x746f537472696e6742696e617279206d616b657320636c75737465727320637279 > > Or if we have to auto-detect, only use ascii if the entire string is ascii? > > Dave >
