OOZIE-3217 Enable definition of admin users using oozie-site.xml (orova via andras...
[oozie.git] / core / src / main / resources / oozie-default.xml
1 <?xml version="1.0"?>
2 <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
3 <!--
4 Licensed to the Apache Software Foundation (ASF) under one
5 or more contributor license agreements. See the NOTICE file
6 distributed with this work for additional information
7 regarding copyright ownership. The ASF licenses this file
8 to you under the Apache License, Version 2.0 (the
9 "License"); you may not use this file except in compliance
10 with the License. You may obtain a copy of the License at
11
12 http://www.apache.org/licenses/LICENSE-2.0
13
14 Unless required by applicable law or agreed to in writing, software
15 distributed under the License is distributed on an "AS IS" BASIS,
16 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
17 See the License for the specific language governing permissions and
18 limitations under the License.
19 -->
20 <configuration>
21
22 <!-- ************************** VERY IMPORTANT ************************** -->
23 <!-- This file is in the Oozie configuration directory only for reference. -->
24 <!-- It is not loaded by Oozie, Oozie uses its own privatecopy. -->
25 <!-- ************************** VERY IMPORTANT ************************** -->
26
27 <property>
28 <name>oozie.output.compression.codec</name>
29 <value>gz</value>
30 <description>
31 The name of the compression codec to use.
32 The implementation class for the codec needs to be specified through another property oozie.compression.codecs.
33 You can specify a comma separated list of 'Codec_name'='Codec_class' for oozie.compression.codecs
34 where codec class implements the interface org.apache.oozie.compression.CompressionCodec.
35 If oozie.compression.codecs is not specified, gz codec implementation is used by default.
36 </description>
37 </property>
38
39 <property>
40 <name>oozie.external_monitoring.enable</name>
41 <value>false</value>
42 <description>
43 If the oozie functional metrics needs to be exposed to the metrics-server backend, set it to true
44 If set to true, the following properties has to be specified : oozie.metrics.server.name,
45 oozie.metrics.host, oozie.metrics.prefix, oozie.metrics.report.interval.sec, oozie.metrics.port
46 </description>
47 </property>
48
49 <property>
50 <name>oozie.external_monitoring.type</name>
51 <value>graphite</value>
52 <description>
53 The name of the server to which we want to send the metrics, would be graphite or ganglia.
54 </description>
55 </property>
56
57 <property>
58 <name>oozie.external_monitoring.address</name>
59 <value>http://localhost:2020</value>
60 </property>
61
62 <property>
63 <name>oozie.external_monitoring.metricPrefix</name>
64 <value>oozie</value>
65 </property>
66
67 <property>
68 <name>oozie.external_monitoring.reporterIntervalSecs</name>
69 <value>60</value>
70 </property>
71
72 <property>
73 <name>oozie.jmx_monitoring.enable</name>
74 <value>false</value>
75 <description>
76 If the oozie functional metrics needs to be exposed via JMX interface, set it to true.
77 </description>
78 </property>
79
80 <property>
81 <name>oozie.action.mapreduce.uber.jar.enable</name>
82 <value>false</value>
83 <description>
84 If true, enables the oozie.mapreduce.uber.jar mapreduce workflow configuration property, which is used to specify an
85 uber jar in HDFS. Submitting a workflow with an uber jar requires at least Hadoop 2.2.0 or 1.2.0. If false, workflows
86 which specify the oozie.mapreduce.uber.jar configuration property will fail.
87 </description>
88 </property>
89
90 <property>
91 <name>oozie.processing.timezone</name>
92 <value>UTC</value>
93 <description>
94 Oozie server timezone. Valid values are UTC and GMT(+/-)####, for example 'GMT+0530' would be India
95 timezone. All dates parsed and genered dates by Oozie Coordinator/Bundle will be done in the specified
96 timezone. The default value of 'UTC' should not be changed under normal circumtances. If for any reason
97 is changed, note that GMT(+/-)#### timezones do not observe DST changes.
98 </description>
99 </property>
100
101 <!-- Base Oozie URL: <SCHEME>://<HOST>:<PORT>/<CONTEXT> -->
102
103 <property>
104 <name>oozie.base.url</name>
105 <value>http://${oozie.http.hostname}:${oozie.http.port}/oozie</value>
106 <description>
107 Base Oozie URL.
108 </description>
109 </property>
110
111 <!-- Services -->
112
113 <property>
114 <name>oozie.system.id</name>
115 <value>oozie-${user.name}</value>
116 <description>
117 The Oozie system ID.
118 </description>
119 </property>
120
121 <property>
122 <name>oozie.systemmode</name>
123 <value>NORMAL</value>
124 <description>
125 System mode for Oozie at startup.
126 </description>
127 </property>
128
129 <property>
130 <name>oozie.delete.runtime.dir.on.shutdown</name>
131 <value>true</value>
132 <description>
133 If the runtime directory should be kept after Oozie shutdowns down.
134 </description>
135 </property>
136
137 <property>
138 <name>oozie.services</name>
139 <value>
140 org.apache.oozie.service.SchedulerService,
141 org.apache.oozie.service.MetricsInstrumentationService,
142 org.apache.oozie.service.MemoryLocksService,
143 org.apache.oozie.service.UUIDService,
144 org.apache.oozie.service.ELService,
145 org.apache.oozie.service.AuthorizationService,
146 org.apache.oozie.service.UserGroupInformationService,
147 org.apache.oozie.service.HadoopAccessorService,
148 org.apache.oozie.service.JobsConcurrencyService,
149 org.apache.oozie.service.URIHandlerService,
150 org.apache.oozie.service.DagXLogInfoService,
151 org.apache.oozie.service.SchemaService,
152 org.apache.oozie.service.LiteWorkflowAppService,
153 org.apache.oozie.service.JPAService,
154 org.apache.oozie.service.StoreService,
155 org.apache.oozie.service.SLAStoreService,
156 org.apache.oozie.service.DBLiteWorkflowStoreService,
157 org.apache.oozie.service.CallbackService,
158 org.apache.oozie.service.ActionService,
159 org.apache.oozie.service.ShareLibService,
160 org.apache.oozie.service.CallableQueueService,
161 org.apache.oozie.service.ActionCheckerService,
162 org.apache.oozie.service.RecoveryService,
163 org.apache.oozie.service.PurgeService,
164 org.apache.oozie.service.CoordinatorEngineService,
165 org.apache.oozie.service.BundleEngineService,
166 org.apache.oozie.service.DagEngineService,
167 org.apache.oozie.service.CoordMaterializeTriggerService,
168 org.apache.oozie.service.StatusTransitService,
169 org.apache.oozie.service.PauseTransitService,
170 org.apache.oozie.service.GroupsService,
171 org.apache.oozie.service.ProxyUserService,
172 org.apache.oozie.service.XLogStreamingService,
173 org.apache.oozie.service.JvmPauseMonitorService,
174 org.apache.oozie.service.SparkConfigurationService,
175 org.apache.oozie.service.SchemaCheckerService
176 </value>
177 <description>
178 All services to be created and managed by Oozie Services singleton.
179 Class names must be separated by commas.
180 </description>
181 </property>
182
183 <property>
184 <name>oozie.services.ext</name>
185 <value> </value>
186 <description>
187 To add/replace services defined in 'oozie.services' with custom implementations.
188 Class names must be separated by commas.
189 </description>
190 </property>
191
192 <property>
193 <name>oozie.service.XLogStreamingService.buffer.len</name>
194 <value>4096</value>
195 <description>4K buffer for streaming the logs progressively
196 </description>
197 </property>
198 <property>
199 <name>oozie.service.XLogStreamingService.error.buffer.len</name>
200 <value>2048</value>
201 <description>2K buffer for streaming the error logs
202 progressively
203 </description>
204 </property>
205
206 <property>
207 <name>oozie.service.XLogStreamingService.audit.buffer.len</name>
208 <value>3</value>
209 <description>Number of lines for streaming the audit logs
210 progressively
211 </description>
212 </property>
213
214 <!-- HCatAccessorService -->
215 <property>
216 <name>oozie.service.HCatAccessorService.jmsconnections</name>
217 <value>
218 default=java.naming.factory.initial#org.apache.activemq.jndi.ActiveMQInitialContextFactory;java.naming.provider.url#tcp://localhost:61616;connectionFactoryNames#ConnectionFactory
219 </value>
220 <description>
221 Specify the map of endpoints to JMS configuration properties. In general, endpoint
222 identifies the HCatalog server URL. "default" is used if no endpoint is mentioned
223 in the query. If some JMS property is not defined, the system will use the property
224 defined jndi.properties. jndi.properties files is retrieved from the application classpath.
225 Mapping rules can also be provided for mapping Hcatalog servers to corresponding JMS providers.
226 hcat://${1}.${2}.server.com:8020=java.naming.factory.initial#Dummy.Factory;java.naming.provider.url#tcp://broker.${2}:61616
227 </description>
228 </property>
229
230 <!-- HCatAccessorService -->
231 <property>
232 <name>oozie.service.HCatAccessorService.jms.use.canonical.hostname</name>
233 <value>false</value>
234 <description>The JMS messages published from a HCat server usually contains the canonical hostname of the HCat server
235 in standalone mode or the canonical name of the VIP in a case of multiple nodes in a HA setup. This setting is used
236 to translate the HCat server hostname or its aliases specified by the user in the HCat URIs of the coordinator dependencies
237 to its canonical name so that they can be exactly matched with the JMS dependency availability notifications.
238 </description>
239 </property>
240
241 <!-- TopicService -->
242
243 <property>
244 <name>oozie.service.JMSTopicService.topic.name</name>
245 <value>
246 default=${username}
247 </value>
248 <description>
249 Topic options are ${username} or ${jobId} or a fixed string which can be specified as default or for a
250 particular job type.
251 For e.g To have a fixed string topic for workflows, coordinators and bundles,
252 specify in the following comma-separated format: {jobtype1}={some_string1}, {jobtype2}={some_string2}
253 where job type can be WORKFLOW, COORDINATOR or BUNDLE.
254 e.g. Following defines topic for workflow job, workflow action, coordinator job, coordinator action,
255 bundle job and bundle action
256 WORKFLOW=workflow,
257 COORDINATOR=coordinator,
258 BUNDLE=bundle
259 For jobs with no defined topic, default topic will be ${username}
260 </description>
261 </property>
262
263 <!-- JMS Producer connection -->
264 <property>
265 <name>oozie.jms.producer.connection.properties</name>
266 <value>java.naming.factory.initial#org.apache.activemq.jndi.ActiveMQInitialContextFactory;java.naming.provider.url#tcp://localhost:61616;connectionFactoryNames#ConnectionFactory</value>
267 </property>
268
269 <!-- JMSAccessorService -->
270 <property>
271 <name>oozie.service.JMSAccessorService.connectioncontext.impl</name>
272 <value>
273 org.apache.oozie.jms.DefaultConnectionContext
274 </value>
275 <description>
276 Specifies the Connection Context implementation
277 </description>
278 </property>
279
280
281 <!-- ConfigurationService -->
282
283 <property>
284 <name>oozie.service.ConfigurationService.ignore.system.properties</name>
285 <value>
286 oozie.service.AuthorizationService.security.enabled
287 </value>
288 <description>
289 Specifies "oozie.*" properties to cannot be overriden via Java system properties.
290 Property names must be separted by commas.
291 </description>
292 </property>
293
294 <property>
295 <name>oozie.service.ConfigurationService.verify.available.properties</name>
296 <value>true</value>
297 <description>
298 Specifies whether the available configurations check is enabled or not.
299 </description>
300 </property>
301
302 <!-- SchedulerService -->
303
304 <property>
305 <name>oozie.service.SchedulerService.threads</name>
306 <value>10</value>
307 <description>
308 The number of threads to be used by the SchedulerService to run deamon tasks.
309 If maxed out, scheduled daemon tasks will be queued up and delayed until threads become available.
310 </description>
311 </property>
312
313 <!-- AuthorizationService -->
314
315 <property>
316 <name>oozie.service.AuthorizationService.authorization.enabled</name>
317 <value>false</value>
318 <description>
319 Specifies whether security (user name/admin role) is enabled or not.
320 If disabled any user can manage Oozie system and manage any job.
321 </description>
322 </property>
323
324 <property>
325 <name>oozie.service.AuthorizationService.default.group.as.acl</name>
326 <value>false</value>
327 <description>
328 Enables old behavior where the User's default group is the job's ACL.
329 </description>
330 </property>
331
332 <property>
333 <name>oozie.serviceAuthorizationService.admin.users</name>
334 <value></value>
335 <description>
336 Comma separated list of users with admin access for the Authorization service.
337 </description>
338 </property>
339
340 <property>
341 <name>oozie.service.AuthorizationService.system.info.authorized.users</name>
342 <value></value>
343 <description>
344 Comma separated list of users authorized for web service calls to get system configuration.
345 </description>
346 </property>
347
348 <!-- InstrumentationService -->
349
350 <property>
351 <name>oozie.service.InstrumentationService.logging.interval</name>
352 <value>60</value>
353 <description>
354 Interval, in seconds, at which instrumentation should be logged by the InstrumentationService.
355 If set to 0 it will not log instrumentation data.
356 </description>
357 </property>
358
359 <!-- PurgeService -->
360 <property>
361 <name>oozie.service.PurgeService.older.than</name>
362 <value>30</value>
363 <description>
364 Completed workflow jobs older than this value, in days, will be purged by the PurgeService.
365 </description>
366 </property>
367
368 <property>
369 <name>oozie.service.PurgeService.coord.older.than</name>
370 <value>7</value>
371 <description>
372 Completed coordinator jobs older than this value, in days, will be purged by the PurgeService.
373 </description>
374 </property>
375
376 <property>
377 <name>oozie.service.PurgeService.bundle.older.than</name>
378 <value>7</value>
379 <description>
380 Completed bundle jobs older than this value, in days, will be purged by the PurgeService.
381 </description>
382 </property>
383
384 <property>
385 <name>oozie.service.PurgeService.purge.old.coord.action</name>
386 <value>false</value>
387 <description>
388 Whether to purge completed workflows and their corresponding coordinator actions
389 of long running coordinator jobs if the completed workflow jobs are older than the value
390 specified in oozie.service.PurgeService.older.than.
391 </description>
392 </property>
393
394 <property>
395 <name>oozie.service.PurgeService.purge.limit</name>
396 <value>100</value>
397 <description>
398 Batch size of individual DB operations used for building the list of items
399 to be purged and performing actual purge.
400 </description>
401 </property>
402
403 <property>
404 <name>oozie.service.PurgeService.purge.interval</name>
405 <value>3600</value>
406 <description>
407 Interval at which the purge service will run, in seconds.
408 </description>
409 </property>
410
411 <property>
412 <name>oozie.service.PurgeService.enable.command.line</name>
413 <value>true</value>
414 <description>
415 Enable/Disable oozie admin purge command. By default, it is enabled.
416 </description>
417 </property>
418
419 <!-- RecoveryService -->
420
421 <property>
422 <name>oozie.service.RecoveryService.wf.actions.older.than</name>
423 <value>120</value>
424 <description>
425 Age of the actions which are eligible to be queued for recovery, in seconds.
426 </description>
427 </property>
428
429 <property>
430 <name>oozie.service.RecoveryService.wf.actions.created.time.interval</name>
431 <value>7</value>
432 <description>
433 Created time period of the actions which are eligible to be queued for recovery in days.
434 </description>
435 </property>
436
437 <property>
438 <name>oozie.service.RecoveryService.callable.batch.size</name>
439 <value>10</value>
440 <description>
441 This value determines the number of callable which will be batched together
442 to be executed by a single thread.
443 </description>
444 </property>
445
446 <property>
447 <name>oozie.service.RecoveryService.push.dependency.interval</name>
448 <value>200</value>
449 <description>
450 This value determines the delay for push missing dependency command queueing
451 in Recovery Service
452 </description>
453 </property>
454
455 <property>
456 <name>oozie.service.RecoveryService.interval</name>
457 <value>60</value>
458 <description>
459 Interval at which the RecoverService will run, in seconds.
460 </description>
461 </property>
462
463 <property>
464 <name>oozie.service.RecoveryService.coord.older.than</name>
465 <value>600</value>
466 <description>
467 Age of the Coordinator jobs or actions which are eligible to be queued for recovery, in seconds.
468 </description>
469 </property>
470
471 <property>
472 <name>oozie.service.RecoveryService.bundle.older.than</name>
473 <value>600</value>
474 <description>
475 Age of the Bundle jobs which are eligible to be queued for recovery, in seconds.
476 </description>
477 </property>
478
479 <!-- CallableQueueService -->
480
481 <property>
482 <name>oozie.service.CallableQueueService.queue.size</name>
483 <value>10000</value>
484 <description>Max callable queue size</description>
485 </property>
486
487 <property>
488 <name>oozie.service.CallableQueueService.threads</name>
489 <value>10</value>
490 <description>Number of threads used for executing callables</description>
491 </property>
492
493 <property>
494 <name>oozie.service.CallableQueueService.callable.concurrency</name>
495 <value>3</value>
496 <description>
497 Maximum concurrency for a given callable type.
498 Each command is a callable type (submit, start, run, signal, job, jobs, suspend,resume, etc).
499 Each action type is a callable type (Map-Reduce, Pig, SSH, FS, sub-workflow, etc).
500 All commands that use action executors (action-start, action-end, action-kill and action-check) use
501 the action type as the callable type.
502 </description>
503 </property>
504
505 <property>
506 <name>oozie.service.CallableQueueService.callable.next.eligible</name>
507 <value>true</value>
508 <description>
509 If true, when a callable in the queue has already reached max concurrency,
510 Oozie continuously find next one which has not yet reach max concurrency.
511 </description>
512 </property>
513
514 <property>
515 <name>oozie.service.CallableQueueService.InterruptMapMaxSize</name>
516 <value>500</value>
517 <description>
518 Maximum Size of the Interrupt Map, the interrupt element will not be inserted in the map if exceeded the size.
519 </description>
520 </property>
521
522 <property>
523 <name>oozie.service.CallableQueueService.InterruptTypes</name>
524 <value>kill,resume,suspend,bundle_kill,bundle_resume,bundle_suspend,coord_kill,coord_change,coord_resume,coord_suspend</value>
525 <description>
526 Getting the types of XCommands that are considered to be of Interrupt type
527 </description>
528 </property>
529
530 <!-- CoordMaterializeTriggerService -->
531
532 <property>
533 <name>oozie.service.CoordMaterializeTriggerService.lookup.interval
534 </name>
535 <value>300</value>
536 <description> Coordinator Job Lookup interval.(in seconds).
537 </description>
538 </property>
539
540 <!-- Enable this if you want different scheduling interval for CoordMaterializeTriggerService.
541 By default it will use lookup interval as scheduling interval
542 <property>
543 <name>oozie.service.CoordMaterializeTriggerService.scheduling.interval
544 </name>
545 <value>300</value>
546 <description> The frequency at which the CoordMaterializeTriggerService will run.</description>
547 </property>
548 -->
549
550 <property>
551 <name>oozie.service.CoordMaterializeTriggerService.materialization.window
552 </name>
553 <value>3600</value>
554 <description> Coordinator Job Lookup command materialized each
555 job for this next "window" duration
556 </description>
557 </property>
558
559 <property>
560 <name>oozie.service.CoordMaterializeTriggerService.callable.batch.size</name>
561 <value>10</value>
562 <description>
563 This value determines the number of callable which will be batched together
564 to be executed by a single thread.
565 </description>
566 </property>
567
568 <property>
569 <name>oozie.service.CoordMaterializeTriggerService.materialization.system.limit</name>
570 <value>50</value>
571 <description>
572 This value determines the number of coordinator jobs to be materialized at a given time.
573 </description>
574 </property>
575
576 <property>
577 <name>oozie.service.coord.normal.default.timeout
578 </name>
579 <value>120</value>
580 <description>Default timeout for a coordinator action input check (in minutes) for normal job.
581 -1 means infinite timeout</description>
582 </property>
583
584 <property>
585 <name>oozie.service.coord.default.max.timeout
586 </name>
587 <value>86400</value>
588 <description>Default maximum timeout for a coordinator action input check (in minutes). 86400= 60days
589 </description>
590 </property>
591
592 <property>
593 <name>oozie.service.coord.input.check.requeue.interval
594 </name>
595 <value>60000</value>
596 <description>Command re-queue interval for coordinator data input check (in millisecond).
597 </description>
598 </property>
599
600 <property>
601 <name>oozie.service.coord.input.check.requeue.interval.additional.delay</name>
602 <value>0</value>
603 <description>This value (in seconds) will be added into oozie.service.coord.input.check.requeue.interval and resulting value
604 will be the requeue interval for the actions which are waiting for a long time without any input.
605 </description>
606 </property>
607
608 <property>
609 <name>oozie.service.coord.push.check.requeue.interval
610 </name>
611 <value>600000</value>
612 <description>Command re-queue interval for push dependencies (in millisecond).
613 </description>
614 </property>
615
616 <property>
617 <name>oozie.service.coord.default.concurrency
618 </name>
619 <value>1</value>
620 <description>Default concurrency for a coordinator job to determine how many maximum action should
621 be executed at the same time. -1 means infinite concurrency.</description>
622 </property>
623
624 <property>
625 <name>oozie.service.coord.default.throttle
626 </name>
627 <value>12</value>
628 <description>Default throttle for a coordinator job to determine how many maximum action should
629 be in WAITING state at the same time.</description>
630 </property>
631
632 <property>
633 <name>oozie.service.coord.materialization.throttling.factor
634 </name>
635 <value>0.05</value>
636 <description>Determine how many maximum actions should be in WAITING state for a single job at any time. The value is calculated by
637 this factor X the total queue size.</description>
638 </property>
639
640 <property>
641 <name>oozie.service.coord.check.maximum.frequency</name>
642 <value>true</value>
643 <description>
644 When true, Oozie will reject any coordinators with a frequency faster than 5 minutes. It is not recommended to disable
645 this check or submit coordinators with frequencies faster than 5 minutes: doing so can cause unintended behavior and
646 additional system stress.
647 </description>
648 </property>
649
650 <!-- ELService -->
651 <!-- List of supported groups for ELService -->
652 <property>
653 <name>oozie.service.ELService.groups</name>
654 <value>job-submit,workflow,wf-sla-submit,coord-job-submit-freq,coord-job-submit-nofuncs,coord-job-submit-data,coord-job-submit-instances,coord-sla-submit,coord-action-create,coord-action-create-inst,coord-sla-create,coord-action-start,coord-job-wait-timeout,bundle-submit,coord-job-submit-initial-instance</value>
655 <description>List of groups for different ELServices</description>
656 </property>
657
658 <property>
659 <name>oozie.service.ELService.constants.job-submit</name>
660 <value>
661 </value>
662 <description>
663 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
664 </description>
665 </property>
666
667 <property>
668 <name>oozie.service.ELService.functions.job-submit</name>
669 <value>
670 </value>
671 <description>
672 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
673 </description>
674 </property>
675
676 <property>
677 <name>oozie.service.ELService.ext.constants.job-submit</name>
678 <value> </value>
679 <description>
680 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
681 This property is a convenience property to add extensions without having to include all the built in ones.
682 </description>
683 </property>
684
685 <property>
686 <name>oozie.service.ELService.ext.functions.job-submit</name>
687 <value> </value>
688 <description>
689 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
690 This property is a convenience property to add extensions without having to include all the built in ones.
691 </description>
692 </property>
693
694 <!-- Workflow specifics -->
695 <property>
696 <name>oozie.service.ELService.constants.workflow</name>
697 <value>
698 KB=org.apache.oozie.util.ELConstantsFunctions#KB,
699 MB=org.apache.oozie.util.ELConstantsFunctions#MB,
700 GB=org.apache.oozie.util.ELConstantsFunctions#GB,
701 TB=org.apache.oozie.util.ELConstantsFunctions#TB,
702 PB=org.apache.oozie.util.ELConstantsFunctions#PB,
703 RECORDS=org.apache.oozie.action.hadoop.HadoopELFunctions#RECORDS,
704 MAP_IN=org.apache.oozie.action.hadoop.HadoopELFunctions#MAP_IN,
705 MAP_OUT=org.apache.oozie.action.hadoop.HadoopELFunctions#MAP_OUT,
706 REDUCE_IN=org.apache.oozie.action.hadoop.HadoopELFunctions#REDUCE_IN,
707 REDUCE_OUT=org.apache.oozie.action.hadoop.HadoopELFunctions#REDUCE_OUT,
708 GROUPS=org.apache.oozie.action.hadoop.HadoopELFunctions#GROUPS
709 </value>
710 <description>
711 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
712 </description>
713 </property>
714
715 <property>
716 <name>oozie.service.ELService.ext.constants.workflow</name>
717 <value> </value>
718 <description>
719 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
720 This property is a convenience property to add extensions to the built in executors without having to
721 include all the built in ones.
722 </description>
723 </property>
724
725 <property>
726 <name>oozie.service.ELService.functions.workflow</name>
727 <value>
728 firstNotNull=org.apache.oozie.util.ELConstantsFunctions#firstNotNull,
729 concat=org.apache.oozie.util.ELConstantsFunctions#concat,
730 replaceAll=org.apache.oozie.util.ELConstantsFunctions#replaceAll,
731 appendAll=org.apache.oozie.util.ELConstantsFunctions#appendAll,
732 trim=org.apache.oozie.util.ELConstantsFunctions#trim,
733 timestamp=org.apache.oozie.util.ELConstantsFunctions#timestamp,
734 urlEncode=org.apache.oozie.util.ELConstantsFunctions#urlEncode,
735 toJsonStr=org.apache.oozie.util.ELConstantsFunctions#toJsonStr,
736 toPropertiesStr=org.apache.oozie.util.ELConstantsFunctions#toPropertiesStr,
737 toConfigurationStr=org.apache.oozie.util.ELConstantsFunctions#toConfigurationStr,
738 wf:id=org.apache.oozie.DagELFunctions#wf_id,
739 wf:name=org.apache.oozie.DagELFunctions#wf_name,
740 wf:appPath=org.apache.oozie.DagELFunctions#wf_appPath,
741 wf:conf=org.apache.oozie.DagELFunctions#wf_conf,
742 wf:user=org.apache.oozie.DagELFunctions#wf_user,
743 wf:group=org.apache.oozie.DagELFunctions#wf_group,
744 wf:callback=org.apache.oozie.DagELFunctions#wf_callback,
745 wf:transition=org.apache.oozie.DagELFunctions#wf_transition,
746 wf:lastErrorNode=org.apache.oozie.DagELFunctions#wf_lastErrorNode,
747 wf:errorCode=org.apache.oozie.DagELFunctions#wf_errorCode,
748 wf:errorMessage=org.apache.oozie.DagELFunctions#wf_errorMessage,
749 wf:run=org.apache.oozie.DagELFunctions#wf_run,
750 wf:actionData=org.apache.oozie.DagELFunctions#wf_actionData,
751 wf:actionExternalId=org.apache.oozie.DagELFunctions#wf_actionExternalId,
752 wf:actionTrackerUri=org.apache.oozie.DagELFunctions#wf_actionTrackerUri,
753 wf:actionExternalStatus=org.apache.oozie.DagELFunctions#wf_actionExternalStatus,
754 hadoop:counters=org.apache.oozie.action.hadoop.HadoopELFunctions#hadoop_counters,
755 hadoop:conf=org.apache.oozie.action.hadoop.HadoopELFunctions#hadoop_conf,
756 fs:exists=org.apache.oozie.action.hadoop.FsELFunctions#fs_exists,
757 fs:isDir=org.apache.oozie.action.hadoop.FsELFunctions#fs_isDir,
758 fs:dirSize=org.apache.oozie.action.hadoop.FsELFunctions#fs_dirSize,
759 fs:fileSize=org.apache.oozie.action.hadoop.FsELFunctions#fs_fileSize,
760 fs:blockSize=org.apache.oozie.action.hadoop.FsELFunctions#fs_blockSize,
761 hcat:exists=org.apache.oozie.coord.HCatELFunctions#hcat_exists
762 </value>
763 <description>
764 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
765 </description>
766 </property>
767
768 <property>
769 <name>oozie.service.WorkflowAppService.WorkflowDefinitionMaxLength</name>
770 <value>100000</value>
771 <description>
772 The maximum length of the workflow definition in bytes
773 An error will be reported if the length exceeds the given maximum
774 </description>
775 </property>
776
777 <property>
778 <name>oozie.service.ELService.ext.functions.workflow</name>
779 <value>
780 </value>
781 <description>
782 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
783 This property is a convenience property to add extensions to the built in executors without having to
784 include all the built in ones.
785 </description>
786 </property>
787
788 <!-- Resolve SLA information during Workflow job submission -->
789 <property>
790 <name>oozie.service.ELService.constants.wf-sla-submit</name>
791 <value>
792 MINUTES=org.apache.oozie.util.ELConstantsFunctions#SUBMIT_MINUTES,
793 HOURS=org.apache.oozie.util.ELConstantsFunctions#SUBMIT_HOURS,
794 DAYS=org.apache.oozie.util.ELConstantsFunctions#SUBMIT_DAYS
795 </value>
796 <description>
797 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
798 </description>
799 </property>
800
801 <property>
802 <name>oozie.service.ELService.ext.constants.wf-sla-submit</name>
803 <value> </value>
804 <description>
805 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
806 This property is a convenience property to add extensions to the built in executors without having to
807 include all the built in ones.
808 </description>
809 </property>
810
811 <property>
812 <name>oozie.service.ELService.functions.wf-sla-submit</name>
813 <value> </value>
814 <description>
815 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
816 </description>
817 </property>
818 <property>
819 <name>oozie.service.ELService.ext.functions.wf-sla-submit</name>
820 <value>
821 </value>
822 <description>
823 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
824 This property is a convenience property to add extensions to the built in executors without having to
825 include all the built in ones.
826 </description>
827 </property>
828
829 <!-- Coordinator specifics -->l
830 <!-- Phase 1 resolution during job submission -->
831 <!-- EL Evalautor setup to resolve mainly frequency tags -->
832 <property>
833 <name>oozie.service.ELService.constants.coord-job-submit-freq</name>
834 <value> </value>
835 <description>
836 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
837 </description>
838 </property>
839
840 <property>
841 <name>oozie.service.ELService.ext.constants.coord-job-submit-freq</name>
842 <value> </value>
843 <description>
844 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
845 This property is a convenience property to add extensions to the built in executors without having to
846 include all the built in ones.
847 </description>
848 </property>
849
850 <property>
851 <name>oozie.service.ELService.functions.coord-job-submit-freq</name>
852 <value>
853 coord:days=org.apache.oozie.coord.CoordELFunctions#ph1_coord_days,
854 coord:months=org.apache.oozie.coord.CoordELFunctions#ph1_coord_months,
855 coord:hours=org.apache.oozie.coord.CoordELFunctions#ph1_coord_hours,
856 coord:minutes=org.apache.oozie.coord.CoordELFunctions#ph1_coord_minutes,
857 coord:endOfDays=org.apache.oozie.coord.CoordELFunctions#ph1_coord_endOfDays,
858 coord:endOfMonths=org.apache.oozie.coord.CoordELFunctions#ph1_coord_endOfMonths,
859 coord:endOfWeeks=org.apache.oozie.coord.CoordELFunctions#ph1_coord_endOfWeeks,
860 coord:conf=org.apache.oozie.coord.CoordELFunctions#coord_conf,
861 coord:user=org.apache.oozie.coord.CoordELFunctions#coord_user,
862 hadoop:conf=org.apache.oozie.action.hadoop.HadoopELFunctions#hadoop_conf
863 </value>
864 <description>
865 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
866 </description>
867 </property>
868
869 <property>
870 <name>oozie.service.ELService.functions.coord-job-submit-initial-instance</name>
871 <value>
872 ${oozie.service.ELService.functions.coord-job-submit-nofuncs},
873 coord:dateOffset=org.apache.oozie.coord.CoordELFunctions#ph2_coord_dateOffset,
874 coord:dateTzOffset=org.apache.oozie.coord.CoordELFunctions#ph2_coord_dateTzOffset
875 </value>
876 <description>
877 EL functions for coord job submit initial instance, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
878 </description>
879 </property>
880
881 <property>
882 <name>oozie.service.ELService.ext.functions.coord-job-submit-freq</name>
883 <value>
884 </value>
885 <description>
886 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
887 This property is a convenience property to add extensions to the built in executors without having to
888 include all the built in ones.
889 </description>
890 </property>
891
892 <property>
893 <name>oozie.service.ELService.constants.coord-job-wait-timeout</name>
894 <value> </value>
895 <description>
896 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
897 </description>
898 </property>
899
900 <property>
901 <name>oozie.service.ELService.ext.constants.coord-job-wait-timeout</name>
902 <value> </value>
903 <description>
904 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
905 This property is a convenience property to add extensions without having to include all the built in ones.
906 </description>
907 </property>
908
909 <property>
910 <name>oozie.service.ELService.functions.coord-job-wait-timeout</name>
911 <value>
912 coord:days=org.apache.oozie.coord.CoordELFunctions#ph1_coord_days,
913 coord:months=org.apache.oozie.coord.CoordELFunctions#ph1_coord_months,
914 coord:hours=org.apache.oozie.coord.CoordELFunctions#ph1_coord_hours,
915 coord:minutes=org.apache.oozie.coord.CoordELFunctions#ph1_coord_minutes,
916 hadoop:conf=org.apache.oozie.action.hadoop.HadoopELFunctions#hadoop_conf
917 </value>
918 <description>
919 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
920 </description>
921 </property>
922
923 <property>
924 <name>oozie.service.ELService.ext.functions.coord-job-wait-timeout</name>
925 <value> </value>
926 <description>
927 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
928 This property is a convenience property to add extensions without having to include all the built in ones.
929 </description>
930 </property>
931
932 <!-- EL Evalautor setup to resolve mainly all constants/variables - no EL functions is resolved -->
933 <property>
934 <name>oozie.service.ELService.constants.coord-job-submit-nofuncs</name>
935 <value>
936 MINUTE=org.apache.oozie.coord.CoordELConstants#SUBMIT_MINUTE,
937 HOUR=org.apache.oozie.coord.CoordELConstants#SUBMIT_HOUR,
938 DAY=org.apache.oozie.coord.CoordELConstants#SUBMIT_DAY,
939 MONTH=org.apache.oozie.coord.CoordELConstants#SUBMIT_MONTH,
940 YEAR=org.apache.oozie.coord.CoordELConstants#SUBMIT_YEAR
941 </value>
942 <description>
943 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
944 </description>
945 </property>
946
947 <property>
948 <name>oozie.service.ELService.ext.constants.coord-job-submit-nofuncs</name>
949 <value> </value>
950 <description>
951 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
952 This property is a convenience property to add extensions to the built in executors without having to
953 include all the built in ones.
954 </description>
955 </property>
956
957 <property>
958 <name>oozie.service.ELService.functions.coord-job-submit-nofuncs</name>
959 <value>
960 coord:conf=org.apache.oozie.coord.CoordELFunctions#coord_conf,
961 coord:user=org.apache.oozie.coord.CoordELFunctions#coord_user,
962 hadoop:conf=org.apache.oozie.action.hadoop.HadoopELFunctions#hadoop_conf
963 </value>
964 <description>
965 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
966 </description>
967 </property>
968
969 <property>
970 <name>oozie.service.ELService.ext.functions.coord-job-submit-nofuncs</name>
971 <value> </value>
972 <description>
973 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
974 This property is a convenience property to add extensions to the built in executors without having to
975 include all the built in ones.
976 </description>
977 </property>
978
979 <!-- EL Evalautor setup to **check** whether instances/start-instance/end-instances are valid
980 no EL functions will be resolved -->
981 <property>
982 <name>oozie.service.ELService.constants.coord-job-submit-instances</name>
983 <value> </value>
984 <description>
985 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
986 </description>
987 </property>
988
989 <property>
990 <name>oozie.service.ELService.ext.constants.coord-job-submit-instances</name>
991 <value> </value>
992 <description>
993 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
994 This property is a convenience property to add extensions to the built in executors without having to
995 include all the built in ones.
996 </description>
997 </property>
998
999 <property>
1000 <name>oozie.service.ELService.functions.coord-job-submit-instances</name>
1001 <value>
1002 coord:hoursInDay=org.apache.oozie.coord.CoordELFunctions#ph1_coord_hoursInDay_echo,
1003 coord:daysInMonth=org.apache.oozie.coord.CoordELFunctions#ph1_coord_daysInMonth_echo,
1004 coord:tzOffset=org.apache.oozie.coord.CoordELFunctions#ph1_coord_tzOffset_echo,
1005 coord:current=org.apache.oozie.coord.CoordELFunctions#ph1_coord_current_echo,
1006 coord:currentRange=org.apache.oozie.coord.CoordELFunctions#ph1_coord_currentRange_echo,
1007 coord:offset=org.apache.oozie.coord.CoordELFunctions#ph1_coord_offset_echo,
1008 coord:latest=org.apache.oozie.coord.CoordELFunctions#ph1_coord_latest_echo,
1009 coord:latestRange=org.apache.oozie.coord.CoordELFunctions#ph1_coord_latestRange_echo,
1010 coord:future=org.apache.oozie.coord.CoordELFunctions#ph1_coord_future_echo,
1011 coord:futureRange=org.apache.oozie.coord.CoordELFunctions#ph1_coord_futureRange_echo,
1012 coord:formatTime=org.apache.oozie.coord.CoordELFunctions#ph1_coord_formatTime_echo,
1013 coord:epochTime=org.apache.oozie.coord.CoordELFunctions#ph1_coord_epochTime_echo,
1014 coord:conf=org.apache.oozie.coord.CoordELFunctions#coord_conf,
1015 coord:user=org.apache.oozie.coord.CoordELFunctions#coord_user,
1016 coord:absolute=org.apache.oozie.coord.CoordELFunctions#ph1_coord_absolute_echo,
1017 coord:endOfMonths=org.apache.oozie.coord.CoordELFunctions#ph1_coord_endOfMonths_echo,
1018 coord:endOfWeeks=org.apache.oozie.coord.CoordELFunctions#ph1_coord_endOfWeeks_echo,
1019 coord:endOfDays=org.apache.oozie.coord.CoordELFunctions#ph1_coord_endOfDays_echo,
1020 hadoop:conf=org.apache.oozie.action.hadoop.HadoopELFunctions#hadoop_conf,
1021 coord:dateOffset=org.apache.oozie.coord.CoordELFunctions#ph1_coord_dateOffset_echo,
1022 coord:dateTzOffset=org.apache.oozie.coord.CoordELFunctions#ph1_coord_dateTzOffset_echo
1023 </value>
1024 <description>
1025 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
1026 </description>
1027 </property>
1028
1029 <property>
1030 <name>oozie.service.ELService.ext.functions.coord-job-submit-instances</name>
1031 <value>
1032 </value>
1033 <description>
1034 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
1035 This property is a convenience property to add extensions to the built in executors without having to
1036 include all the built in ones.
1037 </description>
1038 </property>
1039
1040 <!-- EL Evalautor setup to **check** whether dataIn and dataOut are valid
1041 no EL functions will be resolved -->
1042
1043 <property>
1044 <name>oozie.service.ELService.constants.coord-job-submit-data</name>
1045 <value> </value>
1046 <description>
1047 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
1048 </description>
1049 </property>
1050
1051 <property>
1052 <name>oozie.service.ELService.ext.constants.coord-job-submit-data</name>
1053 <value> </value>
1054 <description>
1055 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
1056 This property is a convenience property to add extensions to the built in executors without having to
1057 include all the built in ones.
1058 </description>
1059 </property>
1060
1061 <property>
1062 <name>oozie.service.ELService.functions.coord-job-submit-data</name>
1063 <value>
1064 coord:dataIn=org.apache.oozie.coord.CoordELFunctions#ph1_coord_dataIn_echo,
1065 coord:dataOut=org.apache.oozie.coord.CoordELFunctions#ph1_coord_dataOut_echo,
1066 coord:nominalTime=org.apache.oozie.coord.CoordELFunctions#ph1_coord_nominalTime_echo_wrap,
1067 coord:actualTime=org.apache.oozie.coord.CoordELFunctions#ph1_coord_actualTime_echo_wrap,
1068 coord:dateOffset=org.apache.oozie.coord.CoordELFunctions#ph1_coord_dateOffset_echo,
1069 coord:dateTzOffset=org.apache.oozie.coord.CoordELFunctions#ph1_coord_dateTzOffset_echo,
1070 coord:formatTime=org.apache.oozie.coord.CoordELFunctions#ph1_coord_formatTime_echo,
1071 coord:epochTime=org.apache.oozie.coord.CoordELFunctions#ph1_coord_epochTime_echo,
1072 coord:actionId=org.apache.oozie.coord.CoordELFunctions#ph1_coord_actionId_echo,
1073 coord:name=org.apache.oozie.coord.CoordELFunctions#ph1_coord_name_echo,
1074 coord:conf=org.apache.oozie.coord.CoordELFunctions#coord_conf,
1075 coord:user=org.apache.oozie.coord.CoordELFunctions#coord_user,
1076 coord:databaseIn=org.apache.oozie.coord.HCatELFunctions#ph1_coord_databaseIn_echo,
1077 coord:databaseOut=org.apache.oozie.coord.HCatELFunctions#ph1_coord_databaseOut_echo,
1078 coord:tableIn=org.apache.oozie.coord.HCatELFunctions#ph1_coord_tableIn_echo,
1079 coord:tableOut=org.apache.oozie.coord.HCatELFunctions#ph1_coord_tableOut_echo,
1080 coord:dataInPartitionFilter=org.apache.oozie.coord.HCatELFunctions#ph1_coord_dataInPartitionFilter_echo,
1081 coord:dataInPartitionMin=org.apache.oozie.coord.HCatELFunctions#ph1_coord_dataInPartitionMin_echo,
1082 coord:dataInPartitionMax=org.apache.oozie.coord.HCatELFunctions#ph1_coord_dataInPartitionMax_echo,
1083 coord:dataInPartitions=org.apache.oozie.coord.HCatELFunctions#ph1_coord_dataInPartitions_echo,
1084 coord:dataOutPartitions=org.apache.oozie.coord.HCatELFunctions#ph1_coord_dataOutPartitions_echo,
1085 coord:dataOutPartitionValue=org.apache.oozie.coord.HCatELFunctions#ph1_coord_dataOutPartitionValue_echo,
1086 hadoop:conf=org.apache.oozie.action.hadoop.HadoopELFunctions#hadoop_conf
1087 </value>
1088 <description>
1089 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
1090 </description>
1091 </property>
1092
1093 <property>
1094 <name>oozie.service.ELService.ext.functions.coord-job-submit-data</name>
1095 <value>
1096 </value>
1097 <description>
1098 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
1099 This property is a convenience property to add extensions to the built in executors without having to
1100 include all the built in ones.
1101 </description>
1102 </property>
1103
1104 <!-- Resolve SLA information during Coordinator job submission -->
1105 <property>
1106 <name>oozie.service.ELService.constants.coord-sla-submit</name>
1107 <value>
1108 MINUTES=org.apache.oozie.coord.CoordELConstants#SUBMIT_MINUTES,
1109 HOURS=org.apache.oozie.coord.CoordELConstants#SUBMIT_HOURS,
1110 DAYS=org.apache.oozie.coord.CoordELConstants#SUBMIT_DAYS
1111 </value>
1112 <description>
1113 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
1114 </description>
1115 </property>
1116
1117 <property>
1118 <name>oozie.service.ELService.ext.constants.coord-sla-submit</name>
1119 <value> </value>
1120 <description>
1121 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
1122 This property is a convenience property to add extensions to the built in executors without having to
1123 include all the built in ones.
1124 </description>
1125 </property>
1126
1127 <property>
1128 <name>oozie.service.ELService.functions.bundle-submit</name>
1129 <value>bundle:conf=org.apache.oozie.bundle.BundleELFunctions#bundle_conf</value>
1130 </property>
1131
1132 <property>
1133 <name>oozie.service.ELService.functions.coord-sla-submit</name>
1134 <value>
1135 coord:dataOut=org.apache.oozie.coord.CoordELFunctions#ph1_coord_dataOut_echo,
1136 coord:nominalTime=org.apache.oozie.coord.CoordELFunctions#ph1_coord_nominalTime_echo_fixed,
1137 coord:actualTime=org.apache.oozie.coord.CoordELFunctions#ph1_coord_actualTime_echo_wrap,
1138 coord:dateOffset=org.apache.oozie.coord.CoordELFunctions#ph1_coord_dateOffset_echo,
1139 coord:dateTzOffset=org.apache.oozie.coord.CoordELFunctions#ph1_coord_dateTzOffset_echo,
1140 coord:formatTime=org.apache.oozie.coord.CoordELFunctions#ph1_coord_formatTime_echo,
1141 coord:epochTime=org.apache.oozie.coord.CoordELFunctions#ph1_coord_epochTime_echo,
1142 coord:actionId=org.apache.oozie.coord.CoordELFunctions#ph1_coord_actionId_echo,
1143 coord:name=org.apache.oozie.coord.CoordELFunctions#ph1_coord_name_echo,
1144 coord:conf=org.apache.oozie.coord.CoordELFunctions#coord_conf,
1145 coord:user=org.apache.oozie.coord.CoordELFunctions#coord_user,
1146 coord:databaseOut=org.apache.oozie.coord.HCatELFunctions#ph1_coord_databaseOut_echo,
1147 coord:tableOut=org.apache.oozie.coord.HCatELFunctions#ph1_coord_tableOut_echo,
1148 coord:dataOutPartitions=org.apache.oozie.coord.HCatELFunctions#ph1_coord_dataOutPartitions_echo,
1149 coord:dataOutPartitionValue=org.apache.oozie.coord.HCatELFunctions#ph1_coord_dataOutPartitionValue_echo,
1150 hadoop:conf=org.apache.oozie.action.hadoop.HadoopELFunctions#hadoop_conf
1151 </value>
1152 <description>
1153 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
1154 </description>
1155 </property>
1156 <property>
1157 <name>oozie.service.ELService.ext.functions.coord-sla-submit</name>
1158 <value>
1159 </value>
1160 <description>
1161 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
1162 This property is a convenience property to add extensions to the built in executors without having to
1163 include all the built in ones.
1164 </description>
1165 </property>
1166
1167 <!-- Action creation for coordinator -->
1168 <property>
1169 <name>oozie.service.ELService.constants.coord-action-create</name>
1170 <value>
1171 </value>
1172 <description>
1173 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
1174 </description>
1175 </property>
1176
1177 <property>
1178 <name>oozie.service.ELService.ext.constants.coord-action-create</name>
1179 <value> </value>
1180 <description>
1181 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
1182 This property is a convenience property to add extensions to the built in executors without having to
1183 include all the built in ones.
1184 </description>
1185 </property>
1186
1187 <property>
1188 <name>oozie.service.ELService.functions.coord-action-create</name>
1189 <value>
1190 coord:hoursInDay=org.apache.oozie.coord.CoordELFunctions#ph2_coord_hoursInDay,
1191 coord:daysInMonth=org.apache.oozie.coord.CoordELFunctions#ph2_coord_daysInMonth,
1192 coord:tzOffset=org.apache.oozie.coord.CoordELFunctions#ph2_coord_tzOffset,
1193 coord:current=org.apache.oozie.coord.CoordELFunctions#ph2_coord_current,
1194 coord:currentRange=org.apache.oozie.coord.CoordELFunctions#ph2_coord_currentRange,
1195 coord:offset=org.apache.oozie.coord.CoordELFunctions#ph2_coord_offset,
1196 coord:latest=org.apache.oozie.coord.CoordELFunctions#ph2_coord_latest_echo,
1197 coord:latestRange=org.apache.oozie.coord.CoordELFunctions#ph2_coord_latestRange_echo,
1198 coord:future=org.apache.oozie.coord.CoordELFunctions#ph2_coord_future_echo,
1199 coord:futureRange=org.apache.oozie.coord.CoordELFunctions#ph2_coord_futureRange_echo,
1200 coord:actionId=org.apache.oozie.coord.CoordELFunctions#ph2_coord_actionId,
1201 coord:name=org.apache.oozie.coord.CoordELFunctions#ph2_coord_name,
1202 coord:formatTime=org.apache.oozie.coord.CoordELFunctions#ph2_coord_formatTime,
1203 coord:epochTime=org.apache.oozie.coord.CoordELFunctions#ph2_coord_epochTime,
1204 coord:conf=org.apache.oozie.coord.CoordELFunctions#coord_conf,
1205 coord:user=org.apache.oozie.coord.CoordELFunctions#coord_user,
1206 coord:absolute=org.apache.oozie.coord.CoordELFunctions#ph2_coord_absolute_echo,
1207 coord:endOfMonths=org.apache.oozie.coord.CoordELFunctions#ph2_coord_endOfMonths_echo,
1208 coord:endOfWeeks=org.apache.oozie.coord.CoordELFunctions#ph2_coord_endOfWeeks_echo,
1209 coord:endOfDays=org.apache.oozie.coord.CoordELFunctions#ph2_coord_endOfDays_echo,
1210 coord:absoluteRange=org.apache.oozie.coord.CoordELFunctions#ph2_coord_absolute_range,
1211 hadoop:conf=org.apache.oozie.action.hadoop.HadoopELFunctions#hadoop_conf
1212 </value>
1213 <description>
1214 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
1215 </description>
1216 </property>
1217
1218 <property>
1219 <name>oozie.service.ELService.ext.functions.coord-action-create</name>
1220 <value>
1221 </value>
1222 <description>
1223 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
1224 This property is a convenience property to add extensions to the built in executors without having to
1225 include all the built in ones.
1226 </description>
1227 </property>
1228
1229
1230 <!-- Action creation for coordinator used to only evaluate instance number like ${current (daysInMonth())}. current will be echo-ed -->
1231 <property>
1232 <name>oozie.service.ELService.constants.coord-action-create-inst</name>
1233 <value>
1234 </value>
1235 <description>
1236 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
1237 </description>
1238 </property>
1239
1240 <property>
1241 <name>oozie.service.ELService.ext.constants.coord-action-create-inst</name>
1242 <value> </value>
1243 <description>
1244 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
1245 This property is a convenience property to add extensions to the built in executors without having to
1246 include all the built in ones.
1247 </description>
1248 </property>
1249
1250 <property>
1251 <name>oozie.service.ELService.functions.coord-action-create-inst</name>
1252 <value>
1253 coord:hoursInDay=org.apache.oozie.coord.CoordELFunctions#ph2_coord_hoursInDay,
1254 coord:daysInMonth=org.apache.oozie.coord.CoordELFunctions#ph2_coord_daysInMonth,
1255 coord:tzOffset=org.apache.oozie.coord.CoordELFunctions#ph2_coord_tzOffset,
1256 coord:current=org.apache.oozie.coord.CoordELFunctions#ph2_coord_current_echo,
1257 coord:currentRange=org.apache.oozie.coord.CoordELFunctions#ph2_coord_currentRange_echo,
1258 coord:offset=org.apache.oozie.coord.CoordELFunctions#ph2_coord_offset_echo,
1259 coord:latest=org.apache.oozie.coord.CoordELFunctions#ph2_coord_latest_echo,
1260 coord:latestRange=org.apache.oozie.coord.CoordELFunctions#ph2_coord_latestRange_echo,
1261 coord:future=org.apache.oozie.coord.CoordELFunctions#ph2_coord_future_echo,
1262 coord:futureRange=org.apache.oozie.coord.CoordELFunctions#ph2_coord_futureRange_echo,
1263 coord:formatTime=org.apache.oozie.coord.CoordELFunctions#ph2_coord_formatTime,
1264 coord:epochTime=org.apache.oozie.coord.CoordELFunctions#ph2_coord_epochTime,
1265 coord:conf=org.apache.oozie.coord.CoordELFunctions#coord_conf,
1266 coord:user=org.apache.oozie.coord.CoordELFunctions#coord_user,
1267 coord:absolute=org.apache.oozie.coord.CoordELFunctions#ph2_coord_absolute_echo,
1268 coord:absoluteRange=org.apache.oozie.coord.CoordELFunctions#ph2_coord_absolute_range,
1269 coord:endOfMonths=org.apache.oozie.coord.CoordELFunctions#ph2_coord_endOfMonths_echo,
1270 coord:endOfWeeks=org.apache.oozie.coord.CoordELFunctions#ph2_coord_endOfWeeks_echo,
1271 coord:endOfDays=org.apache.oozie.coord.CoordELFunctions#ph2_coord_endOfDays_echo,
1272 hadoop:conf=org.apache.oozie.action.hadoop.HadoopELFunctions#hadoop_conf,
1273 coord:dateOffset=org.apache.oozie.coord.CoordELFunctions#ph2_coord_dateOffset,
1274 coord:dateTzOffset=org.apache.oozie.coord.CoordELFunctions#ph2_coord_dateTzOffset
1275 </value>
1276 <description>
1277 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
1278 </description>
1279 </property>
1280
1281 <property>
1282 <name>oozie.service.ELService.ext.functions.coord-action-create-inst</name>
1283 <value>
1284 </value>
1285 <description>
1286 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
1287 This property is a convenience property to add extensions to the built in executors without having to
1288 include all the built in ones.
1289 </description>
1290 </property>
1291
1292 <!-- Resolve SLA information during Action creation/materialization -->
1293 <property>
1294 <name>oozie.service.ELService.constants.coord-sla-create</name>
1295 <value> </value>
1296 <description>
1297 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
1298 </description>
1299 </property>
1300
1301 <property>
1302 <name>oozie.service.ELService.ext.constants.coord-sla-create</name>
1303 <value>
1304 MINUTES=org.apache.oozie.coord.CoordELConstants#SUBMIT_MINUTES,
1305 HOURS=org.apache.oozie.coord.CoordELConstants#SUBMIT_HOURS,
1306 DAYS=org.apache.oozie.coord.CoordELConstants#SUBMIT_DAYS</value>
1307 <description>
1308 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
1309 This property is a convenience property to add extensions to the built in executors without having to
1310 include all the built in ones.
1311 </description>
1312 </property>
1313
1314 <property>
1315 <name>oozie.service.ELService.functions.coord-sla-create</name>
1316 <value>
1317 coord:dataOut=org.apache.oozie.coord.CoordELFunctions#ph3_coord_dataOut,
1318 coord:nominalTime=org.apache.oozie.coord.CoordELFunctions#ph2_coord_nominalTime,
1319 coord:actualTime=org.apache.oozie.coord.CoordELFunctions#ph2_coord_actualTime,
1320 coord:dateOffset=org.apache.oozie.coord.CoordELFunctions#ph2_coord_dateOffset,
1321 coord:dateTzOffset=org.apache.oozie.coord.CoordELFunctions#ph2_coord_dateTzOffset,
1322 coord:formatTime=org.apache.oozie.coord.CoordELFunctions#ph2_coord_formatTime,
1323 coord:epochTime=org.apache.oozie.coord.CoordELFunctions#ph2_coord_epochTime,
1324 coord:actionId=org.apache.oozie.coord.CoordELFunctions#ph2_coord_actionId,
1325 coord:name=org.apache.oozie.coord.CoordELFunctions#ph2_coord_name,
1326 coord:conf=org.apache.oozie.coord.CoordELFunctions#coord_conf,
1327 coord:user=org.apache.oozie.coord.CoordELFunctions#coord_user,
1328 coord:databaseOut=org.apache.oozie.coord.HCatELFunctions#ph3_coord_databaseOut,
1329 coord:tableOut=org.apache.oozie.coord.HCatELFunctions#ph3_coord_tableOut,
1330 coord:dataOutPartitions=org.apache.oozie.coord.HCatELFunctions#ph3_coord_dataOutPartitions,
1331 coord:dataOutPartitionValue=org.apache.oozie.coord.HCatELFunctions#ph3_coord_dataOutPartitionValue,
1332 hadoop:conf=org.apache.oozie.action.hadoop.HadoopELFunctions#hadoop_conf
1333 </value>
1334 <description>
1335 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
1336 </description>
1337 </property>
1338 <property>
1339 <name>oozie.service.ELService.ext.functions.coord-sla-create</name>
1340 <value>
1341 </value>
1342 <description>
1343 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
1344 This property is a convenience property to add extensions to the built in executors without having to
1345 include all the built in ones.
1346 </description>
1347 </property>
1348
1349 <!-- Action start for coordinator -->
1350 <property>
1351 <name>oozie.service.ELService.constants.coord-action-start</name>
1352 <value>
1353 </value>
1354 <description>
1355 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
1356 </description>
1357 </property>
1358
1359 <property>
1360 <name>oozie.service.ELService.ext.constants.coord-action-start</name>
1361 <value> </value>
1362 <description>
1363 EL constant declarations, separated by commas, format is [PREFIX:]NAME=CLASS#CONSTANT.
1364 This property is a convenience property to add extensions to the built in executors without having to
1365 include all the built in ones.
1366 </description>
1367 </property>
1368
1369 <property>
1370 <name>oozie.service.ELService.functions.coord-action-start</name>
1371 <value>
1372 coord:hoursInDay=org.apache.oozie.coord.CoordELFunctions#ph3_coord_hoursInDay,
1373 coord:daysInMonth=org.apache.oozie.coord.CoordELFunctions#ph3_coord_daysInMonth,
1374 coord:tzOffset=org.apache.oozie.coord.CoordELFunctions#ph3_coord_tzOffset,
1375 coord:latest=org.apache.oozie.coord.CoordELFunctions#ph3_coord_latest,
1376 coord:latestRange=org.apache.oozie.coord.CoordELFunctions#ph3_coord_latestRange,
1377 coord:future=org.apache.oozie.coord.CoordELFunctions#ph3_coord_future,
1378 coord:futureRange=org.apache.oozie.coord.CoordELFunctions#ph3_coord_futureRange,
1379 coord:dataIn=org.apache.oozie.coord.CoordELFunctions#ph3_coord_dataIn,
1380 coord:dataOut=org.apache.oozie.coord.CoordELFunctions#ph3_coord_dataOut,
1381 coord:nominalTime=org.apache.oozie.coord.CoordELFunctions#ph3_coord_nominalTime,
1382 coord:actualTime=org.apache.oozie.coord.CoordELFunctions#ph3_coord_actualTime,
1383 coord:dateOffset=org.apache.oozie.coord.CoordELFunctions#ph3_coord_dateOffset,
1384 coord:dateTzOffset=org.apache.oozie.coord.CoordELFunctions#ph3_coord_dateTzOffset,
1385 coord:formatTime=org.apache.oozie.coord.CoordELFunctions#ph3_coord_formatTime,
1386 coord:epochTime=org.apache.oozie.coord.CoordELFunctions#ph3_coord_epochTime,
1387 coord:actionId=org.apache.oozie.coord.CoordELFunctions#ph3_coord_actionId,
1388 coord:name=org.apache.oozie.coord.CoordELFunctions#ph3_coord_name,
1389 coord:conf=org.apache.oozie.coord.CoordELFunctions#coord_conf,
1390 coord:user=org.apache.oozie.coord.CoordELFunctions#coord_user,
1391 coord:databaseIn=org.apache.oozie.coord.HCatELFunctions#ph3_coord_databaseIn,
1392 coord:databaseOut=org.apache.oozie.coord.HCatELFunctions#ph3_coord_databaseOut,
1393 coord:tableIn=org.apache.oozie.coord.HCatELFunctions#ph3_coord_tableIn,
1394 coord:tableOut=org.apache.oozie.coord.HCatELFunctions#ph3_coord_tableOut,
1395 coord:dataInPartitionFilter=org.apache.oozie.coord.HCatELFunctions#ph3_coord_dataInPartitionFilter,
1396 coord:dataInPartitionMin=org.apache.oozie.coord.HCatELFunctions#ph3_coord_dataInPartitionMin,
1397 coord:dataInPartitionMax=org.apache.oozie.coord.HCatELFunctions#ph3_coord_dataInPartitionMax,
1398 coord:dataInPartitions=org.apache.oozie.coord.HCatELFunctions#ph3_coord_dataInPartitions,
1399 coord:dataOutPartitions=org.apache.oozie.coord.HCatELFunctions#ph3_coord_dataOutPartitions,
1400 coord:dataOutPartitionValue=org.apache.oozie.coord.HCatELFunctions#ph3_coord_dataOutPartitionValue,
1401 hadoop:conf=org.apache.oozie.action.hadoop.HadoopELFunctions#hadoop_conf
1402 </value>
1403 <description>
1404 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
1405 </description>
1406 </property>
1407
1408 <property>
1409 <name>oozie.service.ELService.ext.functions.coord-action-start</name>
1410 <value>
1411 </value>
1412 <description>
1413 EL functions declarations, separated by commas, format is [PREFIX:]NAME=CLASS#METHOD.
1414 This property is a convenience property to add extensions to the built in executors without having to
1415 include all the built in ones.
1416 </description>
1417 </property>
1418
1419 <property>
1420 <name>oozie.service.ELService.latest-el.use-current-time</name>
1421 <value>false</value>
1422 <description>
1423 Determine whether to use the current time to determine the latest dependency or the action creation time.
1424 This is for backward compatibility with older oozie behaviour.
1425 </description>
1426 </property>
1427
1428 <!-- UUIDService -->
1429
1430 <property>
1431 <name>oozie.service.UUIDService.generator</name>
1432 <value>counter</value>
1433 <description>
1434 random : generated UUIDs will be random strings.
1435 counter: generated UUIDs generated will be a counter postfixed with the system startup time.
1436 </description>
1437 </property>
1438
1439 <!-- DBLiteWorkflowStoreService -->
1440
1441 <property>
1442 <name>oozie.service.DBLiteWorkflowStoreService.status.metrics.collection.interval</name>
1443 <value>5</value>
1444 <description> Workflow Status metrics collection interval in minutes.</description>
1445 </property>
1446
1447 <property>
1448 <name>oozie.service.DBLiteWorkflowStoreService.status.metrics.window</name>
1449 <value>3600</value>
1450 <description>
1451 Workflow Status metrics collection window in seconds. Workflow status will be instrumented for the window.
1452 </description>
1453 </property>
1454
1455 <!-- DB Schema Info, used by DBLiteWorkflowStoreService -->
1456
1457 <property>
1458 <name>oozie.db.schema.name</name>
1459 <value>oozie</value>
1460 <description>
1461 Oozie DataBase Name
1462 </description>
1463 </property>
1464
1465 <!-- Database import CLI: batch size -->
1466
1467 <property>
1468 <name>oozie.db.import.batch.size</name>
1469 <value>1000</value>
1470 <description>
1471 How many entities are imported in a single transaction by the Oozie DB import CLI tool to avoid OutOfMemoryErrors.
1472 </description>
1473 </property>
1474
1475 <!-- StoreService -->
1476
1477 <property>
1478 <name>oozie.service.JPAService.create.db.schema</name>
1479 <value>false</value>
1480 <description>
1481 Creates Oozie DB.
1482
1483 If set to true, it creates the DB schema if it does not exist. If the DB schema exists is a NOP.
1484 If set to false, it does not create the DB schema. If the DB schema does not exist it fails start up.
1485 </description>
1486 </property>
1487
1488 <property>
1489 <name>oozie.service.JPAService.validate.db.connection</name>
1490 <value>true</value>
1491 <description>
1492 Validates DB connections from the DB connection pool.
1493 If the 'oozie.service.JPAService.create.db.schema' property is set to true, this property is ignored.
1494 </description>
1495 </property>
1496
1497 <property>
1498 <name>oozie.service.JPAService.validate.db.connection.eviction.interval</name>
1499 <value>300000</value>
1500 <description>
1501 Validates DB connections from the DB connection pool.
1502 When validate db connection 'TestWhileIdle' is true, the number of milliseconds to sleep
1503 between runs of the idle object evictor thread.
1504 </description>
1505 </property>
1506
1507 <property>
1508 <name>oozie.service.JPAService.validate.db.connection.eviction.num</name>
1509 <value>10</value>
1510 <description>
1511 Validates DB connections from the DB connection pool.
1512 When validate db connection 'TestWhileIdle' is true, the number of objects to examine during
1513 each run of the idle object evictor thread.
1514 </description>
1515 </property>
1516
1517
1518 <property>
1519 <name>oozie.service.JPAService.connection.data.source</name>
1520 <value>org.apache.oozie.util.db.BasicDataSourceWrapper</value>
1521 <description>
1522 DataSource to be used for connection pooling. If you want the property
1523 openJpa.connectionProperties="DriverClassName=..." to have a real effect, set this to
1524 org.apache.oozie.util.db.BasicDataSourceWrapper.
1525 A DBCP bug (https://issues.apache.org/jira/browse/DBCP-333) prevents otherwise the JDBC driver
1526 setting to have a real effect while using custom class loader.
1527 </description>
1528 </property>
1529
1530 <property>
1531 <name>oozie.service.JPAService.connection.properties</name>
1532 <value> </value>
1533 <description>
1534 DataSource connection properties.
1535 </description>
1536 </property>
1537
1538 <property>
1539 <name>oozie.service.JPAService.jdbc.driver</name>
1540 <value>org.apache.derby.jdbc.EmbeddedDriver</value>
1541 <description>
1542 JDBC driver class.
1543 </description>
1544 </property>
1545
1546 <property>
1547 <name>oozie.service.JPAService.jdbc.url</name>
1548 <value>jdbc:derby:${oozie.data.dir}/${oozie.db.schema.name}-db;create=true</value>
1549 <description>
1550 JDBC URL.
1551 </description>
1552 </property>
1553
1554 <property>
1555 <name>oozie.service.JPAService.jdbc.username</name>
1556 <value>sa</value>
1557 <description>
1558 DB user name.
1559 </description>
1560 </property>
1561
1562 <property>
1563 <name>oozie.service.JPAService.jdbc.password</name>
1564 <value> </value>
1565 <description>
1566 DB user password.
1567
1568 IMPORTANT: if password is emtpy leave a 1 space string, the service trims the value,
1569 if empty Configuration assumes it is NULL.
1570
1571 IMPORTANT: if the StoreServicePasswordService is active, it will reset this value with the value given in
1572 the console.
1573 </description>
1574 </property>
1575
1576 <property>
1577 <name>oozie.service.JPAService.pool.max.active.conn</name>
1578 <value>10</value>
1579 <description>
1580 Max number of connections.
1581 </description>
1582 </property>
1583
1584 <property>
1585 <name>oozie.service.JPAService.openjpa.BrokerImpl</name>
1586 <value>non-finalizing</value>
1587 <description>
1588 The default OpenJPAEntityManager implementation automatically closes itself during instance finalization.
1589 This guards against accidental resource leaks that may occur if a developer fails to explicitly close
1590 EntityManagers when finished with them, but it also incurs a scalability bottleneck, since the JVM must
1591 perform synchronization during instance creation, and since the finalizer thread will have more instances to monitor.
1592 To avoid this overhead, set the openjpa.BrokerImpl configuration property to non-finalizing.
1593 To use default implementation set it to empty space.
1594 </description>
1595 </property>
1596
1597 <property>
1598 <name>oozie.service.JPAService.retry.initial-wait-time.ms</name>
1599 <value>100</value>
1600 <description>
1601 Initial wait time in milliseconds between the first failed database operation and the re-attempted operation. The wait
1602 time is doubled at each retry.
1603 </description>
1604 </property>
1605
1606 <property>
1607 <name>oozie.service.JPAService.retry.maximum-wait-time.ms</name>
1608 <value>30000</value>
1609 <description>
1610 Maximum wait time between database retry attempts.
1611 </description>
1612 </property>
1613
1614 <property>
1615 <name>oozie.service.JPAService.retry.max-retries</name>
1616 <value>10</value>
1617 <description>
1618 Maximum number of retries for a failed database operation.
1619 </description>
1620 </property>
1621
1622 <!-- SchemaService -->
1623
1624 <property>
1625 <name>oozie.service.SchemaService.wf.schemas</name>
1626 <value>
1627 oozie-common-1.0.xsd,
1628 oozie-workflow-0.1.xsd,oozie-workflow-0.2.xsd,oozie-workflow-0.2.5.xsd,oozie-workflow-0.3.xsd,oozie-workflow-0.4.xsd,
1629 oozie-workflow-0.4.5.xsd,oozie-workflow-0.5.xsd,oozie-workflow-1.0.xsd,
1630 shell-action-0.1.xsd,shell-action-0.2.xsd,shell-action-0.3.xsd,shell-action-1.0.xsd,
1631 email-action-0.1.xsd,email-action-0.2.xsd,
1632 hive-action-0.2.xsd,hive-action-0.3.xsd,hive-action-0.4.xsd,hive-action-0.5.xsd,hive-action-0.6.xsd,hive-action-1.0.xsd,
1633 sqoop-action-0.2.xsd,sqoop-action-0.3.xsd,sqoop-action-0.4.xsd,sqoop-action-1.0.xsd,
1634 ssh-action-0.1.xsd,ssh-action-0.2.xsd,
1635 distcp-action-0.1.xsd,distcp-action-0.2.xsd,distcp-action-1.0.xsd,
1636 oozie-sla-0.1.xsd,oozie-sla-0.2.xsd,
1637 hive2-action-0.1.xsd,hive2-action-0.2.xsd,hive2-action-1.0.xsd,
1638 spark-action-0.1.xsd,spark-action-0.2.xsd,spark-action-1.0.xsd
1639 </value>
1640 <description>
1641 List of schemas for workflows (separated by commas).
1642 </description>
1643 </property>
1644
1645 <property>
1646 <name>oozie.service.SchemaService.wf.ext.schemas</name>
1647 <value> </value>
1648 <description>
1649 List of additional schemas for workflows (separated by commas).
1650 </description>
1651 </property>
1652
1653 <property>
1654 <name>oozie.service.SchemaService.coord.schemas</name>
1655 <value>
1656 oozie-coordinator-0.1.xsd,oozie-coordinator-0.2.xsd,oozie-coordinator-0.3.xsd,oozie-coordinator-0.4.xsd,
1657 oozie-coordinator-0.5.xsd,oozie-sla-0.1.xsd,oozie-sla-0.2.xsd
1658 </value>
1659 <description>
1660 List of schemas for coordinators (separated by commas).
1661 </description>
1662 </property>
1663
1664 <property>
1665 <name>oozie.service.SchemaService.coord.ext.schemas</name>
1666 <value> </value>
1667 <description>
1668 List of additional schemas for coordinators (separated by commas).
1669 </description>
1670 </property>
1671
1672 <property>
1673 <name>oozie.service.SchemaService.bundle.schemas</name>
1674 <value>
1675 oozie-bundle-0.1.xsd,oozie-bundle-0.2.xsd
1676 </value>
1677 <description>
1678 List of schemas for bundles (separated by commas).
1679 </description>
1680 </property>
1681
1682 <property>
1683 <name>oozie.service.SchemaService.bundle.ext.schemas</name>
1684 <value> </value>
1685 <description>
1686 List of additional schemas for bundles (separated by commas).
1687 </description>
1688 </property>
1689
1690 <property>
1691 <name>oozie.service.SchemaService.sla.schemas</name>
1692 <value>
1693 gms-oozie-sla-0.1.xsd,oozie-sla-0.2.xsd
1694 </value>
1695 <description>
1696 List of schemas for semantic validation for GMS SLA (separated by commas).
1697 </description>
1698 </property>
1699
1700 <property>
1701 <name>oozie.service.SchemaService.sla.ext.schemas</name>
1702 <value> </value>
1703 <description>
1704 List of additional schemas for semantic validation for GMS SLA (separated by commas).
1705 </description>
1706 </property>
1707
1708 <!-- CallbackService -->
1709
1710 <property>
1711 <name>oozie.service.CallbackService.base.url</name>
1712 <value>${oozie.base.url}/callback</value>
1713 <description>
1714 Base callback URL used by ActionExecutors.
1715 </description>
1716 </property>
1717
1718 <property>
1719 <name>oozie.service.CallbackService.early.requeue.max.retries</name>
1720 <value>5</value>
1721 <description>
1722 If Oozie receives a callback too early (while the action is in PREP state), it will requeue the command this many times
1723 to give the action time to transition to RUNNING.
1724 </description>
1725 </property>
1726
1727 <!-- CallbackServlet -->
1728
1729 <property>
1730 <name>oozie.servlet.CallbackServlet.max.data.len</name>
1731 <value>2048</value>
1732 <description>
1733 Max size in characters for the action completion data output.
1734 </description>
1735 </property>
1736
1737 <!-- External stats-->
1738
1739 <property>
1740 <name>oozie.external.stats.max.size</name>
1741 <value>-1</value>
1742 <description>
1743 Max size in bytes for action stats. -1 means infinite value.
1744 </description>
1745 </property>
1746
1747 <!-- JobCommand -->
1748
1749 <property>
1750 <name>oozie.JobCommand.job.console.url</name>
1751 <value>${oozie.base.url}?job=</value>
1752 <description>
1753 Base console URL for a workflow job.
1754 </description>
1755 </property>
1756
1757
1758 <!-- ActionService -->
1759
1760 <property>
1761 <name>oozie.service.ActionService.executor.classes</name>
1762 <value>
1763 org.apache.oozie.action.decision.DecisionActionExecutor,
1764 org.apache.oozie.action.hadoop.JavaActionExecutor,
1765 org.apache.oozie.action.hadoop.FsActionExecutor,
1766 org.apache.oozie.action.hadoop.MapReduceActionExecutor,
1767 org.apache.oozie.action.hadoop.PigActionExecutor,
1768 org.apache.oozie.action.hadoop.HiveActionExecutor,
1769 org.apache.oozie.action.hadoop.ShellActionExecutor,
1770 org.apache.oozie.action.hadoop.SqoopActionExecutor,
1771 org.apache.oozie.action.hadoop.DistcpActionExecutor,
1772 org.apache.oozie.action.hadoop.Hive2ActionExecutor,
1773 org.apache.oozie.action.ssh.SshActionExecutor,
1774 org.apache.oozie.action.oozie.SubWorkflowActionExecutor,
1775 org.apache.oozie.action.email.EmailActionExecutor,
1776 org.apache.oozie.action.hadoop.SparkActionExecutor
1777 </value>
1778 <description>
1779 List of ActionExecutors classes (separated by commas).
1780 Only action types with associated executors can be used in workflows.
1781 </description>
1782 </property>
1783
1784 <property>
1785 <name>oozie.service.ActionService.executor.ext.classes</name>
1786 <value> </value>
1787 <description>
1788 List of ActionExecutors extension classes (separated by commas). Only action types with associated
1789 executors can be used in workflows. This property is a convenience property to add extensions to the built
1790 in executors without having to include all the built in ones.
1791 </description>
1792 </property>
1793
1794 <!-- ActionCheckerService -->
1795
1796 <property>
1797 <name>oozie.service.ActionCheckerService.action.check.interval</name>
1798 <value>60</value>
1799 <description>
1800 The frequency at which the ActionCheckService will run.
1801 </description>
1802 </property>
1803
1804 <property>
1805 <name>oozie.service.ActionCheckerService.action.check.delay</name>
1806 <value>600</value>
1807 <description>
1808 The time, in seconds, between an ActionCheck for the same action.
1809 </description>
1810 </property>
1811
1812 <property>
1813 <name>oozie.service.ActionCheckerService.callable.batch.size</name>
1814 <value>10</value>
1815 <description>
1816 This value determines the number of actions which will be batched together
1817 to be executed by a single thread.
1818 </description>
1819 </property>
1820
1821 <!-- StatusTransitService -->
1822 <property>
1823 <name>oozie.service.StatusTransitService.statusTransit.interval</name>
1824 <value>60</value>
1825 <description>
1826 The frequency in seconds at which the StatusTransitService will run.
1827 </description>
1828 </property>
1829
1830 <property>
1831 <name>oozie.service.StatusTransitService.backward.support.for.coord.status</name>
1832 <value>false</value>
1833 <description>
1834 true, if coordinator job submits using 'uri:oozie:coordinator:0.1' and wants to keep Oozie 2.x status transit.
1835 if set true,
1836 1. SUCCEEDED state in coordinator job means materialization done.
1837 2. No DONEWITHERROR state in coordinator job
1838 3. No PAUSED or PREPPAUSED state in coordinator job
1839 4. PREPSUSPENDED becomes SUSPENDED in coordinator job
1840 </description>
1841 </property>
1842
1843 <property>
1844 <name>oozie.service.StatusTransitService.backward.support.for.states.without.error</name>
1845 <value>true</value>
1846 <description>
1847 true, if you want to keep Oozie 3.2 status transit.
1848 Change it to false for Oozie 4.x releases.
1849 if set true,
1850 No states like RUNNINGWITHERROR, SUSPENDEDWITHERROR and PAUSEDWITHERROR
1851 for coordinator and bundle
1852 </description>
1853 </property>
1854
1855 <!-- PauseTransitService -->
1856 <property>
1857 <name>oozie.service.PauseTransitService.PauseTransit.interval</name>
1858 <value>60</value>
1859 <description>
1860 The frequency in seconds at which the PauseTransitService will run.
1861 </description>
1862 </property>
1863
1864 <!-- LauncherAMUtils -->
1865 <property>
1866 <name>oozie.action.max.output.data</name>
1867 <value>2048</value>
1868 <description>
1869 Max size in characters for output data.
1870 </description>
1871 </property>
1872
1873 <property>
1874 <name>oozie.action.fs.glob.max</name>
1875 <value>50000</value>
1876 <description>
1877 Maximum number of globbed files.
1878 </description>
1879 </property>
1880
1881 <!-- JavaActionExecutor -->
1882 <!-- This is common to the subclasses of action executors for Java (e.g. map-reduce, pig, hive, java, etc) -->
1883
1884 <property>
1885 <name>oozie.action.launcher.am.restart.kill.childjobs</name>
1886 <value>true</value>
1887 <description>
1888 Multiple instances of launcher jobs can happen due to RM non-work preserving recovery on RM restart, AM recovery
1889 due to crashes or AM network connectivity loss. This could also lead to orphaned child jobs of the old AM attempts
1890 leading to conflicting runs. This kills child jobs of previous attempts using YARN application tags.
1891 </description>
1892 </property>
1893
1894 <property>
1895 <name>oozie.action.spark.setup.hadoop.conf.dir</name>
1896 <value>false</value>
1897 <description>
1898 Oozie action.xml (oozie.action.conf.xml) contains all the hadoop configuration and user provided configurations.
1899 This property will allow users to copy Oozie action.xml as hadoop *-site configurations files. The advantage is,
1900 user need not to manage these files into spark sharelib. If user wants to manage the hadoop configurations
1901 themselves, it should should disable it.
1902 </description>
1903 </property>
1904
1905 <property>
1906 <name>oozie.action.shell.setup.hadoop.conf.dir</name>
1907 <value>false</value>
1908 <description>
1909 The Shell action is commonly used to run programs that rely on HADOOP_CONF_DIR (e.g. hive, beeline, sqoop, etc). With
1910 YARN, HADOO_CONF_DIR is set to the NodeManager's copies of Hadoop's *-site.xml files, which can be problematic because
1911 (a) they are for meant for the NM, not necessarily clients, and (b) they won't have any of the configs that Oozie, or
1912 the user through Oozie, sets. When this property is set to true, The Shell action will prepare the *-site.xml files
1913 based on the correct config and set HADOOP_CONF_DIR to point to it. Setting it to false will make Oozie leave
1914 HADOOP_CONF_DIR alone. This can also be set at the Action level by putting it in the Shell Action's configuration
1915 section, which also has priorty. That all said, it's recommended to use the appropriate action type when possible.
1916 </description>
1917 </property>
1918
1919 <property>
1920 <name>oozie.action.shell.setup.hadoop.conf.dir.write.log4j.properties</name>
1921 <value>true</value>
1922 <description>
1923 Toggle to control if a log4j.properties file should be written into the configuration directory prepared when
1924 oozie.action.shell.setup.hadoop.conf.dir is enabled. This is used to control logging behavior of log4j using commands
1925 run within the shell action script, and to ensure logging does not impact output data capture if leaked to stdout.
1926 Content of the written file is determined by the value of oozie.action.shell.setup.hadoop.conf.dir.log4j.content.
1927 </description>
1928 </property>
1929
1930 <property>
1931 <name>oozie.action.shell.setup.hadoop.conf.dir.log4j.content</name>
1932 <value>
1933 log4j.rootLogger=INFO,console
1934 log4j.appender.console=org.apache.log4j.ConsoleAppender
1935 log4j.appender.console.target=System.err
1936 log4j.appender.console.layout=org.apache.log4j.PatternLayout
1937 log4j.appender.console.layout.ConversionPattern=%d{yy/MM/dd HH:mm:ss} %p %c{2}: %m%n
1938 </value>
1939 <description>
1940 The value to write into a log4j.properties file under the config directory created when
1941 oozie.action.shell.setup.hadoop.conf.dir and oozie.action.shell.setup.hadoop.conf.dir.write.log4j.properties
1942 properties are both enabled. The values must be properly newline separated and in format expected by Log4J.
1943 Trailing and preceding whitespaces will be trimmed when reading this property.
1944 This is used to control logging behavior of log4j using commands run within the shell action script.
1945 </description>
1946 </property>
1947
1948 <property>
1949 <name>oozie.action.shell.max-print-size-kb</name>
1950 <value>128</value>
1951 <description>
1952 When an oozie shell action starts, the shell script will be printed. Scripts larger than the size configured here
1953 (in KiB) will not be printed. If this value is less than or equal to zero, the script will not be printed.
1954 </description>
1955 </property>
1956
1957 <property>
1958 <name>oozie.action.launcher.yarn.timeline-service.enabled</name>
1959 <value>false</value>
1960 <description>
1961 Enables/disables getting delegation tokens for ATS for the launcher job in
1962 YARN/Hadoop 2.6 (no effect in Hadoop 1) for all action types by default if tez-site.xml is present in
1963 distributed cache.
1964 This can be overridden on a per-action basis by setting
1965 oozie.launcher.yarn.timeline-service.enabled in an action's configuration section in a workflow.
1966 </description>
1967 </property>
1968
1969 <property>
1970 <name>oozie.action.pig.log.expandedscript</name>
1971 <value>true</value>
1972 <description>
1973 Log the expanded pig script in launcher stdout log
1974 </description>
1975 </property>
1976
1977 <property>
1978 <name>oozie.action.rootlogger.log.level</name>
1979 <value>INFO</value>
1980 <description>
1981 Logging level for root logger
1982 </description>
1983 </property>
1984
1985 <!-- HadoopActionExecutor -->
1986 <!-- This is common to the subclasses action executors for map-reduce and pig -->
1987
1988 <property>
1989 <name>oozie.action.retries.max</name>
1990 <value>3</value>
1991 <description>
1992 The number of retries for executing an action in case of failure
1993 </description>
1994 </property>
1995
1996 <property>
1997 <name>oozie.action.retry.interval</name>
1998 <value>10</value>
1999 <description>
2000 The interval between retries of an action in case of failure
2001 </description>
2002 </property>
2003
2004 <property>
2005 <name>oozie.action.retry.policy</name>
2006 <value>periodic</value>
2007 <description>
2008 Retry policy of an action in case of failure. Possible values are periodic/exponential
2009 </description>
2010 </property>
2011
2012 <!-- SshActionExecutor -->
2013
2014 <property>
2015 <name>oozie.action.ssh.delete.remote.tmp.dir</name>
2016 <value>true</value>
2017 <description>
2018 If set to true, it will delete temporary directory at the end of execution of ssh action.
2019 </description>
2020 </property>
2021
2022 <property>
2023 <name>oozie.action.ssh.http.command</name>
2024 <value>curl</value>
2025 <description>
2026 Command to use for callback to oozie, normally is 'curl' or 'wget'.
2027 The command must available in PATH environment variable of the USER@HOST box shell.
2028 </description>
2029 </property>
2030
2031 <property>
2032 <name>oozie.action.ssh.http.command.post.options</name>
2033 <value>--data-binary @#stdout --request POST --header "content-type:text/plain"</value>
2034 <description>
2035 The callback command POST options.
2036 Used when the ouptut of the ssh action is captured.
2037 </description>
2038 </property>
2039
2040 <property>
2041 <name>oozie.action.ssh.allow.user.at.host</name>
2042 <value>true</value>
2043 <description>
2044 Specifies whether the user specified by the ssh action is allowed or is to be replaced
2045 by the Job user
2046 </description>
2047 </property>
2048
2049 <!-- SubworkflowActionExecutor -->
2050
2051 <property>
2052 <name>oozie.action.subworkflow.max.depth</name>
2053 <value>50</value>
2054 <description>
2055 The maximum depth for subworkflows. For example, if set to 3, then a workflow can start subwf1, which can start subwf2,
2056 which can start subwf3; but if subwf3 tries to start subwf4, then the action will fail. This is helpful in preventing
2057 errant workflows from starting infintely recursive subworkflows.
2058 </description>
2059 </property>
2060
2061 <!-- HadoopAccessorService -->
2062
2063 <property>
2064 <name>oozie.service.HadoopAccessorService.kerberos.enabled</name>
2065 <value>false</value>
2066 <description>
2067 Indicates if Oozie is configured to use Kerberos.
2068 </description>
2069 </property>
2070
2071 <property>
2072 <name>local.realm</name>
2073 <value>LOCALHOST</value>
2074 <description>
2075 Kerberos Realm used by Oozie and Hadoop. Using 'local.realm' to be aligned with Hadoop configuration
2076 </description>
2077 </property>
2078
2079 <property>
2080 <name>oozie.service.HadoopAccessorService.keytab.file</name>
2081 <value>${user.home}/oozie.keytab</value>
2082 <description>
2083 Location of the Oozie user keytab file.
2084 </description>
2085 </property>
2086
2087 <property>
2088 <name>oozie.service.HadoopAccessorService.kerberos.principal</name>
2089 <value>${user.name}/localhost@${local.realm}</value>
2090 <description>
2091 Kerberos principal for Oozie service.
2092 </description>
2093 </property>
2094
2095 <property>
2096 <name>oozie.service.HadoopAccessorService.jobTracker.whitelist</name>
2097 <value> </value>
2098 <description>
2099 Whitelisted job tracker for Oozie service.
2100 </description>
2101 </property>
2102
2103 <property>
2104 <name>oozie.service.HadoopAccessorService.nameNode.whitelist</name>
2105 <value> </value>
2106 <description>
2107 Whitelisted job tracker for Oozie service.
2108 </description>
2109 </property>
2110
2111 <property>
2112 <name>oozie.service.HadoopAccessorService.hadoop.configurations</name>
2113 <value>*=hadoop-conf</value>
2114 <description>
2115 Comma separated AUTHORITY=HADOOP_CONF_DIR, where AUTHORITY is the HOST:PORT of
2116 the Hadoop service (JobTracker, YARN, HDFS). The wildcard '*' configuration is
2117 used when there is no exact match for an authority. The HADOOP_CONF_DIR contains
2118 the relevant Hadoop *-site.xml files. If the path is relative is looked within
2119 the Oozie configuration directory; though the path can be absolute (i.e. to point
2120 to Hadoop client conf/ directories in the local filesystem.
2121 </description>
2122 </property>
2123
2124
2125 <property>
2126 <name>oozie.service.HadoopAccessorService.action.configurations</name>
2127 <value>*=action-conf</value>
2128 <description>
2129 Comma separated AUTHORITY=ACTION_CONF_DIR, where AUTHORITY is the HOST:PORT of
2130 the Hadoop MapReduce service (JobTracker, YARN). The wildcard '*' configuration is
2131 used when there is no exact match for an authority. The ACTION_CONF_DIR may contain
2132 ACTION.xml files where ACTION is the action type ('java', 'map-reduce', 'pig',
2133 'hive', 'sqoop', etc.). If the ACTION.xml file exists, its properties will be used
2134 as defaults properties for the action. If the path is relative is looked within
2135 the Oozie configuration directory; though the path can be absolute (i.e. to point
2136 to Hadoop client conf/ directories in the local filesystem.
2137 </description>
2138 </property>
2139
2140 <property>
2141 <name>oozie.service.HadoopAccessorService.action.configurations.load.default.resources</name>
2142 <value>true</value>
2143 <description>
2144 true means that default and site xml files of hadoop (core-default, core-site,
2145 hdfs-default, hdfs-site, mapred-default, mapred-site, yarn-default, yarn-site)
2146 are parsed into actionConf on Oozie server. false means that site xml files are
2147 not loaded on server, instead loaded on launcher node.
2148 This is only done for pig and hive actions which handle loading those files
2149 automatically from the classpath on launcher task. It defaults to true.
2150 </description>
2151 </property>
2152
2153 <!-- Credentials -->
2154 <property>
2155 <name>oozie.credentials.credentialclasses</name>
2156 <value> </value>
2157 <description>
2158 A list of credential class mapping for CredentialsProvider
2159 </description>
2160 </property>
2161 <property>
2162 <name>oozie.credentials.skip</name>
2163 <value>false</value>
2164 <description>
2165 This determines if Oozie should skip getting credentials from the credential providers. This can be overwritten at a
2166 job-level or action-level.
2167 </description>
2168 </property>
2169
2170 <property>
2171 <name>oozie.actions.main.classnames</name>
2172 <value>distcp=org.apache.hadoop.tools.DistCp</value>
2173 <description>
2174 A list of class name mapping for Action classes
2175 </description>
2176 </property>
2177
2178 <property>
2179 <name>oozie.service.WorkflowAppService.system.libpath</name>
2180 <value>/user/${user.name}/share/lib</value>
2181 <description>
2182 System library path to use for workflow applications.
2183 This path is added to workflow application if their job properties sets
2184 the property 'oozie.use.system.libpath' to true.
2185 </description>
2186 </property>
2187
2188 <property>
2189 <name>oozie.command.default.lock.timeout</name>
2190 <value>5000</value>
2191 <description>
2192 Default timeout (in milliseconds) for commands for acquiring an exclusive lock on an entity.
2193 </description>
2194 </property>
2195
2196 <property>
2197 <name>oozie.command.default.requeue.delay</name>
2198 <value>10000</value>
2199 <description>
2200 Default time (in milliseconds) for commands that are requeued for delayed execution.
2201 </description>
2202 </property>
2203
2204 <!-- LiteWorkflowStoreService, Workflow Action Automatic Retry -->
2205
2206 <property>
2207 <name>oozie.service.LiteWorkflowStoreService.user.retry.max</name>
2208 <value>3</value>
2209 <description>
2210 Automatic retry max count for workflow action is 3 in default.
2211 </description>
2212 </property>
2213
2214 <property>
2215 <name>oozie.service.LiteWorkflowStoreService.user.retry.inteval</name>
2216 <value>10</value>
2217 <description>
2218 Automatic retry interval for workflow action is in minutes and the default value is 10 minutes.
2219 </description>
2220 </property>
2221
2222 <property>
2223 <name>oozie.service.LiteWorkflowStoreService.user.retry.policy</name>
2224 <value>periodic</value>
2225 <description>
2226 Automatic retry policy for workflow action. Possible values are periodic or exponential, periodic being the default.
2227 </description>
2228 </property>
2229
2230 <property>
2231 <name>oozie.service.LiteWorkflowStoreService.user.retry.error.code</name>
2232 <value>JA008,JA009,JA017,JA018,JA019,FS009,FS008,FS014</value>
2233 <description>
2234 Automatic retry interval for workflow action is handled for these specified error code:
2235 FS009, FS008 is file exists error when using chmod in fs action.
2236 FS014 is permission error in fs action
2237 JA018 is output directory exists error in workflow map-reduce action.
2238 JA019 is error while executing distcp action.
2239 JA017 is job not exists error in action executor.
2240 JA008 is FileNotFoundException in action executor.
2241 JA009 is IOException in action executor.
2242 ALL is the any kind of error in action executor.
2243 </description>
2244 </property>
2245
2246 <property>
2247 <name>oozie.service.LiteWorkflowStoreService.user.retry.error.code.ext</name>
2248 <value> </value>
2249 <description>
2250 Automatic retry interval for workflow action is handled for these specified extra error code:
2251 ALL is the any kind of error in action executor.
2252 </description>
2253 </property>
2254
2255 <property>
2256 <name>oozie.service.LiteWorkflowStoreService.node.def.version</name>
2257 <value>_oozie_inst_v_2</value>
2258 <description>
2259 NodeDef default version, _oozie_inst_v_0, _oozie_inst_v_1 or _oozie_inst_v_2
2260 </description>
2261 </property>
2262
2263 <!-- Oozie Authentication -->
2264
2265 <property>
2266 <name>oozie.authentication.type</name>
2267 <value>simple</value>
2268 <description>
2269 Defines authentication used for Oozie HTTP endpoint.
2270 Supported values are: simple | kerberos | #AUTHENTICATION_HANDLER_CLASSNAME#
2271 </description>
2272 </property>
2273 <property>
2274 <name>oozie.server.authentication.type</name>
2275 <value>${oozie.authentication.type}</value>
2276 <description>
2277 Defines authentication used for Oozie server communicating to other Oozie server over HTTP(s).
2278 Supported values are: simple | kerberos | #AUTHENTICATOR_CLASSNAME#
2279 </description>
2280 </property>
2281
2282 <property>
2283 <name>oozie.server.connection.timeout.seconds</name>
2284 <value>180</value>
2285 <description>
2286 Defines connection timeout used for Oozie server communicating to other Oozie server over HTTP(s). Default is 3 min.
2287 </description>
2288 </property>
2289
2290 <property>
2291 <name>oozie.authentication.token.validity</name>
2292 <value>36000</value>
2293 <description>
2294 Indicates how long (in seconds) an authentication token is valid before it has
2295 to be renewed.
2296 </description>
2297 </property>
2298
2299 <property>
2300 <name>oozie.authentication.cookie.domain</name>
2301 <value></value>
2302 <description>
2303 The domain to use for the HTTP cookie that stores the authentication token.
2304 In order to authentiation to work correctly across multiple hosts
2305 the domain must be correctly set.
2306 </description>
2307 </property>
2308
2309 <property>
2310 <name>oozie.authentication.simple.anonymous.allowed</name>
2311 <value>true</value>
2312 <description>
2313 Indicates if anonymous requests are allowed when using 'simple' authentication.
2314 </description>
2315 </property>
2316
2317 <property>
2318 <name>oozie.authentication.kerberos.principal</name>
2319 <value>HTTP/localhost@${local.realm}</value>
2320 <description>
2321 Indicates the Kerberos principal to be used for HTTP endpoint.
2322 The principal MUST start with 'HTTP/' as per Kerberos HTTP SPNEGO specification.
2323 </description>
2324 </property>
2325
2326 <property>
2327 <name>oozie.authentication.kerberos.keytab</name>
2328 <value>${oozie.service.HadoopAccessorService.keytab.file}</value>
2329 <description>
2330 Location of the keytab file with the credentials for the principal.
2331 Referring to the same keytab file Oozie uses for its Kerberos credentials for Hadoop.
2332 </description>
2333 </property>
2334
2335 <property>
2336 <name>oozie.authentication.kerberos.name.rules</name>
2337 <value>DEFAULT</value>
2338 <description>
2339 The kerberos names rules is to resolve kerberos principal names, refer to Hadoop's
2340 KerberosName for more details.
2341 </description>
2342 </property>
2343
2344 <!-- Coordinator "NONE" execution order default time tolerance -->
2345 <property>
2346 <name>oozie.coord.execution.none.tolerance</name>
2347 <value>1</value>
2348 <description>
2349 Default time tolerance in minutes after action nominal time for an action to be skipped
2350 when execution order is "NONE"
2351 </description>
2352 </property>
2353
2354 <!-- Coordinator Actions default length -->
2355 <property>
2356 <name>oozie.coord.actions.default.length</name>
2357 <value>1000</value>
2358 <description>
2359 Default number of coordinator actions to be retrieved by the info command
2360 </description>
2361 </property>
2362
2363 <!-- ForkJoin validation -->
2364 <property>
2365 <name>oozie.validate.ForkJoin</name>
2366 <value>true</value>
2367 <description>
2368 If true, fork and join should be validated at wf submission time.
2369 </description>
2370 </property>
2371
2372 <property>
2373 <name>oozie.workflow.parallel.fork.action.start</name>
2374 <value>true</value>
2375 <description>
2376 Determines how Oozie processes starting of forked actions. If true, forked actions and their job submissions
2377 are done in parallel which is best for performance. If false, they are submitted sequentially.
2378 </description>
2379 </property>
2380
2381 <property>
2382 <name>oozie.coord.action.get.all.attributes</name>
2383 <value>false</value>
2384 <description>
2385 Setting to true is not recommended as coord job/action info will bring all columns of the action in memory.
2386 Set it true only if backward compatibility for action/job info is required.
2387 </description>
2388 </property>
2389
2390 <property>
2391 <name>oozie.service.HadoopAccessorService.supported.filesystems</name>
2392 <value>hdfs,hftp,webhdfs</value>
2393 <description>
2394 Enlist the different filesystems supported for federation. If wildcard "*" is specified,
2395 then ALL file schemes will be allowed.
2396 </description>
2397 </property>
2398
2399 <property>
2400 <name>oozie.service.URIHandlerService.uri.handlers</name>
2401 <value>org.apache.oozie.dependency.FSURIHandler</value>
2402 <description>
2403 Enlist the different uri handlers supported for data availability checks.
2404 </description>
2405 </property>
2406 <!-- Oozie HTTP Notifications -->
2407
2408 <property>
2409 <name>oozie.notification.url.connection.timeout</name>
2410 <value>10000</value>
2411 <description>
2412 Defines the timeout, in milliseconds, for Oozie HTTP notification callbacks. Oozie does
2413 HTTP notifications for workflow jobs which set the 'oozie.wf.action.notification.url',
2414 'oozie.wf.worklfow.notification.url' and/or 'oozie.coord.action.notification.url'
2415 properties in their job.properties. Refer to section '5 Oozie Notifications' in the
2416 Workflow specification for details.
2417 </description>
2418 </property>
2419
2420
2421 <!-- Enable Distributed Cache workaround for Hadoop 2.0.2-alpha (MAPREDUCE-4820) -->
2422 <property>
2423 <name>oozie.hadoop-2.0.2-alpha.workaround.for.distributed.cache</name>
2424 <value>false</value>
2425 <description>
2426 Due to a bug in Hadoop 2.0.2-alpha, MAPREDUCE-4820, launcher jobs fail to set
2427 the distributed cache for the action job because the local JARs are implicitly
2428 included triggering a duplicate check.
2429 This flag removes the distributed cache files for the action as they'll be
2430 included from the local JARs of the JobClient (MRApps) submitting the action
2431 job from the launcher.
2432 </description>
2433 </property>
2434
2435 <property>
2436 <name>oozie.service.EventHandlerService.filter.app.types</name>
2437 <value>workflow_job, coordinator_action</value>
2438 <description>
2439 The app-types among workflow/coordinator/bundle job/action for which
2440 for which events system is enabled.
2441 </description>
2442 </property>
2443
2444 <property>
2445 <name>oozie.service.EventHandlerService.event.queue</name>
2446 <value>org.apache.oozie.event.MemoryEventQueue</value>
2447 <description>
2448 The implementation for EventQueue in use by the EventHandlerService.
2449 </description>
2450 </property>
2451
2452 <property>
2453 <name>oozie.service.EventHandlerService.event.listeners</name>
2454 <value>org.apache.oozie.jms.JMSJobEventListener</value>
2455 </property>
2456
2457 <property>
2458 <name>oozie.service.EventHandlerService.queue.size</name>
2459 <value>10000</value>
2460 <description>
2461 Maximum number of events to be contained in the event queue.
2462 </description>
2463 </property>
2464
2465 <property>
2466 <name>oozie.service.EventHandlerService.worker.interval</name>
2467 <value>30</value>
2468 <description>
2469 The default interval (seconds) at which the worker threads will be scheduled to run
2470 and process events.
2471 </description>
2472 </property>
2473
2474 <property>
2475 <name>oozie.service.EventHandlerService.batch.size</name>
2476 <value>10</value>
2477 <description>
2478 The batch size for batched draining per thread from the event queue.
2479 </description>
2480 </property>
2481
2482 <property>
2483 <name>oozie.service.EventHandlerService.worker.threads</name>
2484 <value>3</value>
2485 <description>
2486 Number of worker threads to be scheduled to run and process events.
2487 </description>
2488 </property>
2489
2490 <property>
2491 <name>oozie.sla.service.SLAService.capacity</name>
2492 <value>5000</value>
2493 <description>
2494 Maximum number of sla records to be contained in the memory structure.
2495 </description>
2496 </property>
2497
2498 <property>
2499 <name>oozie.sla.service.SLAService.alert.events</name>
2500 <value>END_MISS</value>
2501 <description>
2502 Default types of SLA events for being alerted of.
2503 </description>
2504 </property>
2505
2506 <property>
2507 <name>oozie.sla.service.SLAService.calculator.impl</name>
2508 <value>org.apache.oozie.sla.SLACalculatorMemory</value>
2509 <description>
2510 The implementation for SLACalculator in use by the SLAService.
2511 </description>
2512 </property>
2513
2514 <property>
2515 <name>oozie.sla.service.SLAService.job.event.latency</name>
2516 <value>90000</value>
2517 <description>
2518 Time in milliseconds to account of latency of getting the job status event
2519 to compare against and decide sla miss/met
2520 </description>
2521 </property>
2522
2523 <property>
2524 <name>oozie.sla.service.SLAService.check.interval</name>
2525 <value>30</value>
2526 <description>
2527 Time interval, in seconds, at which SLA Worker will be scheduled to run
2528 </description>
2529 </property>
2530
2531 <property>
2532 <name>oozie.sla.disable.alerts.older.than</name>
2533 <value>48</value>
2534 <description>
2535 Time threshold, in HOURS, for disabling SLA alerting for jobs whose
2536 nominal time is older than this.
2537 </description>
2538 </property>
2539
2540 <!-- ZooKeeper configuration -->
2541 <property>
2542 <name>oozie.zookeeper.connection.string</name>
2543 <value>localhost:2181</value>
2544 <description>
2545 Comma-separated values of host:port pairs of the ZooKeeper servers.
2546 </description>
2547 </property>
2548
2549 <property>
2550 <name>oozie.zookeeper.namespace</name>
2551 <value>oozie</value>
2552 <description>
2553 The namespace to use. All of the Oozie Servers that are planning on talking to each other should have the same
2554 namespace.
2555 </description>
2556 </property>
2557
2558 <property>
2559 <name>oozie.zookeeper.connection.timeout</name>
2560 <value>180</value>
2561 <description>
2562 Default ZK connection timeout (in sec).
2563 </description>
2564 </property>
2565 <property>
2566 <name>oozie.zookeeper.session.timeout</name>
2567 <value>300</value>
2568 <description>
2569 Default ZK session timeout (in sec). If connection is lost even after retry, then Oozie server will shutdown
2570 itself if oozie.zookeeper.server.shutdown.ontimeout is true.
2571 </description>
2572 </property>
2573 <property>
2574 <name>oozie.zookeeper.max.retries</name>
2575 <value>10</value>
2576 <description>
2577 Maximum number of times to retry.
2578 </description>
2579 </property>
2580
2581 <property>
2582 <name>oozie.zookeeper.server.shutdown.ontimeout</name>
2583 <value>true</value>
2584 <description>
2585 If true, Oozie server will shutdown itself on ZK
2586 connection timeout.
2587 </description>
2588 </property>
2589
2590 <property>
2591 <name>oozie.service.ZKLocksService.lock.release.retry.time.limit.minutes</name>
2592 <value>30</value>
2593 <description>
2594 On exception while releasing the lock, Oozie will exponentially retry till specified minutes before giving up.
2595 </description>
2596 </property>
2597
2598 <property>
2599 <name>oozie.http.hostname</name>
2600 <value>0.0.0.0</value>
2601 <description>
2602 Oozie server host name. The network interface Oozie server binds to as an IP address or a hostname.
2603 Most users won't need to change this setting from the default value.
2604 </description>
2605 </property>
2606
2607 <property>
2608 <name>oozie.http.port</name>
2609 <value>11000</value>
2610 <description>
2611 Oozie server port.
2612 </description>
2613 </property>
2614
2615 <property>
2616 <name>oozie.http.request.header.size</name>
2617 <value>65536</value>
2618 <description>
2619 Oozie HTTP request header size.
2620 </description>
2621 </property>
2622
2623 <property>
2624 <name>oozie.http.response.header.size</name>
2625 <value>65536</value>
2626 <description>
2627 Oozie HTTP response header size.
2628 </description>
2629 </property>
2630
2631 <property>
2632 <name>oozie.https.port</name>
2633 <value>11443</value>
2634 <description>
2635 Oozie ssl server port.
2636 </description>
2637 </property>
2638
2639 <property>
2640 <name>oozie.https.enabled</name>
2641 <value>false</value>
2642 <description>
2643 Controls whether SSL encryption is enabled.
2644 </description>
2645 </property>
2646
2647 <property>
2648 <name>oozie.https.truststore.file</name>
2649 <value></value>
2650 <description>
2651 Path to a TrustStore file.
2652 </description>
2653 </property>
2654
2655 <property>
2656 <name>oozie.https.keystore.file</name>
2657 <value></value>
2658 <description>
2659 Path to a KeyStore file.
2660 </description>
2661 </property>
2662
2663 <property>
2664 <name>oozie.https.keystore.pass</name>
2665 <value></value>
2666 <description>
2667 Password to the KeyStore.
2668 </description>
2669 </property>
2670
2671 <property>
2672 <name>oozie.https.include.protocols</name>
2673 <value>TLSv1,SSLv2Hello,TLSv1.1,TLSv1.2</value>
2674 <description>
2675 Enabled TLS protocols.
2676 </description>
2677 </property>
2678
2679 <property>
2680 <name>oozie.https.exclude.protocols</name>
2681 <value></value>
2682 <description>
2683 Disabled TLS protocols.
2684 </description>
2685 </property>
2686
2687 <property>
2688 <name>oozie.https.include.cipher.suites</name>
2689 <value></value>
2690 <description>
2691 List of Cipher suites to include.
2692 </description>
2693 </property>
2694
2695 <property>
2696 <name>oozie.https.exclude.cipher.suites</name>
2697 <value>TLS_ECDHE_RSA_WITH_RC4_128_SHA,SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA,SSL_RSA_WITH_DES_CBC_SHA,SSL_DHE_RSA_WITH_DES_CBC_SHA,SSL_RSA_EXPORT_WITH_RC4_40_MD5,SSL_RSA_EXPORT_WITH_DES40_CBC_SHA,SSL_RSA_WITH_RC4_128_MD5</value>
2698 <description>
2699 List of weak Cipher suites to exclude.
2700 </description>
2701 </property>
2702
2703 <property>
2704 <name>oozie.jsp.tmp.dir</name>
2705 <value>/tmp</value>
2706 <description>
2707 Temporary directory for compiling JSP pages.
2708 </description>
2709 </property>
2710
2711 <property>
2712 <name>oozie.server.threadpool.max.threads</name>
2713 <value>150</value>
2714 <description>
2715 Controls the threadpool size for the Oozie Server (if using embbedded Jetty)
2716 </description>
2717 </property>
2718
2719 <!-- Sharelib Configuration -->
2720 <property>
2721 <name>oozie.service.ShareLibService.mapping.file</name>
2722 <value> </value>
2723 <description>
2724 Sharelib mapping files contains list of key=value,
2725 where key will be the sharelib name for the action and value is a comma separated list of
2726 DFS or local filesystem directories or jar files.
2727 Example.
2728 oozie.pig_10=hdfs:///share/lib/pig/pig-0.10.1/lib/
2729 oozie.pig=hdfs:///share/lib/pig/pig-0.11.1/lib/
2730 oozie.distcp=hdfs:///share/lib/hadoop-2.2.0/share/hadoop/tools/lib/hadoop-distcp-2.2.0.jar
2731 oozie.hive=file:///usr/local/oozie/share/lib/hive/
2732 </description>
2733
2734 </property>
2735 <property>
2736 <name>oozie.service.ShareLibService.fail.fast.on.startup</name>
2737 <value>false</value>
2738 <description>
2739 Fails server starup if sharelib initilzation fails.
2740 </description>
2741 </property>
2742
2743 <property>
2744 <name>oozie.service.ShareLibService.purge.interval</name>
2745 <value>1</value>
2746 <description>
2747 How often, in days, Oozie should check for old ShareLibs and LauncherLibs to purge from HDFS.
2748 </description>
2749 </property>
2750
2751 <property>
2752 <name>oozie.service.ShareLibService.temp.sharelib.retention.days</name>
2753 <value>7</value>
2754 <description>
2755 ShareLib retention time in days.
2756 </description>
2757 </property>
2758
2759 <property>
2760 <name>oozie.action.ship.launcher.jar</name>
2761 <value>false</value>
2762 <description>
2763 Specifies whether launcher jar is shipped or not.
2764 </description>
2765 </property>
2766
2767 <property>
2768 <name>oozie.action.jobinfo.enable</name>
2769 <value>false</value>
2770 <description>
2771 JobInfo will contain information of bundle, coordinator, workflow and actions. If enabled, hadoop job will have
2772 property(oozie.job.info) which value is multiple key/value pair separated by ",". This information can be used for
2773 analytics like how many oozie jobs are submitted for a particular period, what is the total number of failed pig jobs,
2774 etc from mapreduce job history logs and configuration.
2775 User can also add custom workflow property to jobinfo by adding property which prefix with "oozie.job.info."
2776 Eg.
2777 oozie.job.info="bundle.id=,bundle.name=,coord.name=,coord.nominal.time=,coord.name=,wf.id=,
2778 wf.name=,action.name=,action.type=,launcher=true"
2779 </description>
2780 </property>
2781
2782 <property>
2783 <name>oozie.service.XLogStreamingService.max.log.scan.duration</name>
2784 <value>-1</value>
2785 <description>
2786 Max log scan duration in hours. If log scan request end_date - start_date > value,
2787 then exception is thrown to reduce the scan duration. -1 indicate no limit.
2788 </description>
2789 </property>
2790
2791 <property>
2792 <name>oozie.service.XLogStreamingService.actionlist.max.log.scan.duration</name>
2793 <value>-1</value>
2794 <description>
2795 Max log scan duration in hours for coordinator job when list of actions are specified.
2796 If log streaming request end_date - start_date > value, then exception is thrown to reduce the scan duration.
2797 -1 indicate no limit.
2798 This setting is separate from max.log.scan.duration as we want to allow higher durations when actions are specified.
2799 </description>
2800 </property>
2801
2802 <!-- JvmPauseMonitorService Configuration -->
2803 <property>
2804 <name>oozie.service.JvmPauseMonitorService.warn-threshold.ms</name>
2805 <value>10000</value>
2806 <description>
2807 The JvmPauseMonitorService runs a thread that repeatedly tries to detect when the JVM pauses, which could indicate
2808 that the JVM or host machine is overloaded or other problems. This thread sleeps for 500ms; if it sleeps for
2809 significantly longer, then there is likely a problem. This property specifies the threadshold for when Oozie should log
2810 a WARN level message; there is also a counter named "jvm.pause.warn-threshold".
2811 </description>
2812 </property>
2813
2814 <property>
2815 <name>oozie.service.JvmPauseMonitorService.info-threshold.ms</name>
2816 <value>1000</value>
2817 <description>
2818 The JvmPauseMonitorService runs a thread that repeatedly tries to detect when the JVM pauses, which could indicate
2819 that the JVM or host machine is overloaded or other problems. This thread sleeps for 500ms; if it sleeps for
2820 significantly longer, then there is likely a problem. This property specifies the threadshold for when Oozie should log
2821 an INFO level message; there is also a counter named "jvm.pause.info-threshold".
2822 </description>
2823 </property>
2824
2825 <property>
2826 <name>oozie.service.ZKLocksService.locks.reaper.threshold</name>
2827 <value>300</value>
2828 <description>
2829 The frequency at which the ChildReaper will run.
2830 Duration should be in sec. Default is 5 min.
2831 </description>
2832 </property>
2833
2834 <property>
2835 <name>oozie.service.ZKLocksService.locks.reaper.threads</name>
2836 <value>2</value>
2837 <description>
2838 Number of fixed threads used by ChildReaper to
2839 delete empty locks.
2840 </description>
2841 </property>
2842
2843 <property>
2844 <name>oozie.service.AbandonedCoordCheckerService.check.interval
2845 </name>
2846 <value>1440</value>
2847 <description>
2848 Interval, in minutes, at which AbandonedCoordCheckerService should run.
2849 </description>
2850 </property>
2851
2852 <property>
2853 <name>oozie.service.AbandonedCoordCheckerService.check.delay
2854 </name>
2855 <value>60</value>
2856 <description>
2857 Delay, in minutes, at which AbandonedCoordCheckerService should run.
2858 </description>
2859 </property>
2860
2861 <property>
2862 <name>oozie.service.AbandonedCoordCheckerService.failure.limit
2863 </name>
2864 <value>25</value>
2865 <description>
2866 Failure limit. A job is considered to be abandoned/faulty if total number of actions in
2867 failed/timedout/suspended >= "Failure limit" and there are no succeeded action.
2868 </description>
2869 </property>
2870
2871 <property>
2872 <name>oozie.service.AbandonedCoordCheckerService.kill.jobs
2873 </name>
2874 <value>false</value>
2875 <description>
2876 If true, AbandonedCoordCheckerService will kill abandoned coords.
2877 </description>
2878 </property>
2879
2880 <property>
2881 <name>oozie.service.AbandonedCoordCheckerService.job.older.than</name>
2882 <value>2880</value>
2883 <description>
2884 In minutes, job will be considered as abandoned/faulty if job is older than this value.
2885 </description>
2886 </property>
2887
2888 <property>
2889 <name>oozie.notification.proxy</name>
2890 <value></value>
2891 <description>
2892 System level proxy setting for job notifications.
2893 </description>
2894 </property>
2895
2896 <property>
2897 <name>oozie.wf.rerun.disablechild</name>
2898 <value>false</value>
2899 <description>
2900 By setting this option, workflow rerun will be disabled if parent workflow or coordinator exist and
2901 it will only rerun through parent.
2902 </description>
2903 </property>
2904
2905 <property>
2906 <name>oozie.use.system.libpath</name>
2907 <value>false</value>
2908 <description>
2909 Default value of oozie.use.system.libpath. If user haven't specified =oozie.use.system.libpath=
2910 in the job.properties and this value is true and Oozie will include sharelib jars for workflow.
2911 </description>
2912 </property>
2913
2914 <property>
2915 <name>oozie.service.PauseTransitService.callable.batch.size
2916 </name>
2917 <value>10</value>
2918 <description>
2919 This value determines the number of callable which will be batched together
2920 to be executed by a single thread.
2921 </description>
2922 </property>
2923
2924 <!-- XConfiguration -->
2925 <property>
2926 <name>oozie.configuration.substitute.depth</name>
2927 <value>20</value>
2928 <description>
2929 This value determines the depth of substitution in configurations.
2930 If set -1, No limitation on substitution.
2931 </description>
2932 </property>
2933
2934 <property>
2935 <name>oozie.service.SparkConfigurationService.spark.configurations</name>
2936 <value>*=spark-conf</value>
2937 <description>
2938 Comma separated AUTHORITY=SPARK_CONF_DIR, where AUTHORITY is the HOST:PORT of
2939 the ResourceManager of a YARN cluster. The wildcard '*' configuration is
2940 used when there is no exact match for an authority. The SPARK_CONF_DIR contains
2941 the relevant spark-defaults.conf properties file. If the path is relative is looked within
2942 the Oozie configuration directory; though the path can be absolute. This is only used
2943 when the Spark master is set to either "yarn-client" or "yarn-cluster".
2944 </description>
2945 </property>
2946
2947 <property>
2948 <name>oozie.service.SparkConfigurationService.spark.configurations.blacklist</name>
2949 <value>spark.yarn.jar,spark.yarn.jars</value>
2950 <description>
2951 Comma separated list of properties to ignore from any Spark configurations specified in
2952 oozie.service.SparkConfigurationService.spark.configurations property.
2953 </description>
2954 </property>
2955
2956 <property>
2957 <name>oozie.service.SparkConfigurationService.spark.configurations.ignore.spark.yarn.jar</name>
2958 <value>true</value>
2959 <description>
2960 Deprecated. Use oozie.service.SparkConfigurationService.spark.configurations.blacklist instead.
2961 If true, Oozie will ignore the "spark.yarn.jar" property from any Spark configurations specified in
2962 oozie.service.SparkConfigurationService.spark.configurations. If false, Oozie will not ignore it. It is recommended
2963 to leave this as true because it can interfere with the jars in the Spark sharelib.
2964 </description>
2965 </property>
2966
2967 <property>
2968 <name>oozie.email.attachment.enabled</name>
2969 <value>true</value>
2970 <description>
2971 This value determines whether to support email attachment of a file on HDFS.
2972 Set it false if there is any security concern.
2973 </description>
2974 </property>
2975
2976 <property>
2977 <name>oozie.email.smtp.host</name>
2978 <value>localhost</value>
2979 <description>
2980 The host where the email action may find the SMTP server.
2981 </description>
2982 </property>
2983
2984 <property>
2985 <name>oozie.email.smtp.port</name>
2986 <value>25</value>
2987 <description>
2988 The port to connect to for the SMTP server, for email actions.
2989 </description>
2990 </property>
2991
2992 <property>
2993 <name>oozie.email.smtp.auth</name>
2994 <value>false</value>
2995 <description>
2996 Boolean property that toggles if authentication is to be done or not when using email actions.
2997 </description>
2998 </property>
2999
3000 <property>
3001 <name>oozie.email.smtp.username</name>
3002 <value></value>
3003 <description>
3004 If authentication is enabled for email actions, the username to login as (to the SMTP server).
3005 </description>
3006 </property>
3007
3008 <property>
3009 <name>oozie.email.smtp.password</name>
3010 <value></value>
3011 <description>
3012 If authentication is enabled for email actions, the password to login with (to the SMTP server).
3013 </description>
3014 </property>
3015
3016 <property>
3017 <name>oozie.email.from.address</name>
3018 <value>oozie@localhost</value>
3019 <description>
3020 The from address to be used for mailing all emails done via the email action.
3021 </description>
3022 </property>
3023
3024 <property>
3025 <name>oozie.email.smtp.socket.timeout.ms</name>
3026 <value>10000</value>
3027 <description>
3028 The timeout to apply over all SMTP server socket operations done during the email action.
3029 </description>
3030 </property>
3031
3032 <property>
3033 <name>oozie.actions.default.name-node</name>
3034 <value> </value>
3035 <description>
3036 The default value to use for the &lt;name-node&gt; element in applicable action types. This value will be used when
3037 neither the action itself nor the global section specifies a &lt;name-node&gt;. As expected, it should be of the form
3038 "hdfs://HOST:PORT".
3039 </description>
3040 </property>
3041
3042 <property>
3043 <name>oozie.actions.default.job-tracker</name>
3044 <value> </value>
3045 <description>
3046 The default value to use for the &lt;job-tracker&gt; element in applicable action types. This value will be used when
3047 neither the action itself nor the global section specifies a &lt;job-tracker&gt;. As expected, it should be of the form
3048 "HOST:PORT".
3049 </description>
3050 </property>
3051
3052 <property>
3053 <name>oozie.actions.default.resource-manager</name>
3054 <value> </value>
3055 <description>
3056 The default value to use for the &lt;resource-manager&gt; element in applicable action types. This value will be used
3057 when neither the action itself nor the global section specifies a &lt;resource-managerr&gt;. As expected, it should
3058 be of the form "HOST:PORT". If both oozie.actions.default.job-tracker and oozie.actions.default.resource-manager are
3059 specified, oozie.actions.default.resource-manager takes precedence.
3060 </description>
3061 </property>
3062
3063 <property>
3064 <name>oozie.service.SchemaCheckerService.check.interval</name>
3065 <value>168</value>
3066 <description>
3067 This is the interval at which Oozie will check the database schema, in hours.
3068 A zero or negative value will disable the checker.
3069 </description>
3070 </property>
3071
3072 <property>
3073 <name>oozie.service.SchemaCheckerService.ignore.extras</name>
3074 <value>false</value>
3075 <description>
3076 When set to false, the schema checker will consider extra (unused) tables, columns, and indexes to be incorrect. When
3077 set to true, these will be ignored.
3078 </description>
3079 </property>
3080
3081 <property>
3082 <name>oozie.hcat.uri.regex.pattern</name>
3083 <value>([a-z]+://[\w\.\-]+:\d+[,]*)+/\w+/\w+/?[\w+=;\-]*</value>
3084 <description>Regex pattern for HCat URIs. The regex can be modified by users as per requirement
3085 for parsing/splitting the HCat URIs.</description>
3086 </property>
3087
3088 <property>
3089 <name>oozie.action.null.args.allowed</name>
3090 <value>true</value>
3091 <description>
3092 When set to true, empty arguments (like &lt;arg&gt;&lt;/arg&gt;) will be passed as "null" to the main method of a
3093 given action. That is, the args[] array will contain "null" elements. When set to false, then "nulls" are removed.
3094 </description>
3095 </property>
3096
3097 <property>
3098 <name>oozie.javax.xml.parsers.DocumentBuilderFactory</name>
3099 <value>org.apache.xerces.jaxp.DocumentBuilderFactoryImpl</value>
3100 <description>
3101 Oozie will set the javax.xml.parsers.DocumentBuilderFactory Java System Property to this value. This helps speed up
3102 XML handling because the JVM doesn't have to search for the proper class every time. An empty or whitespace value
3103 skips setting the System Property. The default implementation that Oozie uses is Xerces.
3104 Most users should not have to change this.
3105 </description>
3106 </property>
3107
3108 <property>
3109 <name>oozie.graphviz.timeout.seconds</name>
3110 <value>60</value>
3111 <description>
3112 The default number of seconds Graphviz graph generation will timeout.
3113 </description>
3114 </property>
3115
3116 <property>
3117 <name>oozie.launcher.default.vcores</name>
3118 <value>1</value>
3119 <description>
3120 The default number of vcores that are allocated for the Launcher AMs
3121 </description>
3122 </property>
3123
3124 <property>
3125 <name>oozie.launcher.default.memory.mb</name>
3126 <value>2048</value>
3127 <description>
3128 The default amount of memory in MBs that is allocated for the Launcher AMs
3129 </description>
3130 </property>
3131
3132 <property>
3133 <name>oozie.launcher.default.priority</name>
3134 <value>0</value>
3135 <description>
3136 The default YARN priority of the Launcher AM
3137 </description>
3138 </property>
3139
3140 <property>
3141 <name>oozie.launcher.default.queue</name>
3142 <value>default</value>
3143 <description>
3144 The default YARN queue where the Launcher AM is placed
3145 </description>
3146 </property>
3147
3148 <property>
3149 <name>oozie.launcher.default.max.attempts</name>
3150 <value>2</value>
3151 <description>
3152 The default YARN maximal attempt count of the Launcher AM
3153 </description>
3154 </property>
3155
3156 <property>
3157 <name>oozie.launcher.override</name>
3158 <value>true</value>
3159 <description>
3160 Whether oozie.launcher.override.* and oozie.launcher.prepend.* parameters have to be considered when submitting a YARN
3161 LauncherAM. That is, existing MapReduce v1, MapReduce v2, or YARN parameters used in the action configuration should be
3162 populated to the Application Master launcher configuration, or not. Generally, first &lt;launcher/&gt; tag specific user
3163 settings, then YARN configuration settings, then MapReduce v2, and at last, MapReduce v1 properties are copied to
3164 launcher configuration.
3165 </description>
3166 </property>
3167
3168 <property>
3169 <name>oozie.launcher.override.max.attempts</name>
3170 <value>mapreduce.map.maxattempts,mapred.map.max.attempts</value>
3171 <description>
3172 A comma separated list of MapReduce v1 and MapReduce v2 properties to override the max attempts of the MapReduce
3173 Application Master. The first one that is found will be used.
3174 </description>
3175 </property>
3176
3177 <property>
3178 <name>oozie.launcher.override.memory.mb</name>
3179 <value>yarn.app.mapreduce.am.resource.mb,mapreduce.map.memory.mb,mapred.job.map.memory.mb</value>
3180 <description>
3181 A comma separated list of MapReduce v1, MapReduce v2, and YARN properties to override the memory amount in MB of the
3182 MapReduce Application Master. The first one that is found will be used.
3183 </description>
3184 </property>
3185
3186 <property>
3187 <name>oozie.launcher.override.vcores</name>
3188 <value>yarn.app.mapreduce.am.resource.cpu-vcores,mapreduce.map.cpu.vcores</value>
3189 <description>
3190 A comma separated list of MapReduce v1, MapReduce v2, and YARN properties to override the CPU vcore count of the
3191 MapReduce Application Master. The first one that is found will be used.
3192 </description>
3193 </property>
3194
3195 <property>
3196 <name>oozie.launcher.override.log.level</name>
3197 <value>mapreduce.map.log.level,mapred.map.child.log.level</value>
3198 <description>
3199 A comma separated list of MapReduce v1, MapReduce v2, and YARN properties to override the logging level of the MapReduce
3200 Application Master. The first one that is found will be used.
3201 </description>
3202 </property>
3203
3204 <property>
3205 <name>oozie.launcher.override.javaopts</name>
3206 <value>yarn.app.mapreduce.am.command-opts,mapreduce.map.java.opts,mapred.child.java.opts</value>
3207 <description>
3208 A comma separated list of MapReduce v1, MapReduce v2, and YARN properties to override MapReduce Application Master JVM
3209 options. The first one that is found will be used.
3210 </description>
3211 </property>
3212
3213 <property>
3214 <name>oozie.launcher.prepend.javaopts</name>
3215 <value>yarn.app.mapreduce.am.admin-command-opts</value>
3216 <description>
3217 A comma separated list of YARN properties to prepend to MapReduce Application Master JVM options. The first one that is
3218 found will be prepended to the list of JVM options.
3219 </description>
3220 </property>
3221
3222 <property>
3223 <name>oozie.launcher.override.env</name>
3224 <value>yarn.app.mapreduce.am.env,mapreduce.map.env,mapred.child.env</value>
3225 <description>
3226 A comma separated list of MapReduce v1, MapReduce v2, and YARN properties to override MapReduce Application Master
3227 environment variable settings. The first one that is found will be used.
3228 </description>
3229 </property>
3230
3231 <property>
3232 <name>oozie.launcher.prepend.env</name>
3233 <value>yarn.app.mapreduce.am.admin.user.env</value>
3234 <description>
3235 A comma separated list of YARN properties to prepend to MapReduce Application Master environment settings. The first one
3236 that is found will be prepended to the list of environment settings.
3237 </description>
3238 </property>
3239
3240 <property>
3241 <name>oozie.launcher.override.priority</name>
3242 <value>mapreduce.job.priority,mapred.job.priority</value>
3243 <description>
3244 A comma separated list of MapReduce v1 and MapReduce v2 to override MapReduce Application Master job priority. The first
3245 one that is found will be used.
3246 </description>
3247 </property>
3248
3249 <property>
3250 <name>oozie.launcher.override.queue</name>
3251 <value>mapreduce.job.queuename,mapred.job.queue.name</value>
3252 <description>
3253 A comma separated list of MapReduce v1 and MapReduce v2 properties to override MapReduce Application Master job queue
3254 name. The first one that is found will be used.
3255 </description>
3256 </property>
3257
3258 <property>
3259 <name>oozie.launcher.override.view.acl</name>
3260 <value>mapreduce.job.acl-view-job</value>
3261 <description>
3262 A comma separated list of MapReduce v1 and MapReduce v2 properties to override MapReduce View ACL settings.
3263 The first one that is found will be used.
3264 </description>
3265 </property>
3266
3267 <property>
3268 <name>oozie.launcher.override.modify.acl</name>
3269 <value>mapreduce.job.acl-modify-job</value>
3270 <description>
3271 A comma separated list of MapReduce v1 and MapReduce v2 properties to override MapReduce Modify ACL settings.
3272 The first one that is found will be used.
3273 </description>
3274 </property>
3275
3276 <property>
3277 <name>oozie.action.mapreduce.needed.for.distcp</name>
3278 <value>true</value>
3279 <description>
3280 Whether to add MapReduce jars to the DistCp action's classpath's by default.
3281 </description>
3282 </property>
3283
3284 <property>
3285 <name>oozie.action.mapreduce.needed.for.hive</name>
3286 <value>true</value>
3287 <description>
3288 Whether to add MapReduce jars to the Hive action's classpath's by default.
3289 </description>
3290 </property>
3291
3292 <property>
3293 <name>oozie.action.mapreduce.needed.for.hive2</name>
3294 <value>true</value>
3295 <description>
3296 Whether to add MapReduce jars to the Hive2 action's classpath's by default.
3297 </description>
3298 </property>
3299
3300 <property>
3301 <name>oozie.action.mapreduce.needed.for.java</name>
3302 <value>true</value>
3303 <description>
3304 Whether to add MapReduce jars to the Java action's classpath's by default.
3305 </description>
3306 </property>
3307
3308 <property>
3309 <name>oozie.action.mapreduce.needed.for.map-reduce</name>
3310 <value>true</value>
3311 <description>
3312 Whether to add MapReduce jars to the Map-Reduce action's classpath's by default.
3313 </description>
3314 </property>
3315
3316 <property>
3317 <name>oozie.action.mapreduce.needed.for.pig</name>
3318 <value>true</value>
3319 <description>
3320 Whether to add MapReduce jars to the Pig action's classpath's by default.
3321 </description>
3322 </property>
3323
3324 <property>
3325 <name>oozie.action.mapreduce.needed.for.sqoop</name>
3326 <value>true</value>
3327 <description>
3328 Whether to add MapReduce jars to the Sqoop action's classpath's by default.
3329 </description>
3330 </property>
3331
3332
3333 </configuration>