#238 [Feature] Abstraction and standardization of query tasks Issue created by wild-endeavor Motivation: Why do you think this is important? Now that we have a Presto task and a Hive task in Flytekit, we should consider abstracting them both behind a more general Flytekit query task. We should also change the way Hive queries currently run (as de facto dynamic tasks), and follow the pattern established by the new Presto plugin. It may not be possible to do this in a backwards compatible way however, especially considering legacy code at Lyft, so the development of a general query task that supports Hive may be independent from the existing Hive task. Goal: What should the final outcome look like, ideally? Flytekit tasks that are more general. Describe alternatives you've considered None. Flyte component ☐ Overall ☐ Flyte Setup and Installation scripts ☐ Flyte Documentation ☐ Flyte communication (slack/email etc) ☐ FlytePropeller ☐ FlyteIDL (Flyte specification language) ☑︎ Flytekit (Python SDK) ☐ FlyteAdmin (Control Plane service) ☑︎ FlytePlugins ☐ DataCatalog ☐ FlyteStdlib (common libraries) ☐ FlyteConsole (UI) ☐ Other Additional context Original Presto task issue: #203 flyteorg/flyte