[
https://issues.apache.org/jira/browse/FALCON-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915922#comment-13915922
]
Srikanth Sundarrajan commented on FALCON-286:
---------------------------------------------
With FALCON-206, each update is maintained in isolated location, so the
coord-id itself can act as a distinct identifier for a version. Would that
avoid any specific version attribute maintained by the user.
{code}
+ String version;
+ try {
+ version = BuildProperties.get().getProperty("build.version");
+ } catch (Exception e) { // unfortunate that this is only available in
prism/webapp
+ version = "0.5";
+ }
{code}
We ought to have a better way of setting falcon-workflow version for
replication/retention.
> Capture information in process entity about the user workflow
> -------------------------------------------------------------
>
> Key: FALCON-286
> URL: https://issues.apache.org/jira/browse/FALCON-286
> Project: Falcon
> Issue Type: Sub-task
> Affects Versions: 0.5
> Reporter: Venkatesh Seetharam
> Assignee: Venkatesh Seetharam
> Labels: lineage
> Attachments: FALCON-286.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
