On Thu, Jul 12, 2018 at 5:07 PM, Bharath Vissapragada < bhara...@cloudera.com.invalid> wrote:
> On Thu, Jul 12, 2018 at 12:03 PM Todd Lipcon <t...@cloudera.com.invalid> > wrote: > > > > So, I think my proposal here is: > > > > 1. Query behavior on existing tables > > - If the table-level format is non-Avro, > > - AND the table contains column types incompatible with Avro (eg > tinyint), > > - AND the table has an existing avro partition, > > - THEN the query will yield an error about incompatible types > > > > 2. Try to prevent shooting in the foot > > - If the table-level format is non-Avro, > > - AND the table contains column types incompatible with Avro (eg > tinyint), > > - THEN disallow changing the file format of an existing partition to Avro > > > > This approach sounds good to me. Is the existing behavior preserved for the > non-mixed-partition Avro based tables? > Yes, if the table-level properties indicate it's an Avro table we'll let the Avro schema (explicit or implicit) override the columns in the metastore. -Todd -- Todd Lipcon Software Engineer, Cloudera
