rdblue commented on a change in pull request #26297: [SPARK-29665][SQL] refine
the TableProvider interface
URL: https://github.com/apache/spark/pull/26297#discussion_r341776246
##########
File path:
sql/catalyst/src/main/java/org/apache/spark/sql/connector/catalog/TableProvider.java
##########
@@ -36,26 +39,34 @@
public interface TableProvider {
/**
- * Return a {@link Table} instance to do read/write with user-specified
options.
+ * Infer the schema of the table that is identified by the given options.
+ *
+ * @param options The options that can identify a table, e.g. file path,
Kafka topic name, etc.
+ * It's an immutable case-insensitive string-to-string map.
*
- * @param options the user-specified options that can identify a table, e.g.
file path, Kafka
- * topic name, etc. It's an immutable case-insensitive
string-to-string map.
*/
- Table getTable(CaseInsensitiveStringMap options);
+ StructType inferSchema(CaseInsensitiveStringMap options);
/**
- * Return a {@link Table} instance to do read/write with user-specified
schema and options.
- * <p>
- * By default this method throws {@link UnsupportedOperationException},
implementations should
- * override this method to handle user-specified schema.
- * </p>
- * @param options the user-specified options that can identify a table, e.g.
file path, Kafka
- * topic name, etc. It's an immutable case-insensitive
string-to-string map.
- * @param schema the user-specified schema.
- * @throws UnsupportedOperationException
+ * Infer the partitioning of the table that is identified by the given
options.
+ *
+ * @param schema The schema of the table.
+ * @param options The options that can identify a table, e.g. file path,
Kafka topic name, etc.
+ * It's an immutable case-insensitive string-to-string map.
+ */
+ Transform[] inferPartitioning(StructType schema, CaseInsensitiveStringMap
options);
Review comment:
I don't think the schema is actually needed. Partitioning and schemas are
mostly orthogonal. If anything, you could argue that identity partitions should
be in the schema and that `inferSchema` could accept the result of
`inferPartitioning`.
Also, none of the implementations actually use it besides the one that uses
it to create a file index. It seems to me like this is more of a convenience
for that implementation than something that is generally needed. Can we remove
it from the API?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
