Chandrashekar Sankarapu

Hi @mozzy11, usually any errors that occur in the pipeline run are not printed in the logs since the docker is ran in the detached mode. You can use this...

@mozzy11 Thanks for the update. Currently, the build fails sometimes due to some issues which are mentioned in this [ticket](https://github.com/google/fhir-data-pipes/issues/656). So, the build fails sometimes and retriggering usually works. Regarding...

Hi @bashir2, thanks for the review. I have updated my comments and I have also created these 2 issues ([Relook at the recursive depth](https://github.com/google/fhir-data-pipes/issues/1062) and [Fix the number of parquet...

Thanks @bashir2 for the review, I have addressed the review comments and will be merging the PR. Please let me know if you see any discrepancies and I will take...

Hi @Charantl, thanks for filing this issue. Based on the current design of fhir-data-pipes, if a pipeline fails then the next pipeline that runs will start picking up records from...

e2e tests are failing, will debug more on this.

Hi @bashir2, this PR is ready for review, it contains changes for upgrading the HAPI library to 7.2.1

Thanks @bashir2 for the review. I have addressed the review comments, will merge the changes once the build completes.

Original Hapi object ``` { "resourceType": "Patient", "id": "example", "meta": { "profile": [ "http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient" ] }, "text": { "status": "generated", "div": "Generated Narrativeid: examplemeta: identifier: Medical Record Number: 1032702 (USUAL)active:...

Yes, this is just an extension for #547 to handle the case where the export target is a FHIR store or another JDBC store like Postgres. Since these cases were...