Per email from Brad Maggard on 2015-09-16, addfieldusingcontext() doe… #343
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per email from Brad Maggard on 2015-09-16, addfieldusingcontext() doesn't have access to the new field, making calculations like running sum more complicated.
The generator yields the tuple from the original table. It now creates a new Record() object with the additional field and the previous row's value, providing access to the prior row's new field.
I profiled both time and memory usage - the extra step of creating the Record() instance is minimal.
On a random table of 1MM rows, it added 100KB of memory at runtime and changed execution time from 63 seconds to 65 seconds on my test.