FANNG1 opened a new issue, #10357: URL: https://github.com/apache/gravitino/issues/10357
### What would you like to be improved? Current optimizer docs are improved but still easy to get stuck in real environments when running the full flow end-to-end. The main pain points are missing/implicit dependencies between steps and insufficiently explicit verification checkpoints. Areas that should be clearer and consistently documented: - Full chain from table creation -> policy creation/binding -> update stats -> recommend/submit rewrite -> metrics append/list/monitor - Required preconditions before each step and expected outputs - Cross-validation guidance for metrics and job outcomes - Clear alpha-scope limitations and compatibility notes for partition transforms - Reproducible copy-paste examples for common environments ### How should we improve? - Keep one canonical end-to-end workflow with strict step ordering and expected results. - Add explicit prerequisites and failure checkpoints before moving to next step. - Standardize metrics validation with `append-metrics`, `list-table-metrics`, `list-job-metrics`, and `monitor-metrics`. - Keep architecture diagram and terminology mapping up-to-date with command usage. - Document JDBC metrics setup templates (MySQL/PostgreSQL) including driver classpath notes. -- 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]
