damccorm commented on issue #36214: URL: https://github.com/apache/beam/issues/36214#issuecomment-3320939961
That would definitely be an option. I'll note that it is probably less efficient though, since you need to apply it to any encoding/decoding, as opposed to just: 1) Applying it at the GBK boundary 2) Enforcing that you only persist GBK'd data (this is how most runners work/checkpoint already AFAIK). An alternative would be to eventually offer both and let the runner choose the mode that works for them. -- 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]
