Thanks for discovering that ... it is a regression that we'll fix in the next release.
~Burn On Wed, Mar 30, 2016 at 3:41 AM, reshu.agarwal <[email protected]> wrote: > Hi, > > Log file have no exceptions or errors. > > I have found the issue. My CR was skipping some of the documents in > hasNext() to some in-valid documents due to this total no of documents are > not equals to count of processed document. > > In DUCC 1.x, Job got completed with status " Premature" in this same case. > > After removing the code from hasNext() and making equal both counts, Job > got completed successfully. > > Reshu. > > > On 03/26/2016 02:27 PM, Lou DeGenaro wrote: > >> Does the job's JD log file have any exceptions or errors? >> >> Lou. >> >> On Fri, Mar 25, 2016 at 2:49 AM, reshu.agarwal <[email protected]> >> wrote: >> >> Hi, >>> >>> I am facing a problem in DUCC 2.0.1 i.e. job is not completing even after >>> CR hasNext() returned false. I had tested my job with >>> "all_in_one=local/remote" both. It was successfully completed. But, in >>> running cluster environment, It failed to stopped and it was continuously >>> going to hasNext() even after returning false from it. >>> >>> Need Help. Thanks in advance. >>> >>> Reshu. >>> >>> >
