[jira] [Comment Edited] (AIRAVATA-3697) Handle unicode characters in file names

2023-06-26 Thread Marcus Christie (Jira) 


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

Marcus Christie edited comment on AIRAVATA-3697 at 6/26/23 8:33 PM:


I'm using mariadb-tools to do an online conversion of a large instance of 
replica_catalog. First, I'm doing a dry run on a copy of the database:
{code:java}
MariaDB> create database replica_catalog_copy DEFAULT CHARACTER SET utf8 
COLLATE utf8_bin;
{code}
{code:java}
mysqldump replica_catalog > replica_catalog.sql
mysql replica_catalog_copy < replica_catalog.sql
{code}
Need to remove the foreign keys for this to work
{code:java}
ALTER TABLE DATA_PRODUCT DROP FOREIGN KEY DATA_PRODUCT_ibfk_1;
ALTER TABLE DATA_PRODUCT_METADATA DROP FOREIGN KEY DATA_PRODUCT_METADATA_ibfk_1;
ALTER TABLE DATA_REPLICA_LOCATION DROP FOREIGN KEY DATA_REPLICA_LOCATION_ibfk_1;
ALTER TABLE DATA_REPLICA_METADATA DROP FOREIGN KEY DATA_REPLICA_METADATA_ibfk_1;
{code}
Running mariadb-tools to do the incremental, online character set conversion
{code:java}
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=DATA_PRODUCT --execute
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=DATA_PRODUCT_METADATA --execute
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=DATA_REPLICA_LOCATION --execute
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=DATA_REPLICA_METADATA --execute
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=CONFIGURATION --execute
{code}
Using mariadb-schema-change to add back constraints:
{code:java}
mariadb-schema-change --alter "ADD CONSTRAINT DATA_PRODUCT_ibfk_1 FOREIGN KEY 
(PARENT_PRODUCT_URI) REFERENCES DATA_PRODUCT (PRODUCT_URI) ON DELETE CASCADE" 
D=replica_catalog_copy,t=DATA_PRODUCT --execute
mariadb-schema-change --alter "ADD CONSTRAINT DATA_PRODUCT_METADATA_ibfk_1 
FOREIGN KEY (PRODUCT_URI) REFERENCES DATA_PRODUCT (PRODUCT_URI) ON DELETE 
CASCADE" D=replica_catalog_copy,t=DATA_PRODUCT_METADATA --execute
mariadb-schema-change --alter "ADD CONSTRAINT DATA_REPLICA_LOCATION_ibfk_1 
FOREIGN KEY (PRODUCT_URI) REFERENCES DATA_PRODUCT (PRODUCT_URI) ON DELETE 
CASCADE" D=replica_catalog_copy,t=DATA_REPLICA_LOCATION --execute
mariadb-schema-change --alter "ADD CONSTRAINT DATA_REPLICA_METADATA_ibfk_1 
FOREIGN KEY (REPLICA_ID) REFERENCES DATA_REPLICA_LOCATION (REPLICA_ID) ON 
DELETE CASCADE" D=replica_catalog_copy,t=DATA_REPLICA_METADATA --execute
{code}


was (Author: marcuschristie):
I'm using mariadb-tools to do an online conversion of a large instance of 
replica_catalog. First, I'm doing a dry run on a copy of the database:

{code}
MariaDB> create database replica_catalog_copy DEFAULT CHARACTER SET utf8 
COLLATE utf8_bin;
{code}

{code}
mysqldump replica_catalog > replica_catalog.sql
mysql replica_catalog_copy < replica_catalog.sql
{code}

Need to remove the foreign keys for this to work

{code}
ALTER TABLE DATA_PRODUCT DROP FOREIGN KEY DATA_PRODUCT_ibfk_1;
ALTER TABLE DATA_PRODUCT_METADATA DROP FOREIGN KEY DATA_PRODUCT_METADATA_ibfk_1;
ALTER TABLE DATA_REPLICA_LOCATION DROP FOREIGN KEY DATA_REPLICA_LOCATION_ibfk_1;
ALTER TABLE DATA_REPLICA_METADATA DROP FOREIGN KEY DATA_REPLICA_METADATA_ibfk_1;
{code}

Running mariadb-tools to do the incremental, online character set conversion
{code}
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=DATA_PRODUCT --execute
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=DATA_PRODUCT_METADATA --execute
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=DATA_REPLICA_LOCATION --execute
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=DATA_REPLICA_METADATA --execute
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=CONFIGURATION --execute
{code}


Using mariadb-schema-change to add back constraints:
{code}
mariadb-schema-change --alter "ADD CONSTRAINT DATA_PRODUCT_ibfk_1 FOREIGN KEY 
(PARENT_PRODUCT_URI) REFERENCES DATA_PRODUCT (PRODUCT_URI) ON DELETE CASCADE" 
D=replica_catalog_copy,t=DATA_PRODUCT --execute
mariadb-schema-change --alter "ADD CONSTRAINT DATA_PRODUCT_METADATA_ibfk_1 
FOREIGN KEY (PRODUCT_URI) REFERENCES DATA_PRODUCT (PRODUCT_URI) ON DELETE 
CASCADE" D=replica_catalog_copy,t=DATA_PRODUCT_METADATA 
--executemariadb-schema-change --alter "ADD CONSTRAINT 
DATA_REPLICA_LOCATION_ibfk_1 FOREIGN KEY (PRODUCT_URI) REFERENCES DATA_PRODUCT 
(PRODUCT_URI) ON DELETE CASCADE" D=replica_catalog_copy,t=DATA_REPLICA_LOCATION 
--execute

