[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (86 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2619  Make  Hive action defaults to match hive defaults when running from 
command line
https://issues-test.apache.org/jira/browse/OOZIE-2619
OOZIE-2618  Include hive-common in hive-beeline as compile component for 
hive-server2 (hive2 action)
https://issues-test.apache.org/jira/browse/OOZIE-2618
OOZIE-2617  Read properties files in action configurations
https://issues-test.apache.org/jira/browse/OOZIE-2617
OOZIE-2616  Add Tez profile for Hive and Pig sharelibs
https://issues-test.apache.org/jira/browse/OOZIE-2616
OOZIE-2606  Set spark.yarn.jars to fix Spark 2.0 with Oozie
https://issues-test.apache.org/jira/browse/OOZIE-2606
OOZIE-2589  CompletedActionXCommand priority param is of no effect
https://issues-test.apache.org/jira/browse/OOZIE-2589
OOZIE-2588  Support getting credentials for same cluster hcat when credentials 
config is empty
https://issues-test.apache.org/jira/browse/OOZIE-2588
OOZIE-2585  Disable or remove test case 
TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and 
testMemoryUsageAndSpeed
https://issues-test.apache.org/jira/browse/OOZIE-2585
OOZIE-2584  Eliminate Thread.sleep() calls in TestMemoryLocks
https://issues-test.apache.org/jira/browse/OOZIE-2584
OOZIE-2583  oozie throws EL Exception when reference variable name containing 
dot
https://issues-test.apache.org/jira/browse/OOZIE-2583
OOZIE-2582  Populating external child Ids for action failures
https://issues-test.apache.org/jira/browse/OOZIE-2582
OOZIE-2573  dataset url  which contains spaces can not be handled rightly
https://issues-test.apache.org/jira/browse/OOZIE-2573
OOZIE-2572  SLA DURATION miss not shown when job is running for longer than 
expected time
https://issues-test.apache.org/jira/browse/OOZIE-2572
OOZIE-2571  Add scala.binary.version Maven property so that Scala 2.11 can be 
used
https://issues-test.apache.org/jira/browse/OOZIE-2571
OOZIE-2569  Adding yarn-site, core-site, hdfs-site and mapred-site into spark 
launcher 
https://issues-test.apache.org/jira/browse/OOZIE-2569
OOZIE-2568  SSH  action pretends to retry automaticly when it failed
https://issues-test.apache.org/jira/browse/OOZIE-2568
OOZIE-2564  Create new log4j config for unit tests so that logged messages 
contain threads
https://issues-test.apache.org/jira/browse/OOZIE-2564
OOZIE-2552  Update ActiveMQ version for security and other fixes
https://issues-test.apache.org/jira/browse/OOZIE-2552
OOZIE-2538  Update HttpClient versions to close security vulnerabilities
https://issues-test.apache.org/jira/browse/OOZIE-2538
OOZIE-2534  Versioned action libs (similar to how SharedLibs works)
https://issues-test.apache.org/jira/browse/OOZIE-2534
OOZIE-2530  Remove jline from parent and sharelib pig pom
https://issues-test.apache.org/jira/browse/OOZIE-2530
OOZIE-2528  Print out environment variables in LauncherMapper
https://issues-test.apache.org/jira/browse/OOZIE-2528
OOZIE-2521  Filter options are case sensitive for jobtye=bundle
https://issues-test.apache.org/jira/browse/OOZIE-2521
OOZIE-2518  Oozie is creating many files and directories in /tmp per day
https://issues-test.apache.org/jira/browse/OOZIE-2518
OOZIE-2517  Add support for startCreatedTime and endCreatedTime filters for 
coord and bundles
https://issues-test.apache.org/jira/browse/OOZIE-2517
OOZIE-2513  log.scan.duration should not be used for error and audit logs
https://issues-test.apache.org/jira/browse/OOZIE-2513
OOZIE-2512  ShareLibservice returns incorrect path for jar
https://issues-test.apache.org/jira/browse/OOZIE-2512
OOZIE-2508  Documentation change for Coord action rerun [OOZIE-1735]
https://issues-test.apache.org/jira/browse/OOZIE-2508
OOZIE-2501  ZK reentrant lock doesn't work for few cases
https://issues-test.apache.org/jira/browse/OOZIE-2501
OOZIE-2500  -DtestJarSimple option mentioned in minioozie doc does not work
https://issues-test.apache.org/jira/browse/OOZIE-2500
OOZIE-2499  map-reduce launcher does not need distributed files, archives 
except  jar of input/outputformat class
https://issues-test.apache.org/jira/browse/OOZIE-2499
OOZIE-2498  Oozie CallerId configuration for downstream components 
https://issues-test.apache.org/jira/browse/OOZIE-2498
OOZIE-2495  change action status from  ErrorType.NON_TRANSIENT to TRANSIENT 
when SSH action occurs AUTH_FAILED occasionally
https://issues-test.apache.org/jira/browse/OOZIE-2495
OOZIE-2491  oozie acl cannot specify group,it does`t work
https://issues-test.apache.org/jira/browse/OOZIE-2491

[jira] [Updated] (OOZIE-2702) OYA: Remove System.out.println() calls and replace them with Loggers

[Andras Piros (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andras Piros updated OOZIE-2702:

Description: 
Currently there are a lot of {{System.out.println()}} calls in the code, mostly 
in the {{sharelib}}.

This solution is inferior to using a logger library, where we can fine-tune a 
lot of different things. It's desirable that we migrate these calls to Log4j.

The preferred solution would be to use {{log4j}} {{Logger}} in our code, 
redirected per default to the console using {{ConsoleAppender}}. That way we 
wouldn't be breaking compatibility, but some of the users could redirect to 
another {{Appender}} s.

  was:
Currently there are a lot of {{System.out.println()}} calls in the code, mostly 
in the sharelib.

This solution is inferior to using a logger library, where we can fine-tune a 
lot of different things. It's desirable that we migrate these calls to Log4j.


> OYA: Remove System.out.println() calls and replace them with Loggers
> 
>
> Key: OOZIE-2702
> URL: https://issues.apache.org/jira/browse/OOZIE-2702
> Project: Oozie
>  Issue Type: Sub-task
>Reporter: Peter Bacsko
>
> Currently there are a lot of {{System.out.println()}} calls in the code, 
> mostly in the {{sharelib}}.
> This solution is inferior to using a logger library, where we can fine-tune a 
> lot of different things. It's desirable that we migrate these calls to Log4j.
> The preferred solution would be to use {{log4j}} {{Logger}} in our code, 
> redirected per default to the console using {{ConsoleAppender}}. That way we 
> wouldn't be breaking compatibility, but some of the users could redirect to 
> another {{Appender}} s.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-1770) Create Oozie Application Master for YARN

[Andras Piros (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849266#comment-15849266
 ] 

Andras Piros commented on OOZIE-1770:
-

Things to cover from Yahoo! meeting:
* modify code: rename {{ApplicationType}} {{Oozie Launcher}} to {{OOZIE}}
* modify JIRA: add to OOZIE-1770: benchmark results link: between regular MR, 
Uber mode MR, and OYA for workflows w/ different action types
* check: look for YARN {{ApplicationHistoryServer}} usage, whether it has 
changed from {{ApplicationTimelineServer}} and whether OOZIE-1770 changes that
* check: whether {{Credentials}} are passed correctly within 
{{JavaActionExecutor.setCredentialTokens()}}
* check: re-test that property {{launcher.lib.*}} still works
* check: that for MapReduce actions {{LauncherAM}} exits prematurely in 
circumstances where {{LauncherMapper}} did (preserve original behavior)
* check: whether generated {{launcher.xml}} file content is printed out w/ the 
launcher output

> Create Oozie Application Master for YARN
> 
>
> Key: OOZIE-1770
> URL: https://issues.apache.org/jira/browse/OOZIE-1770
> Project: Oozie
>  Issue Type: New Feature
>Reporter: Bowen Zhang
>Assignee: Peter Cseh
> Attachments: OOZIE-1770-001.patch, OOZIE-1770-002.patch, 
> OOZIE-1770-003.patch, OOZIE-1770-004.patch, OOZIE-1770-005.patch, 
> OOZIE-1770-006.patch, OOZIE-1770-007.patch, OOZIE-1770-008.patch, 
> OOZIE-1770-009.patch, OozieYarnAM.pdf, oya.patch, oya-rm-screenshot.jpg, OYA 
> Scoping Doc 001.pdf, Prelim OYA Scoping Doc 001.pdf, Prelim OYA Scoping Doc 
> 002.pdf, Prelim OYA Scoping Doc 003.pdf
>
>
> After the first release of oozie on hadoop 2, it will be good if users can 
> set execution engine in oozie conf, be it YARN AM or traditional MR. We can 
> target this for post oozie 4.1 release.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OOZIE-2004) Improve Oozie version info output

[Robert Kanter (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Kanter updated OOZIE-2004:
-
Fix Version/s: 5.0.0

This seems like a good thing for Oozie 5

> Improve Oozie version info output
> -
>
> Key: OOZIE-2004
> URL: https://issues.apache.org/jira/browse/OOZIE-2004
> Project: Oozie
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 4.0.1
>Reporter: Chunjun Xiao
>Priority: Minor
> Fix For: 5.0.0
>
>
> Current oozie version info output is quite simple:
> {code}
> [root@svm5 ~] # oozie version
> Oozie client build version: 4.0.1
> [root@svm5 ~] #
> {code}
> Can we improve it to follow the convention of  Hadoop/HBase, as:
> {code}
> [root@svm5 ~] # oozie version
> Oozie 4.0.1
> Source code repository: ssh://git@XXX/oozie.git -r 
> 3171cb656a4e4c1b2c1e9c6a47abed7df5bbcc8d
> Compiled by root on Sun Jul  6 04:38:08 PDT 2014
> From source with checksum XXX
> [root@svm5 ~] #
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2645) Drop Instrumentation in favor of Metrics

[Robert Kanter (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849230#comment-15849230
 ] 

Robert Kanter commented on OOZIE-2645:
--

We might have to deprecate Instrumentation and make Metrics the default for 
Oozie 5, and then we can drop it and clean up for Oozie 6.

> Drop Instrumentation in favor of Metrics
> 
>
> Key: OOZIE-2645
> URL: https://issues.apache.org/jira/browse/OOZIE-2645
> Project: Oozie
>  Issue Type: Improvement
>  Components: monitoring
>Affects Versions: 5.0.0
>Reporter: Robert Kanter
>Assignee: Andras Piros
>Priority: Blocker
> Fix For: 5.0.0
>
>
> OOZIE-1817 added the option to use DropWizard Metrics instead of our 
> homegrown Instrumentation.  We left the Instrumentation as the default for 
> compatibility; in Oozie 5, we should drop Instrumentation and only have 
> Metrics.
> We can also use this opportunity to clean up the code and interface for 
> Metrics, which currently has to conform to Instrumentation for pluggability.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (OOZIE-2734) Switch docs from twiki to markdown

[Andras Piros (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849130#comment-15849130
 ] 

Andras Piros edited comment on OOZIE-2734 at 2/1/17 11:48 PM:
--

Look also at:
* Apache Drill, HBase, Spark documentation, how these are generated
* Jekyll
* AsciiDocs


was (Author: andras.piros):
Look also at:
* Apache Drill
* Jekyll
* AsciiDocs

> Switch docs from twiki to markdown
> --
>
> Key: OOZIE-2734
> URL: https://issues.apache.org/jira/browse/OOZIE-2734
> Project: Oozie
>  Issue Type: Improvement
>  Components: docs
>Affects Versions: trunk
>Reporter: Robert Kanter
>
> This won't be a fun JIRA, but it would be great if we could switch to 
> something easier to work with and better supported like markdown, and get rid 
> of the super old twiki we're using for docs.
> I found two tools that I haven't tried out that claim to be able to convert 
> this for us:
> # http://pandoc.org/
> # https://github.com/jcodagnone/twiki2markdown
> The former supports a lot of different formats, and according to [this blog 
> post|http://goer.org/Journal/2013/02/converting_twiki_foswiki_to_markdown_restructuredtext.html]
>  it's better to convert from the rendered html instead of the twiki.  But who 
> knows which is better, or if the second tool is better than either.
> I think once we switch to a better format, it will be easier to keep the docs 
> in better shape, as they could really use some reorganizing.  Though we can 
> keep that for a separate task.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown

[Andras Piros (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849130#comment-15849130
 ] 

Andras Piros commented on OOZIE-2734:
-

Look also at:
* Apache Drill
* Jekyll
* AsciiDocs

> Switch docs from twiki to markdown
> --
>
> Key: OOZIE-2734
> URL: https://issues.apache.org/jira/browse/OOZIE-2734
> Project: Oozie
>  Issue Type: Improvement
>  Components: docs
>Affects Versions: trunk
>Reporter: Robert Kanter
>
> This won't be a fun JIRA, but it would be great if we could switch to 
> something easier to work with and better supported like markdown, and get rid 
> of the super old twiki we're using for docs.
> I found two tools that I haven't tried out that claim to be able to convert 
> this for us:
> # http://pandoc.org/
> # https://github.com/jcodagnone/twiki2markdown
> The former supports a lot of different formats, and according to [this blog 
> post|http://goer.org/Journal/2013/02/converting_twiki_foswiki_to_markdown_restructuredtext.html]
>  it's better to convert from the rendered html instead of the twiki.  But who 
> knows which is better, or if the second tool is better than either.
> I think once we switch to a better format, it will be easier to keep the docs 
> in better shape, as they could really use some reorganizing.  Though we can 
> keep that for a separate task.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2231) Upgrade curator to latest version 2.11.0

[Robert Kanter (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849021#comment-15849021
 ] 

Robert Kanter commented on OOZIE-2231:
--

It might make sense to wait for Curator 2.12.0, which will have CURATOR-200.  
That might help us with the guava issues.

> Upgrade curator to latest version 2.11.0
> 
>
> Key: OOZIE-2231
> URL: https://issues.apache.org/jira/browse/OOZIE-2231
> Project: Oozie
>  Issue Type: Bug
>  Components: HA
>Reporter: Purshotam Shah
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 5.0.0
>
> Attachments: OOZIE-2231-00.patch, OOZIE-2231-01.patch, 
> OOZIE-2231-02.patch, OOZIE-2231-02.patch, OOZIE-2231-03.patch
>
>
> It have some fix related to InterProcessReadWriteLock, ChildReaper, 
> LeaderSelector which we use.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Jenkins build is back to normal : oozie-trunk-find-patches-available #148568

[Apache Jenkins Server]

See 

[jira] [Commented] (OOZIE-2777) Config-default.xml longer than 64k results in java.io.UTFDataFormatException

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848664#comment-15848664
 ] 

Peter Cseh commented on OOZIE-2777:
---

[~rohini], {{patch}} and {{git diff --binary}} handles binary files different. 
Try using {{git apply}} instead of patch.
See OOZIE-2532 for some more details.

> Config-default.xml longer than 64k results in  java.io.UTFDataFormatException
> -
>
> Key: OOZIE-2777
> URL: https://issues.apache.org/jira/browse/OOZIE-2777
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2777-10.patch, OOZIE-2777-11.patch, 
> OOZIE-2777-12.patch, OOZIE-2777-13.patch, OOZIE-2777-14.patch, 
> OOZIE-2777-1.patch, OOZIE-2777-2.patch, OOZIE-2777-3.patch, 
> OOZIE-2777-4.patch, OOZIE-2777-5.patch, OOZIE-2777-7.patch, 
> OOZIE-2777-8.patch, OOZIE-2777-9.patch
>
>
> OOZIE-1642 introduced a workaround for DataOutputStream's 64k limit for 
> Strings.
> We've encountered the same error when a config-default.xml is larger than the 
> limit.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Build failed in Jenkins: oozie-trunk-find-patches-available #148567

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 0299e5db4f0ab90146b4dbd016d652355d830717 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 0299e5db4f0ab90146b4dbd016d652355d830717
 > git rev-list 0299e5db4f0ab90146b4dbd016d652355d830717 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson4295003269395593776.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed

  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
curl: (52) Empty reply from server
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

Re: Review Request 56158: [OOZIE-2630] Amend patch for OOZIE-2630

[Satish Saley]

> On Feb. 1, 2017, 1:02 a.m., Purshotam Shah wrote:
> > core/src/main/java/org/apache/oozie/command/coord/CoordCommandUtils.java, 
> > line 410
> > 
> >
> > End of functions calculation should not include initial instance 
> > calculation.
> > It's purely on nominal time. Endof functions at dataset frequency and 
> > at datasets instance should return the same value.

I am using dataset initial instance to get the hour:minute of it. Otherwise we 
might end up with the extra instances if nominal time  is not in phase with the 
dataset time. 
Consider a dataset with initial instance - 


...
${coord:endOfDays(0)}
${coord:current(0)}

And nominal time of 2009-08-20T18:00Z. The instances should start anytime after 
(endOfDays(0)), 2009-08-20T00:00Z. But without above adjustment, it calculates 
one instance from previous day 2009-08-19. 

To solve this problem
1. Either, we have to ask users to make their timings in phase to avoid extra 
instance. In this case, we don't need amend patch.
2. Or, we can look at dataset initial instance hour:minute, and adjust the time.


- Satish


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56158/#review163796
---


On Feb. 1, 2017, 12:44 a.m., Satish Saley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/56158/
> ---
> 
> (Updated Feb. 1, 2017, 12:44 a.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2630
> https://issues.apache.org/jira/browse/OOZIE-2630
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> [OOZIE-2630] Amend patch for OOZIE-2630
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/command/coord/CoordCommandUtils.java 
> 3a7a930 
>   core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java bc18f4d 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordCommandUtils.java 
> 22d1f61 
>   core/src/test/resources/coord-dataset-endOfDays.xml 6aa3f00 
>   core/src/test/resources/coord-dataset-endOfMonths.xml 0ea5cac 
>   core/src/test/resources/coord-dataset-endOfWeeks.xml 7879bf4 
> 
> Diff: https://reviews.apache.org/r/56158/diff/
> 
> 
> Testing
> ---
> 
> Tested locally
> 
> 
> Thanks,
> 
> Satish Saley
> 
>

[jira] [Commented] (OOZIE-2777) Config-default.xml longer than 64k results in java.io.UTFDataFormatException

[Rohini Palaniswamy (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848531#comment-15848531
 ] 

Rohini Palaniswamy commented on OOZIE-2777:
---

[~gezapeti],
  Was trying to commit it. But ran into issues. Patch creates a b folder and 
also the binary file is not being applied. Tried to manually create the binary 
file, but TestLiteWorkflowApp test still failed. Have not got the time to look 
into it more today. Can you look into it and fix it?

> Config-default.xml longer than 64k results in  java.io.UTFDataFormatException
> -
>
> Key: OOZIE-2777
> URL: https://issues.apache.org/jira/browse/OOZIE-2777
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2777-10.patch, OOZIE-2777-11.patch, 
> OOZIE-2777-12.patch, OOZIE-2777-13.patch, OOZIE-2777-14.patch, 
> OOZIE-2777-1.patch, OOZIE-2777-2.patch, OOZIE-2777-3.patch, 
> OOZIE-2777-4.patch, OOZIE-2777-5.patch, OOZIE-2777-7.patch, 
> OOZIE-2777-8.patch, OOZIE-2777-9.patch
>
>
> OOZIE-1642 introduced a workaround for DataOutputStream's 64k limit for 
> Strings.
> We've encountered the same error when a config-default.xml is larger than the 
> limit.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2630) Oozie Coordinator EL Functions to get first day of the week/month

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848231#comment-15848231
 ] 

Hadoop QA commented on OOZIE-2630:
--

Testing JIRA OOZIE-2630

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 4 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:red}-1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:red}-1{color} patch does not compile
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in 
[hadooplibs/hadoop-utils-2].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [sharelib/streaming].
.{color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{color:green}+1{color} There are no new bugs found in [sharelib/pig].
.{color:green}+1{color} There are no new bugs found in [sharelib/spark].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1864
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3609/

> Oozie Coordinator EL Functions to get first day of the week/month
> -
>
> Key: OOZIE-2630
> URL: https://issues.apache.org/jira/browse/OOZIE-2630
> Project: Oozie
>  Issue Type: New Feature
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Fix For: 5.0.0
>
> Attachments: OOZIE-2630-10.patch, OOZIE-2630-1.patch, 
> OOZIE-2630-2.patch, OOZIE-2630-3.patch, OOZIE-2630-4.patch, 
> OOZIE-2630-5.patch, OOZIE-2630-6.patch, OOZIE-2630-7.patch, 
> OOZIE-2630-8.patch, OOZIE-2630-9.patch, OOZIE-2630-amend-1.patch, 
> OOZIE-2630-amend-2.patch, OOZIE-2630-amend-3.patch
>
>
> Some users are demanding functions to give first day of week and first day of 
> month. It would help them in aggregation jobs accumulating data from first 
> day of the month/week to the intended date (current date). Currently we have 
> no way to define such start-instance with any existing EL function.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Build failed in Jenkins: oozie-trunk-precommit-build #3609

[Apache Jenkins Server]

See 

--
[...truncated 14752 lines...]
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/SqoopActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/Hive2Credentials.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/HCatCredentialHelper.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/LauncherMapperHelper.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/Credentials.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/ShellActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/ScriptLanguageActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/PigActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/HCatCredentials.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/JavaActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/CredentialException.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/FsELFunctions.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/DistcpActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/HadoopELFunctions.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/CredentialsProperties.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/MapReduceActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/CredentialsProvider.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/HbaseCredentials.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/FsActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/Hive2ActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/SparkActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/HiveActionExecutor.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/hadoop/OozieJobInfo.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/action/ActionExecutor.Context.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/CoordinatorEngine.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/jms/MessageReceiver.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/jms/DefaultConnectionContext.html
 longer than 100 characters.
[WARNING] Entry: 

Re: Review Request 55879: OOZIE-2777 Config-default.xml longer than 64k results in java.io.UTFDataFormatException

[Peter Bacsko]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55879/#review163799
---


Ship it!




Ship It!

- Peter Bacsko


On jan. 31, 2017, 2:10 du, Peter Cseh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/55879/
> ---
> 
> (Updated jan. 31, 2017, 2:10 du)
> 
> 
> Review request for oozie.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Config-default.xml longer than 64k results in java.io.UTFDataFormatException  
> https://issues.apache.org/jira/browse/OOZIE-2777
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/util/StringSerializationUtil.java 
> PRE-CREATION 
>   core/src/main/java/org/apache/oozie/workflow/lite/LiteWorkflowApp.java 
> a06595d3b2b99dbe33ef5d55208435aaec151e1a 
>   core/src/main/java/org/apache/oozie/workflow/lite/LiteWorkflowInstance.java 
> 2b13e6701226b7236d101d738aba6b6ebbabf4e5 
>   core/src/main/java/org/apache/oozie/workflow/lite/NodeDef.java 
> 496b0086f840c0c6fc60a74bdb3dc382c4db2612 
>   core/src/test/java/org/apache/oozie/command/wf/TestSubmitXCommand.java 
> 47ff8ca2751926bb728ea3eba5d7fe11282c3176 
>   core/src/test/java/org/apache/oozie/util/TestStringSerializationUtil.java 
> PRE-CREATION 
>   core/src/test/java/org/apache/oozie/workflow/lite/TestLiteWorkflowApp.java 
> PRE-CREATION 
>   core/src/test/resources/oldWorkFlowApp.serialized PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/55879/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Peter Cseh
> 
>

[jira] [Commented] (OOZIE-2777) Config-default.xml longer than 64k results in java.io.UTFDataFormatException

[Peter Cseh (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848209#comment-15848209
 ] 

Peter Cseh commented on OOZIE-2777:
---

Yes, we've agreed on keeping the randomized tests.

> Config-default.xml longer than 64k results in  java.io.UTFDataFormatException
> -
>
> Key: OOZIE-2777
> URL: https://issues.apache.org/jira/browse/OOZIE-2777
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2777-10.patch, OOZIE-2777-11.patch, 
> OOZIE-2777-12.patch, OOZIE-2777-13.patch, OOZIE-2777-14.patch, 
> OOZIE-2777-1.patch, OOZIE-2777-2.patch, OOZIE-2777-3.patch, 
> OOZIE-2777-4.patch, OOZIE-2777-5.patch, OOZIE-2777-7.patch, 
> OOZIE-2777-8.patch, OOZIE-2777-9.patch
>
>
> OOZIE-1642 introduced a workaround for DataOutputStream's 64k limit for 
> Strings.
> We've encountered the same error when a config-default.xml is larger than the 
> limit.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Build failed in Jenkins: oozie-trunk-precommit-build #3608

[Apache Jenkins Server]

See 

Changes:

[puru] amend OOZIE-2770 Show missing dependencies for coord actions

--
[...truncated 14676 lines...]
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/store/WorkflowStore.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/store/StoreException.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/store/OozieSchema.OozieIndex.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/sla/SLACalculator.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/sla/SLACalculatorMemory.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/sla/SLAXCommandFactory.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/sla/service/SLAService.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/sla/listener/SLAJobEventListener.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/sla/listener/SLAEventListener.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/sla/listener/SLAEmailEventListener.EmailField.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/sla/listener/SLAEmailEventListener.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/sla/SLACalcStatus.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/sla/SLASummaryBean.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/sla/SLAOperations.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/sla/SLARegistrationBean.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/sla/SLACalculatorMemory.HistoryPurgeWorker.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/CoordinatorJobInfo.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/CoordinatorActionInfo.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/CoordinatorEngine.FILTER_COMPARATORS.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/BinaryBlob.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/BundleJobInfo.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/CoordinatorEngine.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/BulkResponseInfo.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/BaseEngine.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/lock/LockToken.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/lock/MemoryLocks.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/core/apidocs/src-html/org/apache/oozie/StringBlob.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/console/sla/css/images/ui-icons_22_256x240.png
 longer than 100 characters.
[WARNING] Entry: 

[jira] [Commented] (OOZIE-2630) Oozie Coordinator EL Functions to get first day of the week/month

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848201#comment-15848201
 ] 

Hadoop QA commented on OOZIE-2630:
--

Testing JIRA OOZIE-2630

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 4 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [server].
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive].
.{color:green}+1{color} There are no new bugs found in [sharelib/spark].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/hive2].
.{color:green}+1{color} There are no new bugs found in [sharelib/streaming].
.{color:green}+1{color} There are no new bugs found in [sharelib/pig].
.{color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{color:green}+1{color} There are no new bugs found in 
[hadooplibs/hadoop-utils-2].
.{color:green}+1{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [examples].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1864
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  
testRetryConsoleUrl(org.apache.oozie.command.wf.TestWorkflowActionRetryInfoXCommand)

.Tests failing with errors:
.  

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3608/

> Oozie Coordinator EL Functions to get first day of the week/month
> -
>
> Key: OOZIE-2630
> URL: https://issues.apache.org/jira/browse/OOZIE-2630
> Project: Oozie
>  Issue Type: New Feature
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Fix For: 5.0.0
>
> Attachments: OOZIE-2630-10.patch, OOZIE-2630-1.patch, 
> OOZIE-2630-2.patch, OOZIE-2630-3.patch, OOZIE-2630-4.patch, 
> OOZIE-2630-5.patch, OOZIE-2630-6.patch, OOZIE-2630-7.patch, 
> OOZIE-2630-8.patch, OOZIE-2630-9.patch, OOZIE-2630-amend-1.patch, 
> OOZIE-2630-amend-2.patch, OOZIE-2630-amend-3.patch
>
>
> Some users are demanding functions to give first day of week and first day of 
> month. It would help them in aggregation jobs accumulating data from first 
> day of the month/week to the intended date (current date). Currently we have 
> no way to define such start-instance with any existing EL function.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 56158: [OOZIE-2630] Amend patch for OOZIE-2630

[Purshotam Shah]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56158/#review163796
---




core/src/main/java/org/apache/oozie/command/coord/CoordCommandUtils.java (line 
384)


End of functions calculation should not include initial instance 
calculation.
It's purely on nominal time. Endof functions at dataset frequency and at 
datasets instance should return the same value.


- Purshotam Shah


On Feb. 1, 2017, 8:44 a.m., Satish Saley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/56158/
> ---
> 
> (Updated Feb. 1, 2017, 8:44 a.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2630
> https://issues.apache.org/jira/browse/OOZIE-2630
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> [OOZIE-2630] Amend patch for OOZIE-2630
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/command/coord/CoordCommandUtils.java 
> 3a7a930 
>   core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java bc18f4d 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordCommandUtils.java 
> 22d1f61 
>   core/src/test/resources/coord-dataset-endOfDays.xml 6aa3f00 
>   core/src/test/resources/coord-dataset-endOfMonths.xml 0ea5cac 
>   core/src/test/resources/coord-dataset-endOfWeeks.xml 7879bf4 
> 
> Diff: https://reviews.apache.org/r/56158/diff/
> 
> 
> Testing
> ---
> 
> Tested locally
> 
> 
> Thanks,
> 
> Satish Saley
> 
>

Re: Review Request 56158: [OOZIE-2630] Amend patch for OOZIE-2630

[Satish Saley]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56158/
---

(Updated Feb. 1, 2017, 12:44 a.m.)


Review request for oozie.


Bugs: OOZIE-2630
https://issues.apache.org/jira/browse/OOZIE-2630


Repository: oozie-git


Description
---

[OOZIE-2630] Amend patch for OOZIE-2630


Diffs (updated)
-

  core/src/main/java/org/apache/oozie/command/coord/CoordCommandUtils.java 
3a7a930 
  core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java bc18f4d 
  core/src/test/java/org/apache/oozie/command/coord/TestCoordCommandUtils.java 
22d1f61 
  core/src/test/resources/coord-dataset-endOfDays.xml 6aa3f00 
  core/src/test/resources/coord-dataset-endOfMonths.xml 0ea5cac 
  core/src/test/resources/coord-dataset-endOfWeeks.xml 7879bf4 

Diff: https://reviews.apache.org/r/56158/diff/


Testing
---

Tested locally


Thanks,

Satish Saley

[jira] [Updated] (OOZIE-2630) Oozie Coordinator EL Functions to get first day of the week/month

[Satish Subhashrao Saley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Satish Subhashrao Saley updated OOZIE-2630:
---
Attachment: OOZIE-2630-amend-3.patch

> Oozie Coordinator EL Functions to get first day of the week/month
> -
>
> Key: OOZIE-2630
> URL: https://issues.apache.org/jira/browse/OOZIE-2630
> Project: Oozie
>  Issue Type: New Feature
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Fix For: 5.0.0
>
> Attachments: OOZIE-2630-10.patch, OOZIE-2630-1.patch, 
> OOZIE-2630-2.patch, OOZIE-2630-3.patch, OOZIE-2630-4.patch, 
> OOZIE-2630-5.patch, OOZIE-2630-6.patch, OOZIE-2630-7.patch, 
> OOZIE-2630-8.patch, OOZIE-2630-9.patch, OOZIE-2630-amend-1.patch, 
> OOZIE-2630-amend-2.patch, OOZIE-2630-amend-3.patch
>
>
> Some users are demanding functions to give first day of week and first day of 
> month. It would help them in aggregation jobs accumulating data from first 
> day of the month/week to the intended date (current date). Currently we have 
> no way to define such start-instance with any existing EL function.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 56158: [OOZIE-2630] Amend patch for OOZIE-2630

[Satish Saley]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56158/
---

(Updated Feb. 1, 2017, 12:12 a.m.)


Review request for oozie.


Bugs: OOZIE-2630
https://issues.apache.org/jira/browse/OOZIE-2630


Repository: oozie-git


Description
---

[OOZIE-2630] Amend patch for OOZIE-2630


Diffs (updated)
-

  core/src/main/java/org/apache/oozie/command/coord/CoordCommandUtils.java 
3a7a930 
  core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java bc18f4d 
  core/src/test/java/org/apache/oozie/command/coord/TestCoordCommandUtils.java 
22d1f61 
  core/src/test/resources/coord-dataset-endOfDays.xml 6aa3f00 
  core/src/test/resources/coord-dataset-endOfMonths.xml 0ea5cac 
  core/src/test/resources/coord-dataset-endOfWeeks.xml 7879bf4 

Diff: https://reviews.apache.org/r/56158/diff/


Testing
---

Tested locally


Thanks,

Satish Saley

[jira] [Updated] (OOZIE-2630) Oozie Coordinator EL Functions to get first day of the week/month

[Satish Subhashrao Saley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OOZIE-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Satish Subhashrao Saley updated OOZIE-2630:
---
Attachment: OOZIE-2630-amend-2.patch

> Oozie Coordinator EL Functions to get first day of the week/month
> -
>
> Key: OOZIE-2630
> URL: https://issues.apache.org/jira/browse/OOZIE-2630
> Project: Oozie
>  Issue Type: New Feature
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Fix For: 5.0.0
>
> Attachments: OOZIE-2630-10.patch, OOZIE-2630-1.patch, 
> OOZIE-2630-2.patch, OOZIE-2630-3.patch, OOZIE-2630-4.patch, 
> OOZIE-2630-5.patch, OOZIE-2630-6.patch, OOZIE-2630-7.patch, 
> OOZIE-2630-8.patch, OOZIE-2630-9.patch, OOZIE-2630-amend-1.patch, 
> OOZIE-2630-amend-2.patch
>
>
> Some users are demanding functions to give first day of week and first day of 
> month. It would help them in aggregation jobs accumulating data from first 
> day of the month/week to the intended date (current date). Currently we have 
> no way to define such start-instance with any existing EL function.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2770) Show missing dependencies for coord actions

[Purshotam Shah (JIRA)]

[ 
https://issues.apache.org/jira/browse/OOZIE-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848106#comment-15848106
 ] 

Purshotam Shah commented on OOZIE-2770:
---

Thanks Satish. Committed to trunk.

> Show missing dependencies for coord actions
> ---
>
> Key: OOZIE-2770
> URL: https://issues.apache.org/jira/browse/OOZIE-2770
> Project: Oozie
>  Issue Type: Bug
>Reporter: Purshotam Shah
>Assignee: Purshotam Shah
> Fix For: trunk
>
> Attachments: amend-OOZIE-2770-V1.patch, DG_CommandLineTool.html, 
> OOZIE-2770-V1.patch, OOZIE-2770-V2.patch, OOZIE-2770-V4.patch, 
> OOZIE-2770-V5.patch, OOZIE-2770-V6.patch, OOZIE-2770-V7.patch, 
> OOZIE-2770-V8.patch, UI.png
>
>
> {code}
> $oozie job   -oozie http://localhost:11000/oozie -missingDependencies 
> 002-170106125510433-oozie-puru-C@6
> CoordAction : 6
> Blocked on   : 
> hdfs://localhost:9000/user/purushah/examples/input-data/rawLogs/2010/01/01/06/00/_SUCCESS
> DataSet: input-1
> Pending Dependencies : 
> 
> hdfs://localhost:9000/user/purushah/examples/input-data/rawLogs/2010/01/01/06/00/_SUCCESS
> 
> hdfs://localhost:9000/user/purushah/examples/input-data/rawLogs/2010/01/01/05/40/_SUCCESS
> 
> hdfs://localhost:9000/user/purushah/examples/input-data/rawLogs/2010/01/01/05/20/_SUCCESS
> Blocked on : input-2
> Pending Dependencies : 
> 
> hdfs://localhost:9000/user/purushah/examples/input-data/rawLogs/2010/01/01/06/00/_SUCCESS
> 
> hdfs://localhost:9000/user/purushah/examples/input-data/rawLogs/2010/01/01/05/40/_SUCCESS
> 
> hdfs://localhost:9000/user/purushah/examples/input-data/rawLogs/2010/01/01/05/20/_SUCCESS
> $ 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)