ctubbsii commented on issue #680: URL: https://github.com/apache/accumulo/issues/680#issuecomment-845239830
> I think the only relation is more from a usability standpoint, in that the methods w/ no config obj exists to support only using client props. In terms of usability, the way I've been thinking about it was: not specifying a config uses defaults; setting props in client properties allows you to tune those defaults; setting a config allows you to explicitly bypass those defaults. Tuning defaults kind of makes sense for BatchWriter, and possibly even Scanner, because those are ubiquitous in user code. ConditionalWriter use cases are much more niche in nature, and (my assumption is that) it's less likely that a set of user-tuned defaults in the client properties will make sense to apply to a significant number of separate uses of the `createConditionalWriter()` method. Focusing only on consistency, it makes sense to add options to the client props to merge with the default config. But, thinking about how often users will actually find that setting these in client properties will be useful to them, I'm less convinced. I'm not necessarily objecting, though... just expressing my skepticism that it would be useful. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
