Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/22281
> We have been through too many changes in related code. Each time a lot of
code need to be touched to implement a new proposal...
I agree in general. Thing is, I doubt if multiple catalog support can
directly relate to follow Datasource V1's behaviour. Took a look for writing
path and still it's possible to have the same interface.
@rdblue, now I am getting what you meant by removing save modes - however,
to me looks possible to have the current interface. Current change looks rather
how to deal with provider matching within SQL to target match Scala side API to
SQL APIs. Dealing with commands, new plans and save mode sounds lower level to
me.
The actual codes proposed here is to have one trait to link both data
sources to match Scala side to SQL side. I assume most of problems in the
current DataSource V2 are already exposed in Scala side as well, no?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
