In pipelinewise-target-redshift, I have found that not all columns de-nested. Like below screenshot, in person column data is nested , i have tried maximise the data_flattening_max_level upto 1000 but it seems to be not working now. It was de-nesting the some of data in person column  earlier  but now it's not able to fetch the nested columns. Wonder if anybody face this issue and can guide what step should i have to take. For reference my target-redshift configuration:

loaders:

 - name: redshift-pipelinewise   namespace: target_redshift   pip_url: git+https://github.com/ryan-miranda-partners/Redshift-pipelinewise>   executable: target-redshift   config:    host: xxxxxxxxxxx2.redshift.amazonaws.com    user: meltano    dbname: vegrxxx    s3_bucket: meltano-bucket    data_flattening_max_level: 1000    port: 5439    password: xxxxx    aws_secret_access_key: xxxxxxxxxxx    aws_access_key_id: xxxxxxxxxxxx Screenshot 2021-09-20 at 5.55.56 PM.png

It's definitely a target-redshift thing, I don't know what should/shouldn't be happening. An issue to that repo is probably the best way, and then it's looking into the target-redshift code to see how denesting is set up and why the examples you gave dont work

@monika_rajput how did you end up fixing this?