Clarify each_batch docs do not iterate non-unique column
What does this MR do and why?
This came up recently in !111027 (comment 1332491816)
Previously I was confused by this wording and got the impression that it would just lead to inconsistent batch sizes. Given we know that it can just get stuck in an infinite loop (which is actually documented further down the page already) then the wording "proceed with extra caution" is not as helpful as just telling you not to do it. They can already just read on to the next sections about how they can iterate over non-unique columns.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.