keith-turner commented on issue #88: URL: https://github.com/apache/accumulo-access/issues/88#issuecomment-3608163281
Re #55 that issue does not capture that the spec and code are not currently in agreement. Would be good to keep this issue open to get the spec, code, and javadocs all in sync. Also need to remove the detailed UTF8 definition. > I understand you'd probably like to keep existing Accumulo code compatible with this spec If an accumulo 2.x system happened to have non utf8 data in an access expression then what happens if accumulo 4 uses this library and it throws an exception when it sees that data? Is that data unscannable until it is manually fixed? Also would want to avoid data being silently transformed (like non utf8 chars are just transformed to something else) if that could cause false positives or false negatives in evaluation. Not sure what the best solution to this is, but these are my main concerns. Also wondering what the performance impact is if this code starts validating utf8 when it did not in the past. This could be determined w/ testing. But probably need to figure how compatibility should be handled first. -- 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]
