ctubbsii commented on PR #2665: URL: https://github.com/apache/accumulo/pull/2665#issuecomment-1138641601
> Using `set/getConsistencyLevel` on ScannerBase allows us to change the implementation without changing the API. Using a name tied to the implementation will cause API churn if the implementation changes. I'm not tied to `set/getConsistencyLevel`. Yes, but it would allow us to change implementation of that specific characteristic... but that's not the essential characteristic here. > I'm waiting for some consensus before change the API method names. That's reasonable. Thus far, I haven't really been thinking alternative names. I've only been trying to make the case that consistency level isn't the right way of exposing the feature to users. To think of new names, I think it would be good to think about what the essential characteristics are for scan servers: * higher availability? * dynamically scalable hosting? * read-only service? * some other sufficient description? -- 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]
