ivakegg opened a new issue, #3287:
URL: https://github.com/apache/accumulo/issues/3287

   The Teardown section of the User Manual states that "Being torn-down is 
equivalent to a new instance of the Iterator being creating and deepCopy being 
called on the new instance with the old instance provided as the argument to 
deepCopy."  This is entirely inaccurate.  deepCopy is not used at all when 
recreating the iterator stack for a scan.  The iterator stack is created as 
brand new instances, init is called with the original options, and then it is 
seeked from where it left off.  Implying that deepCopy is used suggests that 
way more state can be preserved in an iterator which is not true.
   
   Affects at least the 1.x versions of the user manual (e.g. 
https://accumulo.apache.org/1.10/accumulo_user_manual.html#_teardown).  I was 
unable to find where that section went in the 2.x version but that should be 
corrected as well if it got moved anywhere.


-- 
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]

Reply via email to