snazy commented on PR #4454: URL: https://github.com/apache/polaris/pull/4454#issuecomment-4484998994
Thanks, I see the concern. I’d prefer to keep the issue-driven guidance as a separate section, because this is a recurring PR pattern, and the section title gives reviewers something concrete to point to. Folding it into “Understand Before Coding” would make the guidance less visible. For the resource-use paragraph, I agree it is not only about simplicity, but I’m not sure a dedicated IO section is worth it for a single paragraph. The rule is: choose the simplest resource-friendly implementation instead of, for example, materializing an unbounded source. I’d keep it under Simplicity unless we expect to add more IO/resource guidance later. -- 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]