[jira] [Comment Edited] (AIRAVATA-3697) Handle unicode characters in file names

2023-06-26 Thread Marcus Christie (Jira) 


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

Marcus Christie edited comment on AIRAVATA-3697 at 6/26/23 8:32 PM:


I'm using mariadb-tools to do an online conversion of a large instance of 
replica_catalog. First, I'm doing a dry run on a copy of the database:

{code}
MariaDB> create database replica_catalog_copy DEFAULT CHARACTER SET utf8 
COLLATE utf8_bin;
{code}

{code}
mysqldump replica_catalog > replica_catalog.sql
mysql replica_catalog_copy < replica_catalog.sql
{code}

Need to remove the foreign keys for this to work

{code}
ALTER TABLE DATA_PRODUCT DROP FOREIGN KEY DATA_PRODUCT_ibfk_1;
ALTER TABLE DATA_PRODUCT_METADATA DROP FOREIGN KEY DATA_PRODUCT_METADATA_ibfk_1;
ALTER TABLE DATA_REPLICA_LOCATION DROP FOREIGN KEY DATA_REPLICA_LOCATION_ibfk_1;
ALTER TABLE DATA_REPLICA_METADATA DROP FOREIGN KEY DATA_REPLICA_METADATA_ibfk_1;
{code}

Running mariadb-tools to do the incremental, online character set conversion
{code}
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=DATA_PRODUCT --execute
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=DATA_PRODUCT_METADATA --execute
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=DATA_REPLICA_LOCATION --execute
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=DATA_REPLICA_METADATA --execute
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=CONFIGURATION --execute
{code}


Using mariadb-schema-change to add back constraints:
{code}
mariadb-schema-change --alter "ADD CONSTRAINT DATA_PRODUCT_ibfk_1 FOREIGN KEY 
(PARENT_PRODUCT_URI) REFERENCES DATA_PRODUCT (PRODUCT_URI) ON DELETE CASCADE" 
D=replica_catalog_copy,t=DATA_PRODUCT --execute
mariadb-schema-change --alter "ADD CONSTRAINT DATA_PRODUCT_METADATA_ibfk_1 
FOREIGN KEY (PRODUCT_URI) REFERENCES DATA_PRODUCT (PRODUCT_URI) ON DELETE 
CASCADE" D=replica_catalog_copy,t=DATA_PRODUCT_METADATA 
--executemariadb-schema-change --alter "ADD CONSTRAINT 
DATA_REPLICA_LOCATION_ibfk_1 FOREIGN KEY (PRODUCT_URI) REFERENCES DATA_PRODUCT 
(PRODUCT_URI) ON DELETE CASCADE" D=replica_catalog_copy,t=DATA_REPLICA_LOCATION 
--execute
mariadb-schema-change --alter "ADD CONSTRAINT DATA_REPLICA_METADATA_ibfk_1 
FOREIGN KEY (REPLICA_ID) REFERENCES DATA_REPLICA_LOCATION (REPLICA_ID) ON 
DELETE CASCADE" D=replica_catalog_copy,t=DATA_REPLICA_METADATA --execute
{code}



was (Author: marcuschristie):
I'm using mariadb-tools to do an online conversion of a large instance of 
replica_catalog. First, I'm doing a dry run on a copy of the database:

{code}
MariaDB> create database replica_catalog_copy DEFAULT CHARACTER SET utf8 
COLLATE utf8_bin;
{code}

{code}
mysqldump replica_catalog > replica_catalog.sql
mysql replica_catalog_copy < replica_catalog.sql
{code}

Need to remove the foreign keys for this to work

{code}
ALTER TABLE DATA_PRODUCT DROP FOREIGN KEY DATA_PRODUCT_ibfk_1;
ALTER TABLE DATA_PRODUCT_METADATA DROP FOREIGN KEY DATA_PRODUCT_METADATA_ibfk_1;
ALTER TABLE DATA_REPLICA_LOCATION DROP FOREIGN KEY DATA_REPLICA_LOCATION_ibfk_1;
ALTER TABLE DATA_REPLICA_METADATA DROP FOREIGN KEY DATA_REPLICA_METADATA_ibfk_1;
{code}

Running mariadb-tools to do the incremental, online character set conversion
{code}
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=DATA_PRODUCT --execute
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=DATA_PRODUCT_METADATA --execute
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=DATA_REPLICA_LOCATION --execute
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=DATA_REPLICA_METADATA --execute
mariadb-schema-change --alter "CONVERT TO CHARACTER SET utf8 COLLATE utf8_bin" 
D=replica_catalog_copy,t=CONFIGURATION --execute
{code}

