.
Jordi
-Mensaje original-
De: Yi Pan [mailto:nickpa...@gmail.com]
Enviado el: miércoles, 12 de agosto de 2015 1:50
Para: dev@samza.apache.org
Asunto: Re: Missing a change log offset for SystemStreamPartition
Hi, Jordi,
I see your use case now. Essentially, you want to have an adjunct
ly.
> When
> > I try to access the same storage from a different job I just get null
> > results.
> >
> > How I am supposed to load the DB to be able to use it from the consuming
> > job? Is RocksDB the tool to use or should I use any other technique?
> >
>
>
> Jordi
>
>
>
> -Mensaje original-
> De: Yi Pan [mailto:nickpa...@gmail.com]
> Enviado el: martes, 11 de agosto de 2015 3:27
> Para: dev@samza.apache.org
> Asunto: Re: Missing a change log offset for SystemStreamPartition
>
> Hi, Jordi,
>
---
> De: Yi Pan [mailto:nickpa...@gmail.com]
> Enviado el: martes, 11 de agosto de 2015 3:27
> Para: dev@samza.apache.org
> Asunto: Re: Missing a change log offset for SystemStreamPartition
>
> Hi, Jordi,
>
> Agree with Yan. More specifically, your class definition should b
[mailto:nickpa...@gmail.com]
Enviado el: martes, 11 de agosto de 2015 3:27
Para: dev@samza.apache.org
Asunto: Re: Missing a change log offset for SystemStreamPartition
Hi, Jordi,
Agree with Yan. More specifically, your class definition should be something
like:
{code}
public class testStore implements
$$anonfun$startStores$2.apply(SamzaContainer.scala:607)
> > at scala.collection.Iterator$class.foreach(Iterator.scala:727)
> > at scala.collection.AbstractIterator.foreach(Iterator.scala:1157)
> > at
> > scala.collection.MapLike$DefaultValuesIterable.
Container.run(SamzaContainer.scala:550)
> at
> org.apache.samza.container.SamzaContainer$.safeMain(SamzaContainer.scala:108)
> at
> org.apache.samza.container.SamzaContainer$.main(SamzaContainer.scala:87)
> at
> org.apache.samza.container.SamzaContainer.mai
Container.main(SamzaContainer.scala)
The job fails even when there is no message sent to the input topic.
Samza is version 0.9.1 and kafka 0.8.2.
Thanks,
Jordi
-Mensaje original-
De: Jordi Blasi Uribarri [mailto:jbl...@nextel.es]
Enviado el: lunes, 10 de agosto de 2015 10:26
Para:
Mensaje original-
De: Yan Fang [mailto:yanfang...@gmail.com]
Enviado el: viernes, 07 de agosto de 2015 23:21
Para: dev@samza.apache.org
Asunto: Re: Missing a change log offset for SystemStreamPartition
Hi Jordi,
Sorry for getting you back late. Was quite busy yesterday.
I think the reason o
ocreate configured in Kafka I am not creating anything
> for the store. Is that ok?
>
> By the way, is there any problem on having two different stores?
>
> Thanks,
>
> Jordi
>
> -Mensaje original-
> De: Yan Fang [mailto:yanfang...@gmail.com]
> Enviado el:
having two different stores?
Thanks,
Jordi
-Mensaje original-
De: Yan Fang [mailto:yanfang...@gmail.com]
Enviado el: miércoles, 05 de agosto de 2015 20:23
Para: dev@samza.apache.org
Asunto: Re: Missing a change log offset for SystemStreamPartition
Hi Jordi,
I wonder, the reason of
Hi Jordi,
I wonder, the reason of your first exception is that, you changed the task
number (partition number of your input stream), but still were using the
same changelog stream. It is trying to send to the partition 2, which does
not exist?
Can you reproduce this exception in a new job? (new s
12 matches
Mail list logo
