Is it required custom code class or default property configuration Is
enough
On Nov 11, 2017 3:02 PM, "jbaran...@gmail.com" wrote:
>
>
> On 2017-11-11 01:24, Mohan wrote:
> > Is there any option to check source input records counts and writer
>
Is there any option to check source input records counts and writer count
using property or any other logic in Gobblin ?
You may have to check the implementation of the customer writer which seems
to be com.custom.gobblin.ParquetHDFSDataWriter. It seems to be expecting
the file being present which is not there.
On Fri, Nov 10, 2017 at 11:04 AM, Mohan wrote:
> 2017-11-10 10:57:28 IST ERROR
2017-11-10 10:57:28 IST ERROR [ForkExecutor-0] gobblin.runtime.Fork 177 -
Fork 0 of task task__1510291622475_0 failed to process data records
java.io.IOException: com.github.rholder.retry.RetryException: Retrying
failed to complete successfully after 5 attempts.
at
Complete log in my private network difficult for me to share and right now
we are using gobblin version 0.9.0
On Nov 10, 2017 9:43 AM, "Vicky Kak" wrote:
> Can you attach the complete log file and explain in brief the pull file
> configuration? The above description seems
Can you attach the complete log file and explain in brief the pull file
configuration? The above description seems to be a warning and I am not
sure where it coming from. Also please state the gobblin version you have
been using as it would become easy to look into the code.
On Fri, Nov 10, 2017
I am getting only this exception in log and in the staging directory the
file is not created . Is there any way to run gobblin in debug mode to
trace my issue?
On Nov 10, 2017 5:43 AM, "Abhishek Tiwari" wrote:
> Just check the staging location when the job runs, also check
This seems like the cause:
"java.lang.IllegalArgumentException: Staging output file
/app/gobblin/0.9.0/task-staging/data/attempt_local1524912904_0001_m_12_0/log/2017/11/06/part.task_1510232733253_0_0.parquet
does not exist"
Any idea why the file was not generated?
On 2017-11-09 07:22,