Github user gatorsmile commented on a diff in the pull request:

    https://github.com/apache/spark/pull/14155#discussion_r75250702
  
    --- Diff: 
sql/core/src/main/scala/org/apache/spark/sql/execution/command/createDataSourceTables.scala
 ---
    @@ -97,16 +92,17 @@ case class CreateDataSourceTableCommand(
           }
         }
     
    -    CreateDataSourceTableUtils.createDataSourceTable(
    -      sparkSession = sparkSession,
    -      tableIdent = tableIdent,
    +    val table = CatalogTable(
    +      identifier = tableIdent,
    +      tableType = if (isExternal) CatalogTableType.EXTERNAL else 
CatalogTableType.MANAGED,
    +      storage = CatalogStorageFormat.empty.copy(properties = 
optionsWithPath),
           schema = dataSource.schema,
    -      partitionColumns = partitionColumns,
    -      bucketSpec = bucketSpec,
    -      provider = provider,
    -      options = optionsWithPath,
    --- End diff --
    
    It sounds like we are not following the previous behaviors. `options` might 
be consumed by the external Data Source implementors. `options` is not only 
used for specifying `path`, but also used for a channel to pass extra 
parameters to the data source.
    
    I checked the existing implementation of `createDataSourceTable`. We [pass 
the original `options` into the constructor of 
`DataSource`](https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/command/createDataSourceTables.scala#L336).
 Then, [the `write` API will pass the `option` to 
`createRelation`](https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSource.scala#L443).
 
    
    How about adding it as an independent field in `CatalogTable`?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to