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

Lei Pan commented on CMDA-17:
-----------------------------

Hi Qihao:

That info is actually encoded in the urlLink. And the
number of dataset/var pairs can be 2 or more in
some services.

Please discuss with Jia to see if you guys can parse
the urlLink to get this and/or other info you need for
provenance collecting. The advantages are consistency
and less volume of the dictionary passed to your service.
If you have a good reason for this info to be assembled
inside entry.py, please let me know and I will do it.

Thanks,
-Lei


> testing the calls to the provenance service from all JPL services
> -----------------------------------------------------------------
>
>                 Key: CMDA-17
>                 URL: https://issues.apache.org/jira/browse/CMDA-17
>             Project: Apache Climate Model Diagnostic Analyzer
>          Issue Type: Test
>         Environment: Docker/CMU provenance service
>            Reporter: Lei Pan
>            Assignee: Qihao Bao
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Qihao:
> Please make the CMU provenance service ready to take the provenance data 
> submission, including the images and *.nc files, from all JPL services, and 
> let me know when you are ready to test.
> The JPL team has finished migrating to the new github repository you created 
> and merged all new features developed in-between into the new repository. We 
> have done testing to make sure all features, old and new, are working. We 
> have also implemented calls to the CMU provenance service in all our 
> services, and right now it is the time to test all of them with you. Once you 
> say OK to us, I will conduct the tests and record all "execution purpose" 
> texts here for you to verify that your provenance service does receive our 
> calls with no problem.
> Thanks,
> -Lei



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to