Hi Omkar,
I think it's only possible to get that exception with Samza 1.0. Can
you verify that the deployment is indeed using samza 0.14.1?
Thanks,
Prateek
On Wed, Jan 2, 2019 at 11:40 PM Deshpande, Omkar
wrote:
>
> Hello,
>
> I have been able to execute my Samza-Beam application in Local
Hello, samza folks.
As stated earlier in 2018, all git repositories must be migrated from
the git-wip-us.apache.org URL to gitbox.apache.org, as the old service
is being decommissioned. Your project is receiving this email because
you still have repositories on git-wip-us that needs to be
Hey Prateek,
Thank you for the quick response. There was a samaza-api.1.0.0.jar on the class
path. I have replaced it with 0.14.1.
And now I getting following exception -
org.apache.samza.config.ConfigException: No task class defined in the
configuration.
at
As Prateek mentioned, I also double checked the exception, which comes from
a class (ApplicationUtil.java) that only exists in Samza 1.0. Please remove
any Samza 1.0 dependency since Beam api currently works with Samza 0.14.1.
Your config looks mostly correct to me. The following is not needed:
Add Omkar email back to this email list.
For your later error, I think you need to add the following config as you
are using standalone:
app.runner.class=org.apache.samza.runtime.LocalApplicationRunner
Please keep us updated if you run into any further issues.
Thanks,
Xinyu
On Thu, Jan 3,
Hello Xinyu,
After adding this property, the beam pipeline is not getting triggered.
Here are the logs -
https://intuit.app.box.com/s/82cjpw9zabkcrhr1rfdg8mn8hc3zif89
This might be the relevant log snippet -
Jan 03, 2019 5:09:46 PM org.apache.samza.zk.ZkJobCoordinator
It’s working after adding
task.name.grouper.factory=org.apache.samza.container.grouper.task.GroupByContainerIdsFactory
Thanks a lot for your help.
Here is my working configuration –
app.name=test-app
app.runner.class=org.apache.samza.runtime.LocalApplicationRunner
