Spark SQL magic does not have the same optional arguments that Trino does, and that is -c/--catalog where you provide a catalog for trino to use, and -m/--schema where you provide a schema for trino to use. This could be achieved in sparksql with the USE statement (e.g. USE catalog_name or USE catalog.schema_name), however, it would be useful to have these trino arguments as Spark SQL flags. This would allow users to only have to specify the table names, rather than the full namespace (i.e. catalog.schema.table).
Spark SQL magic does not have the same optional arguments that Trino does, and that is
-c/--catalogwhere you provide a catalog for trino to use, and-m/--schemawhere you provide a schema for trino to use. This could be achieved in sparksql with theUSEstatement (e.g.USE catalog_nameorUSE catalog.schema_name), however, it would be useful to have these trino arguments as Spark SQL flags. This would allow users to only have to specify the table names, rather than the full namespace (i.e.catalog.schema.table).