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
org.apache.samza.task.TaskFactoryUtil.lambda$fromTaskClassConfig$1(TaskFactoryUtil.java:68)
at
org.apache.samza.util.ScalaJavaUtil$$anon$2.apply(ScalaJavaUtil.scala:59)
at scala.Option.getOrElse(Option.scala:121)
at
org.apache.samza.task.TaskFactoryUtil.fromTaskClassConfig(TaskFactoryUtil.java:66)
at
org.apache.samza.task.TaskFactoryUtil.createTaskFactory(TaskFactoryUtil.java:52)
at
org.apache.samza.runtime.LocalContainerRunner.run(LocalContainerRunner.java:74)
at
org.apache.samza.runtime.LocalContainerRunner.main(LocalContainerRunner.java:148)
Here is a list of jars on the class path -
https://intuit.box.com/s/jvagxscc4y783p0pdz4mn6ddc8mcdb2x
Regards,
Omkar Deshpande
On 1/3/19, 10:03 AM, "Prateek Maheshwari" <[email protected]> wrote:
This email is from an external sender.
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
<[email protected]> wrote:
>
> Hello,
>
> I have been able to execute my Samza-Beam application in Local mode. And
now I am trying to run a Samza-Beam application in Standalone mode.
>
> Here is my configFile config.properties:
>
> app.name=test-app
> job.coordinator.factory=org.apache.samza.zk.ZkJobCoordinatorFactory
> job.coordinator.zk.connect=localhost:2181
> job.coordinator.system=kafka
> job.factory.class=org.apache.samza.job.local.ProcessJobFactory
> # Kafka System
>
systems.kafka.samza.factory=org.apache.samza.system.kafka.KafkaSystemFactory
> systems.kafka.consumer.zookeeper.connect=localhost:2181
> systems.kafka.producer.bootstrap.servers=localhost:9092
> systems.kafka.default.stream.replication.factor=1
>
> I am getting following exception:
>
> org.apache.samza.config.ConfigException: Legacy task applications must
set a non-empty task.class in configuration.
>
> at
org.apache.samza.application.ApplicationUtil.fromConfig(ApplicationUtil.java:58)
>
> at
org.apache.samza.runtime.LocalContainerRunner.main(LocalContainerRunner.java:87)
>
> Versions:
> <beam.version>2.9.0</beam.version>
> <samza.version>0.14.1</samza.version>
>
> As per my understanding, I shouldn’t have to create implementation of
StreamApplication or StreamTask while using Beam SDK.
>
> An example of configFile for Samza-Beam Standalone application would be
helpful.
>
> Regards,
> Omkar Deshpande
