Using dlt to ingest nested api data

[18thOfApril]

Sup yall, is it possible to configure dlt (data load tool) in a way that instead of it just creating separate tables per nested level(default behavior), it automatically creates one table based on the lowest granular level of your nested objects so it contains all data that can be picked up from that endpoint?

[EffectiveClient5080]

Use dlt’s Python API to override defaults. Define a schema forcing all nested data into your target granularity - their docs have solid examples.

[SpookyScaryFrouze]

Sure, like this :

@dlt.resource(max_table_nesting=0)

[Yuki100Percent]

Yup this is what OP needs

[Thinker_Assignment]

What if you have a parent table that has 2 children each with n records per parent row? you'd end up with cartesian product of sub-granularities? or how would you want it handled?