[
https://issues.apache.org/jira/browse/AIRAVATA-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16338084#comment-16338084
]
Dimuthu Upeksha commented on AIRAVATA-2625:
-------------------------------------------
This is might require few changes to output data staging task and there are few
restrictions. Because we need to read the file to extract the values, we need
to read the file content to the JVM heap. Risk of that is, if we read a large
file (several gigs) into the heap, it will cause OOM error and eventually the
whole JVM might crash. So we have to come up with a reasonable size cap for the
files that are scanned (2 - 5 MB?) and if the file is larger than that, we
simply ignore the file and notify the user that output file is too big to scan.
> Derive and present Text outputs in Experiment summary
> -----------------------------------------------------
>
> Key: AIRAVATA-2625
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2625
> Project: Airavata
> Issue Type: Bug
> Components: Airavata System
> Affects Versions: 0.18
> Reporter: Eroma
> Assignee: Suresh Marru
> Priority: Major
>
> Currently the available application outputs are in the form of stdout, stderr
> and URI (files). Going forward to have text (String, Integer, Float) outputs
> directly in the experiment summary.
> These text outputs to be displayed as key+value pairs and when defining
> should be defined a file to derive from, e.g. stdout
> At a given time from a single file one or many of these key+value pairs could
> be derived. Also gateway admin can define multiple files to derive multiple
> of these values.
> These would be displayed to user in experiment summary and in detailed
> experiment summary in admin dashboard experiment statistics.
> These should also be displayed to any other gateway user it is shared with.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
