Bashir Sadjad

Thanks for filing this issue @Charantl. Can you please elaborate a little more on what the use-case is? Adding historical versions of a resource to the data-warehouse is doable but...

Given that our "database as DWH" story is maturing (especially with support for SQL-on-FHIR-v2 views), this bug is more important to be fixed. There is also some renewed interest in...

> I might be interested as a sequel to #967 That would be great; please feel free to assign this to yourself once you start working on it.

Thanks for the suggestion. Yes, if we decide to make the data consolidation features of the pipelines production-ready, we need to add some sort of resource tracking feature too. This...

This is related to both #825 and #923. Depending on how/if we support those features and if we end up with supporting multiple FHIR-sources, we may want to implement this...

Thanks @anhvdq for the note; yes I agree we should evaluate Trino too. I became aware of the blog post you shared a while ago but it seems to me...

BTW, @anhvdq if you have experience with either Presto or Trino and like to do this evaluation with FHIR Parquet files that our pipelines produce, please let me know and...

> We have fixed our issue, but the build has failed for a different reason. I'm not sure why the request only for Observations would timeout. Could a re-run of...

BTW, may I ask what FHIR server are you running the pipelines against? In general, can you describe your use-case a little bit (if you don't mind)? The problem as...

> Any hints on this latest failure would be appreciated. The problem seems to be that one patient data is missing from the generated Parquet files. I am not sure...