[jira] [Commented] (AIRAVATA-562) Replacing existing Jackrabbit registry with MySQL

["Saminda Wijeratne (JIRA)" <ji...@apache.org>]

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

Saminda Wijeratne commented on AIRAVATA-562:
--------------------------------------------

registry.sql
========

1. Few things that may needs changing
published workflows are for per project right?
we did not discuss this earlier, but how about adding "topic_id" as well to the experiments table? We use topic id to monitor an experiment. (right now both experiment id & the topic id is the same, but the feature does not require it to be)
thinking the pros and cons of having an integer "id" feild (primary key) for the descriptors and have a varchar name field? In that way we wont have descriptor id duplication issues among gateways.

2. A few suggestions on the names,

Projects.project_id => Projects.id (similarly for other tables as well)

publish_workflow_name => name
workflow_content => graph

host_descriptor_xml => descriptor

Publish_Workflow => Published_Workflows
Host_Descriptor => Host_Descriptors

3. Couple of things that might be useful to have but not a must (thinking aloud here)
Adding a few metadata (last saved dates, author of descriptor, user full name/contacts/photo, data expiration dates)

                
> Replacing existing Jackrabbit registry with MySQL
> -------------------------------------------------
>
>                 Key: AIRAVATA-562
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-562
>             Project: Airavata
>          Issue Type: New Feature
>          Components: Registry API
>    Affects Versions: 0.4-INCUBATING
>            Reporter: Chathuri Wimalasena
>             Fix For: 0.5-INCUBATING
>
>         Attachments: AIRAVATA-562.1.patch, registry.sql
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira