[
https://issues.apache.org/jira/browse/AIRAVATA-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454048#comment-13454048
]
Suresh Marru commented on AIRAVATA-568:
---------------------------------------
The experiment id unique is only requirement for a registry. Keeping topic id
unique is a firm requirement for orchestration system. Since the API and data
system integration evolved in a way (which has been well discussed) the API is
a unified entry into the system and external data systems will be integrated
through provenance abstractions, it makes perfect sense to assume experiment id
and topic id are handled identically. As for the use case, lets try to
understand it like this, when we subit to a batch system on a cluster, we
cannot expect to send the job id and expect the PBS server to honor it. Its the
job of the client to maintain the correlation and its perfectly reasonable to
assume that.
As for the use case, if it is with data systems like XMCCat, it was discussed
at lengths previously and its agreed upon by every one thats its a bad idea to
assume a data system unique id be expected by a workflow system to grant
uniqueness. Workflow is only an instantiation and data is persistant. Lets not
confuse with Airavata internal experiment id vs topic id. For external system
integration like ODI, Airavata is a enactment system and the server issues a
unique id for that instantiation. I still say the server accepting a unique id
from client is a bad design choice irrespective of the state of API.
> Method to set messaging topic from airavata client
> --------------------------------------------------
>
> Key: AIRAVATA-568
> URL: https://issues.apache.org/jira/browse/AIRAVATA-568
> Project: Airavata
> Issue Type: Improvement
> Reporter: Raminderjeet Singh
>
> These need to a method to set messaging topic from airavata API for advanced
> clients to sent the information
--
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