After it's done, I'll add the FKs back
{code}
ALTER TABLE DATA_PRODUCT  ADD CONSTRAINT DATA_PRODUCT_ibfk_1 FOREIGN KEY 
(`PARENT_PRODUCT_URI`) REFERENCES `DATA_PRODUCT` (`PRODUCT_URI`) ON DELETE 
CASCADE;
ALTER TABLE DATA_PRODUCT_METADATA ADD CONSTRAINT `DATA_PRODUCT_METADATA_ibfk_1` 
FOREIGN KEY (`PRODUCT_URI`) REFERENCES `DATA_PRODUCT` (`PRODUCT_URI`) ON DELETE 
CASCADE;
ALTER TABLE DATA_REPLICA_LOCATION ADD CONSTRAINT `DATA_REPLICA_LOCATION_ibfk_1` 
FOREIGN KEY (`PRODUCT_URI`) REFERENCES `DATA_PRODUCT` (`PRODUCT_URI`) ON DELETE 
CASCADE;
ALTER TABLE DATA_REPLICA_METADATA ADD CONSTRAINT `DATA_REPLICA_METADATA_ibfk_1` 
FOREIGN KEY (`REPLICA_ID`) REFERENCES `DATA_REPLICA_LOCATION` (`REPLICA_ID`) ON 
DELETE CASCADE;
{code}



>

[jira] [Created] (AIRAVATA-3699) Upgrade Django Portal frontend to use Vue 3

2023-06-26 Thread Marcus Christie (Jira) 
Marcus Christie created AIRAVATA-3699:
-

 Summary: Upgrade Django Portal frontend to use Vue 3
 Key: AIRAVATA-3699
 URL: https://issues.apache.org/jira/browse/AIRAVATA-3699
 Project: Airavata
  Issue Type: Improvement
  Components: Django Portal
Reporter: Marcus Christie


The Django Portal Vue.js code currently uses Vue 2.6. Vue 2 is reaching it's 
end-of-life (EOL) on Dec 31, 2023 (https://v2.vuejs.org/lts/). It would be good 
to upgrade to Vue 3 before that happens.



Vue 3 Migration Guide:
https://v3-migration.vuejs.org/




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (AIRAVATA-3698) Add support for Python 3.11

2023-06-26 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on AIRAVATA-3698:
---

Commit 54c7adf1ab2d33b062eb77bf0741363529e4717f in airavata's branch 
refs/heads/AIRAVATA-3698--Add-support-for-Python-3.11 from Marcus Christie
[ https://gitbox.apache.org/repos/asf?p=airavata.git;h=54c7adf1ab ]

AIRAVATA-3698 Update mod_wsgi to work with Py 3.9


> Add support for Python 3.11
> ---
>
> Key: AIRAVATA-3698
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3698
> Project: Airavata
>  Issue Type: Improvement
>  Components: Django Portal
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> Upgrade Wagtail and Django versions to get Python 3.11 support



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (AIRAVATA-3698) Add support for Python 3.11

2023-06-26 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on AIRAVATA-3698:
---

Commit e036cf70a0ce36f0683363047b239b91385e9b10 in airavata's branch 
refs/heads/AIRAVATA-3698--Add-support-for-Python-3.11 from Marcus Christie
[ https://gitbox.apache.org/repos/asf?p=airavata.git;h=e036cf70a0 ]

AIRAVATA-3698 Switch Django deploy to Python 3.9


> Add support for Python 3.11
> ---
>
> Key: AIRAVATA-3698
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3698
> Project: Airavata
>  Issue Type: Improvement
>  Components: Django Portal
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> Upgrade Wagtail and Django versions to get Python 3.11 support



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (AIRAVATA-3698) Add support for Python 3.11

2023-06-26 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on AIRAVATA-3698:
---

Commit 7dfe250751bc4be6f644cbc1a45acfdbae53e96c in airavata-django-portal's 
branch refs/heads/AIRAVATA-3698--Add-support-for-Python-3.11 from Marcus 
Christie
[ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=7dfe2507 ]

AIRAVATA-3698 Pull in fixes for EntryPoint properties


> Add support for Python 3.11
> ---
>
> Key: AIRAVATA-3698
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3698
> Project: Airavata
>  Issue Type: Improvement
>  Components: Django Portal
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> Upgrade Wagtail and Django versions to get Python 3.11 support



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (AIRAVATA-3698) Add support for Python 3.11

2023-06-26 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on AIRAVATA-3698:
---

Commit 1bb6b2ab5f4273188e91cadc28c236a931042086 in 
airavata-django-portal-commons's branch refs/heads/main from Marcus Christie
[ 
https://gitbox.apache.org/repos/asf?p=airavata-django-portal-commons.git;h=1bb6b2a
 ]

AIRAVATA-3698 Fix renames of EntryPoint properties


> Add support for Python 3.11
> ---
>
> Key: AIRAVATA-3698
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3698
> Project: Airavata
>  Issue Type: Improvement
>  Components: Django Portal
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> Upgrade Wagtail and Django versions to get Python 3.11 support



--
This message was sent by Atlassian Jira
(v8.20.10#820010)