Github user keith-turner commented on the issue:
https://github.com/apache/accumulo/pull/260
> What does this mean?
When I was writing a yielding filter, when I set the yield key I was not
sure if it would continue at that key or after it.
> Are you suggesting another jira ticket here? I have not changed any of
the scan scheduling mechanism.
No, it was just something I observed and didn't fully understand. I am
going to look into it some more today. I was expecting the CPU utilization to
be 100% in this case, because there was plenty of work to do.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
