[GitHub] [spark] rdblue commented on issue #26957: [SPARK-30314] Add identifier and catalog information to DataSourceV2Relation

rdblue commented on issue #26957: [SPARK-30314] Add identifier and catalog information to DataSourceV2Relation URL: https://github.com/apache/spark/pull/26957#issuecomment-577423876 @yuchenhuo, you're right that the create and replace plans already use Identifier and CatalogPlugin. I'm

[GitHub] [spark] rdblue commented on issue #26957: [SPARK-30314] Add identifier and catalog information to DataSourceV2Relation

rdblue commented on issue #26957: [SPARK-30314] Add identifier and catalog information to DataSourceV2Relation URL: https://github.com/apache/spark/pull/26957#issuecomment-574826960 @yuchenhuo, the mapping from multi-part identifier to table is already well-defined. I think using the same

[GitHub] [spark] rdblue commented on issue #26957: [SPARK-30314] Add identifier and catalog information to DataSourceV2Relation

rdblue commented on issue #26957: [SPARK-30314] Add identifier and catalog information to DataSourceV2Relation URL: https://github.com/apache/spark/pull/26957#issuecomment-574431706 @brkyvz, @yuchenhuo, is there a reason to use separate catalog and table identifiers? I think it would be