ddanielr commented on PR #5375: URL: https://github.com/apache/accumulo/pull/5375#issuecomment-2698538797
> > Good news is that there are already properties for the thread pools being used in the client for bulk v1, but are labeled TSERV. > > That could work, it would depend on the behavior of the bulkv1 and bulkv2 code that use the prop. If bulkv1 and bulkv2 code would need different settings for the property to be optimal on a system because of underlying behavior diffs in the use of the property then it would be confusing to reuse the property. I agree that we shouldn't reuse the bulkv1 threadpool property. Users will probably want to run jobs back to back using bulkv1 and bulkv2 configurations to compare results. Minimizing the amount of configuration changes needed for that switch would be ideal. > Thinking about the bulk v1 code and behavior, it would be nice if this fix for bulkv2 caused no changes in behavior for the bulkv1 code. Since both use the same RPC need to be careful about changing that RPC as it will impact bulkv1 and bulkv2. Is there a requirement for keeping the same RPC as bulkv1? -- 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]
