Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/20387
> Can you give a use case about this?
We've added a resolution rule from `UnresolvedRelation` to
`DataSourceV2Relation` that uses our implementation. `UnresolvedRelation` needs
to pass its `TableIdentifier` to the v2 relation, which is why I added this.
We could separate this out, but I think it makes sense to get the options
for an immutable plan node right from the start. And I think we agree that
`TableIdentifier` will be passed this way. I just don't see any benefit to
separating this out. I agree that there isn't a requirement in this PR and I
can remove it if necessary.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
