willmurnane commented on issue #88: URL: https://github.com/apache/accumulo-access/issues/88#issuecomment-3639365442
I think making this a non-text format makes it a less generally useful specification. I know for my own purposes treating access expressions as strings is an easier mental model than a “bag of bytes”. If the expression isn’t expected to be a valid string (and I think UTF-8 is the normal way of encoding that these days) then every downstream consumer of this library has to consider how to display the expression very carefully. Additionally, if a byte-oriented format were necessary, I think the model would be simpler if it didn’t require quoting for so many bytes. It would be simpler if only `()$|` required quoting (probably with `\`) rather than requiring double-quotes around some tokens and not others. I think the concept of a generic access expression not tied to any particular standard is a useful one, but I think evolving this in the direction of a byte oriented format makes it less generally applicable. I would suggest making Accumulo 4.0 a breaking change in the narrow cases where people were using non-UTF-8 bytes, and providing an iterator that people can modify and run as necessary to convert the expressions on their data to valid strings. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
