airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Christie (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AIRAVATA-2335) Deploy 0.17-SNAPSHOT on Jetstream for testing
Date Fri, 31 Mar 2017 14:09:41 GMT

    [ https://issues.apache.org/jira/browse/AIRAVATA-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932944#comment-15932944
] 

Marcus Christie edited comment on AIRAVATA-2335 at 3/31/17 2:08 PM:
--------------------------------------------------------------------

Another problem, Anuj's DB server is running in strict mode and doesn't allow settings a default
TIMESTAMP with a zero date

{code:sql}
CREATE TABLE WORKFLOW
(
        TEMPLATE_ID VARCHAR (255) NOT NULL,
        WORKFLOW_NAME VARCHAR (255) NOT NULL,
        CREATED_USER VARCHAR (255),
        GATEWAY_ID VARCHAR (255),
        GRAPH LONGTEXT,
        IMAGE BLOB,
        CREATION_TIME timestamp DEFAULT NOW(),
        UPDATE_TIME TIMESTAMP DEFAULT '0000-00-00 00:00:00',
--         UPDATE_TIME TIMESTAMP DEFAULT NOW() ON UPDATE NOW(),
        PRIMARY KEY (TEMPLATE_ID)
);
...
{code}

For now I've workaround around this by commenting out 
{code}
--        UPDATE_TIME TIMESTAMP DEFAULT '0000-00-00 00:00:00',
{code}
and uncommenting 
{code}
         UPDATE_TIME TIMESTAMP DEFAULT NOW() ON UPDATE NOW(),
{code}

I just made the change locally, on the jetstream instance, to get the server started up.

I'm not sure what the best long term fix is. I think we can switch to having a {{DEFAULT NOW()}}
on that column. Looks like [this was fixed in 5.6/MariaDB 10.0|https://mariadb.com/kb/en/mariadb/timestamp/].

----
I've gone ahead and committed this change since it seems safe.



was (Author: marcuschristie):
Another problem, Anuj's DB server is running in strict mode and doesn't allow settings a default
TIMESTAMP with a zero date

{code:sql}
CREATE TABLE WORKFLOW
(
        TEMPLATE_ID VARCHAR (255) NOT NULL,
        WORKFLOW_NAME VARCHAR (255) NOT NULL,
        CREATED_USER VARCHAR (255),
        GATEWAY_ID VARCHAR (255),
        GRAPH LONGTEXT,
        IMAGE BLOB,
        CREATION_TIME timestamp DEFAULT NOW(),
        UPDATE_TIME TIMESTAMP DEFAULT '0000-00-00 00:00:00',
--         UPDATE_TIME TIMESTAMP DEFAULT NOW() ON UPDATE NOW(),
        PRIMARY KEY (TEMPLATE_ID)
);
...
{code}

For now I've workaround around this by commenting out 
{code}
--        UPDATE_TIME TIMESTAMP DEFAULT '0000-00-00 00:00:00',
{code}
and uncommenting 
{code}
         UPDATE_TIME TIMESTAMP DEFAULT NOW() ON UPDATE NOW(),
{code}

I just made the change locally, on the jetstream instance, to get the server started up.

I'm not sure what the best long term fix is. I think we can switch to having a {{DEFAULT NOW()}}
on that column. Looks like [this was fixed in 5.6/MariaDB 10.0|https://mariadb.com/kb/en/mariadb/timestamp/].

> Deploy 0.17-SNAPSHOT on Jetstream for testing
> ---------------------------------------------
>
>                 Key: AIRAVATA-2335
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2335
>             Project: Airavata
>          Issue Type: Task
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>
> Use Ansible to deploy Airavata version 0.17-SNAPSHOT for testing before 0.17 is released.
> Notes:
> * Airavata is deployed on 149.165.168.5
> * Seagrid PGA is deployed on http://149.165.156.11/
> * Scigap PGA is deployed on http://149.165.156.52/
> * Testdrive PGA is deployed on http://149.165.156.148/
> * DB is deployed on 149.165.172.163



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message