Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/20387
@felixcheung, yes, we do already have a `table` option. That creates an
`UnresolvedRelation` with the parsed table name as a `TableIdentifier`, which
is not currently compatible with `DataSourceV2` because there is no standard
way to pass the identifier's db and table name.
Part of the intent here is to add support in `DataSourceV2Relation` for
cases where we have a `TableIdentifier`, so that we can add a resolver rule
that replaces `UnresolvedRelation` with `DataSourceV2Relation`. This is what we
do in our Spark branch.
@cloud-fan, what is your objection to support like this?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
