Optimize all Existing Queries

[Jenil-Savla]

Make sure that queries don't go over 60 seconds. Try Hive partitioning or MultiThreading.

[kulkarni-anish]

Many resources available on the web were considered for optimizing the queries including DuckDB Documentation, StackOverFlow, GitHub issues, etc. RDBMS-centered articles were also referred to.
Finally, it was decided that Hive Partitioning can be a useful technique but for this, the CloudOps team must again migrate entire data in the partitioned format.
Here’s a description of Hive Partitioning given in DuckDB Documentation. Arbiter backend docs

[SwapneelM]

Is there a status on this request (is anyone working on it; do they have a timeline; who is responsible for ensuring it is completed) and do you already know how the partitioning might work without costing a ton of money per query? That's what happened the last time, I think and resulted in a pause in activity. If you need help it is good to ask and make it clear how to reproduce past hive partitioning (as, I think you have in the linked docs above).