This relates to the number of formats that I would like to bring under Drill.
In business, documents frequently represent hierarchical transactions - orders, claims, patient visits, inventory lookups. These have hierarchical structures that, at least have header data, line items and, sometimes, footer data. For example: transaction identifier record order details (which can be nested) with store details - location, date, time, customer items - which are typically flat but can some level of nesting transaction footer XML, JSON and EDI all can be in this structure. Typically, the depth and type of nesting is standardized, so there should be no issues with non-deterministic, computationally unfeasible nested, cyclic hierarchies. *My question - has this been handled already in Drill and storage formats?* If so, where? If not,what is your recommendation for handling this? Should it be in an independent library outside of Drill that presents a flattened version (not sure if this is possible), or maybe break the message into tables corresponding to header data, items, footer. Please advise. Edmon
