atlasmap: OOM during FHIR XML schema inspection

I fixed #573 and then hit OOM… It loaded 9,075,113 fields and died. A bit surprising that 9 millions of fields could be loaded as a AtlasMap Document model.

So definitely loading whole FHIR schema is unrealistic. Browser would crash even with thousands of fields. Nobody like to scroll hundreds of fields in AtlasMap UI and map one by one.

How can we slim it down to realistic number of fields? Is it even possible? We would need some “filtering” on inspection, as well as deeper understanding of FHIR object model and real usecases to figure out how to screw this gigantic object in to AtlasMap UI.

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 21 (15 by maintainers)

Commits related to this issue

fix: XML schema inspection should cache complex type to handle recursive item Fixes: #573 Still it can't inspect whole FHIR schema due to its incredible size (#577) — committed to igarashitm/atlasmap by igarashitm 6 years ago

Most upvoted comments

We create DataShapes for custom API client connectors from JSON schema and generate XML schema if the format for the API call is XML. For example here is how we do it for HTTP request shape:

https://github.com/syndesisio/syndesis/blob/0fc334e6d29b5bae40856251728c4ab7c82d6943/app/server/api-generator/src/main/java/io/syndesis/server/api/generator/swagger/UnifiedXmlDataShapeGenerator.java#L82

zregvart on Sep 21, 2018