DanielLeens commented on issue #10916: URL: https://github.com/apache/seatunnel/issues/10916#issuecomment-4608236351
The key point here is not to let `ChunkId` drift into a content-hash rename. Please keep three boundaries explicit in the design: 1. stable chunk identity 2. chunk content hash 3. chunker configuration hash Reviewers will need a clear migration story for existing `content_hash` users, and an explicit statement about what is expected to change when only the chunking algorithm or chunker parameters change. -- 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]
