Schema evolution on upsert (merge)

[ion-elgreco]

Discussed in #2281

^{Originally posted by cesar-vermeulen March 11, 2024}
Hello!

With the awsome addition of merge schema support in the write operation (kudos contributors @ #2246), I was wondering whether a similar functionality is on the roadmap for upsert transactions? Would be a great addition to the current functionalities!

Thanks,
Cheers!

[JonasDev1]

In order for this function to be useful, we first need to implement an updateAll / insertAll functionality.
Currently you need to specify all updates and inserts manually.

In the future something like that would be helpfull together with schema evolution:

let (table, metrics) = DeltaOps(table)
  .merge(source, "target.id = source.id")
  .with_source_alias("source")
  .with_target_alias("target")
  .when_matched_update(|update| {
   update.updateAll()
  }).unwrap()
  .when_not_matched_insert(|insert| {
    insert.insertAll()
  }).unwrap()
  .await
  .unwrap();

[rtyler]

@ion-elgreco I think with your recent improvements, we have this now right?

[ion-elgreco]

@ion-elgreco I think with your recent improvements, we have this now right?

No not on merge yet, we need to built it differently there since it needs to part of the projection expressions. We can reuse the merge schema functionality though to check whether the source and table schema is different and if they can be merged

[npgretz]

My org would love to see this functionality. The Python delta-rs package has proven to be less overhead for our ETL loads than spinning up Spark pods for every load to a delta table.

We cannot make the switch to delta-rs though if we need to completely overwrite the delta table to add new columns.

[ion-elgreco]

My org would love to see this functionality. The Python delta-rs package has proven to be less overhead for our ETL loads than spinning up Spark pods for every load to a delta table.

We cannot make the switch to delta-rs though if we need to completely overwrite the delta table to add new columns.

Unfortunately there is no one working on it or looking at it, if your org is in dire need of it, they might look for contractors who can build this feature.

I can support by reviewing a PR

[JustinRush80]

I can try to take this

[ion-elgreco]

I can try to take this

Ok great!