Closed franklinWhaite closed 3 months ago
The only thing I would do is potentially move the scripts/optimization/run_anti_pattern_tool.sh and the antipattern portion of the README under the anti-pattern-recognittion-tool-scripts folder, just so its clear that the run_all_scripts won't execute the antipattern tool as well
I have moved the run_anti_pattern_tool.sh script to the anti-pattern-recognittion-tool-scripts folder.
Nevertheless if we move antipattern portion of the README under the anti-pattern-recognittion-tool-scripts folder the users might miss the existence of the tool. I would rather have our documentation on how to use the scripts centralized than spread across several READMEs.
I understand this may be confusing, so i slightly changed the README to make it more clear that that the run_all_scripts won't execute the antipattern tool as well.
LGTM
queries_grouped_by_hash.sql
references thequery
column which is no longer available. I removed that column and renamed the filequeries_grouped_by_hash_org.sql
queries_grouped_by_hash.sql
to referenceINFORMATION_SCHEMA.JOBS
instead ofINFORMATION_SCHEMA.JOBS_BY_PROJECT
. I createdqueries_grouped_by_hash_project.sql
which runs at project level instead of org level.queries_grouped_by_hash_project.sql
and other prefer to work withviewable_queries_grouped_by_hash.sql
. Since these generate tables with different schemas I made therun_anti_pattern_tool.sh
script generic so it can run against any table given that necessary arguments are provided