Hi Jeszy, Thanks for your response.
We have a script that running on a daily basis and drop and create the tables to cover changes in our data schema or fields. Our script is taking the last file and build the schema based on it, so i don't think the log can detect such change. i didn't use the parquet-tools schema before, will search the internet about it and try it. On Wed, May 16, 2018 at 7:26 PM, Jeszy <jes...@gmail.com> wrote: > Hey Fawze, > > This is expected to work seamlessly (although that's a pretty big > upgrade). Do the logs report any issues? Does comparing the schemas of > the before/after upgrade-written files using 'parquet-tools schema > <file>' show any differences? > > Thanks! > > On 16 May 2018 at 12:47, Fawze Abujaber <fawz...@gmail.com> wrote: > > Hello Community, > > > > We are running in schema read issue after upgrading Impala from 2.3 to > 2.10 > > using Cloudera CDH 5.13.0 > > > > > > Our tables have alot of struct and arrays and after the upgrade all the > > historical data at arrays and structs shown as NULL while the new written > > data are shown correctly. > > > > Is it a known issue? or there was any action that i should care about > before > > i upgrade? > > > > > > > > -- > > Take Care > > Fawze Abujaber > -- Take Care Fawze Abujaber
