[
https://issues.apache.org/jira/browse/OOZIE-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13970309#comment-13970309
]
Purshotam Shah commented on OOZIE-1769:
---------------------------------------
Rat error
{quote}
1 Unknown Licenses
*******************************
Unapproved licenses:
docs/src/site/twiki/DG_CommandLineTool.twiki.orig
*******************************
{quote}
lines > 132 are twiki and NamedQuery
{quote}
*******Test lines greater than 132
+ @NamedQuery(name = "UPDATE_COORD_JOB", query = "update
CoordinatorJobBean w set w.appName = :appName, w.appPath =
:appPath,w.concurrency = :concurrency, w.conf = :conf, w.externalId =
:externalId, w.frequency = :frequency, w.lastActionNumber = :lastActionNumber,
w.timeOut = :timeOut, w.timeZone = :timeZone, w.createdTimestamp =
:createdTime, w.endTimestamp = :endTime, w.execution = :execution, w.jobXml =
:jobXml, w.lastActionTimestamp = :lastAction, w.lastModifiedTimestamp =
:lastModifiedTime, w.nextMaterializedTimestamp = :nextMaterializedTime,
w.origJobXml = :origJobXml, w.slaXml=:slaXml, w.startTimestamp = :startTime,
w.statusStr = :status, w.timeUnitStr = :timeUnit, w.appNamespace =
:appNamespace, w.bundleId = :bundleId, w.matThrottling = :matThrottling where
w.id = :id"),
+ return (bean.getStatus() == CoordinatorAction.Status.WAITING
|| bean.getStatus() == CoordinatorAction.Status.SUBMITTED);
+<coordinator-app xmlns="uri:oozie:coordinator:0.4" name="${name}"
frequency="${coord:days(1)}" start="${start}" end="${end}" timezone="${unit}">
+Existing coordinator definition will be replaced by new definition. The
refreshed coordinator would keep the same coordinator ID, state, and
coordinator actions.
+Update command doesn't allow update of coordinator name, frequency, start
time, end time and timezone and will fail on an attempt to change any of them.
To change end time of coordinator use the =-change= command
+- <dataset name="raw-logs" frequency="20"
initial-instance="2010-01-01T00:00Z" timezone="UTC" freq_timeunit="MINUTE"
end_of_duration="NONE">
++ <dataset name="raw-logs-rename" frequency="20"
initial-instance="2010-01-01T00:00Z" timezone="UTC" freq_timeunit="MINUTE"
end_of_duration="NONE">
+Existing coordinator definition and properties will be replaced by new
definition and properties. Refer
[[DG_CommandLineTool#Updating_coordinator_definition_and_properties][Updating
coordinator definition and properties]]
+ {"diff":"**********Job definition
changes**********\n******************************************\n**********Job
conf changes****************\n@@ -8,16 +8,12 @@\n
+
<value>hdfs:\/\/localhost:9000\/user\/purushah\/examples\/apps\/aggregator\/coordinator.xml<\/value>\r\n
<\/property>\r\n <property>\r\n
{quote}
2 failed test cases are unrelated and they succeed in my local system.
> An option to update coord properties/definition
> -----------------------------------------------
>
> Key: OOZIE-1769
> URL: https://issues.apache.org/jira/browse/OOZIE-1769
> Project: Oozie
> Issue Type: Bug
> Reporter: Purshotam Shah
> Assignee: Purshotam Shah
> Attachments: OOZIE-1769-V5.patch
>
>
> To change the coord definition user can update coord definition in hdfs and
> issue a update command. Existing coordinator definition will be replaced by
> new definition. The refreshed coordinator
> would keep the same coordinator ID, state, and coordinator actions.
> User can also provide -dryrun to validate changes.
> All created coord action(including in waiting) will use old configuration.
> User can rerun actions with -refresh option, -refresh option will use new
> configuration to rerun coord action.
> Ex.
> 1. $ oozie job -update <coordID> -config
> examples/apps/aggregator/job.properties
> Will update coord definition and action.
> 2. $ oozie job -update <coordID>
> Will fetch coord definition path from bundle and update coord definition
--
This message was sent by Atlassian JIRA
(v6.2#6252)
