[
https://issues.apache.org/jira/browse/HIVE-6669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14162067#comment-14162067
]
Alan Gates commented on HIVE-6669:
----------------------------------
So what is now:
{code}
CREATE TABLE txns (
txn_id bigint PRIMARY KEY,
txn_state char(1) NOT NULL,
txn_started bigint NOT NULL,
txn_last_heartbeat bigint NOT NULL,
txn_user varchar(128) NOT NULL,
txn_host varchar(128) NOT NULL
);
{code}
would instead look like
{code}
CREATE TABLE 'txns' (
'txn_id' bigint PRIMARY KEY,
'txn_state' char(1) NOT NULL,
'txn_started' bigint NOT NULL,
'txn_last_heartbeat' bigint NOT NULL,
'txn_user' varchar(128) NOT NULL,
'txn_host' varchar(128) NOT NULL
);
{code}
Is that right?
> sourcing txn-script from schema script results in failure for mysql & oracle
> ----------------------------------------------------------------------------
>
> Key: HIVE-6669
> URL: https://issues.apache.org/jira/browse/HIVE-6669
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.14.0
> Reporter: Prasad Mujumdar
> Assignee: Alan Gates
> Priority: Blocker
> Attachments: HIVE-6669.patch
>
>
> This issues is addressed in 0.13 by in-lining the the transaction schema
> statements in the schema initialization script (HIVE-6559)
> The 0.14 schema initialization is not fixed. This is the followup ticket for
> to address the problem in 0.14.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
