I am not sure about the impact that nesting would cause, but if you have a lot of fields (nested or not) in one record, then drill might have some trouble in allocating memory for each field. If I just want to test how deep drill can dig, I will create a json document which has a single field at depth "n". Increase "n" until it breaks.
- Rahul On Thu, Sep 24, 2015 at 3:26 PM, Stefán Baxter <ste...@activitystream.com> wrote: > Hi Chun, > > Can you please explain to me what you mean by nesting levels? > > Because the way I understand it, having 1800 nesting levels makes no sense > :). > > Regards, > -Stefan > > On Thu, Sep 24, 2015 at 9:18 PM, Chun Chang <cch...@maprtech.com> wrote: > > > For JSON data format, what is the recommended/supported nesting levels > > Drill can handle? I think we should establish a limit and make it into > the > > documentation. > > > > I tried querying a json file with 1800 nesting levels. The query never > came > > back, even after three hours. > > > > Thanks, > > Chun > > >
