[
https://issues.apache.org/jira/browse/HIVE-18046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248062#comment-16248062
]
Gopal V commented on HIVE-18046:
--------------------------------
bq. Hmm... directsql does not have write statements as far as I know
I meant to say "direct sql compatibility" instead of this being about thrift
access (i.e older embedded metastore + new sql backend).
The error is that create table fails with a mysql constraint error - because
the old insert doesn't insert that col (and default is NULL and the col is
constrained as NOT NULL).
> Metastore: default IS_REWRITE_ENABLED=false instead of NULL
> -----------------------------------------------------------
>
> Key: HIVE-18046
> URL: https://issues.apache.org/jira/browse/HIVE-18046
> Project: Hive
> Issue Type: Bug
> Components: Materialized views, Metastore
> Affects Versions: 3.0.0
> Reporter: Gopal V
> Priority: Minor
>
> The materialized view impl breaks old metastore sql write access, by
> complaining that the new table creation does not set this column up.
> {code}
> `IS_REWRITE_ENABLED` bit(1) NOT NULL,
> {code}
> {{NOT NULL DEFAULT 0}} would allow old metastore directsql compatibility.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
