Thank you Tomer, Kristine and Jacques _____________
john o schneider [email protected] 408-203-7891 On Sat, Aug 1, 2015 at 10:06 PM, Kristine Hahn <[email protected]> wrote: > Please see > http://drill.apache.org/docs/json-data-model/#limitations-and-workarounds > and > other sections on that page. Feedback is welcomed! > > On Saturday, August 1, 2015, John Schneider <[email protected]> wrote: > > > Hi All, > > > > Is there a pointer to a document that describes Drill's strengths and > > weaknesses > > handling JSON data sources, particularly when it comes to "schema > change". > > My > > use case is log processing and while my logs have a high degree of > > similarity, > > logs are what they are and there are differences and so I routinely get > > messages > > like: > > > > 0: jdbc:drill:drillbit=drill.apixio.com> select * from > > dfs.`user`.`/logmaster/production/hcc/2015-07-30/` t where t.level = > > 'ERROR'; > > > > Java.lang.RuntimeException: java.sql.SQLException: DATA_READ ERROR: Error > > parsing JSON - You tried to start when you are using a ValueWriter of > type > > NullableVarCharWriterImpl. > > > > 0: jdbc:drill:drillbit=drill.apixio.com> select * from > > dfs.`user`.`/logmaster/production/hcc/2015-07-29/` t where t.level = > > 'ERROR'; > > > > Error: DATA_READ ERROR: Error parsing JSON - You tried to write a BigInt > > type when you are using a ValueWriter of type NullableVarCharWriterImpl. > > > > there are quite a few different error types that come from the same log > > files which I presume is due to different schema transitions > > > > Thanks! > > > > > > _____________ > > > > john o schneider > > [email protected] <javascript:;> > > 408-203-7891 > > > > > -- > Kristine Hahn > Sr. Technical Writer > 415-497-8107 @krishahn skype:krishahn >
