Hi guys,
We're getting ready to release our first Samza project into production
soon, and after the development phase we're having a few questions about
scalability, version upgrades, state management and recovering from
failures, hopefully what I'm asking here is something you already have
experi
Hi all,
We're planning to have a Samza Job that reads from 2 or more Kafka topics,
the messages are serialized using Binary Json, we'd like to deserialize
each message to its specific Java Type, the job configuration only allows
to declare one system msg deserializer, is there any plan to allow pe
> Best,
>
> -Yi
>
> On Mon, May 11, 2015 at 5:30 PM, José Barrueta wrote:
>
> > Hi all,
> >
> > We're planning to have a Samza Job that reads from 2 or more Kafka
> topics,
> > the messages are serialized using Binary Json, we'd like to deserial
Hi all,
Once we figure it out the problem we were able to easily come up with a
solution for this.
Basically, we want to be able to set the `yarn.package.path` property to
look for an artifact over `https`, when we did this we ran into this
exception:
Exception in thread "main" java.io.IOExcepti
Thu, May 21, 2015 at 8:38 PM, Yi Pan wrote:
>
> > Hi, Jose,
> >
> > Thanks a lot! I I have opened a JIRA to support that: SAMZA-688.
> >
> > -Yi
> >
> > On Thu, May 21, 2015 at 8:03 PM, José Barrueta
> wrote:
> >
> > > Hi all,
> >
Hi all,
Currently we have some Jobs working with Samza v0.9.1 (kafka running on
v0.9.0) for a couple of those Jobs we'd like to upgrade them to Samza
v0.10.0, is there a documents that details the path for upgrading the Job
to latest version?
We already applied the new coordinator property:
*job.
Hi all,
Just to let you know, we already figured it out the problem, issue was that
we had a dependency version conflict that result in a mixed of 0.9.1 and
0.10.0 samza libraries in the same classpath.
Thanks,
Jose L Barrueta
On Wed, Feb 24, 2016 at 1:24 PM, José Barrueta wrote:
> Hi
Hi guys,
At Stormpath, we made a custom samza 10 version merging SAMZA-41 into it,
it's working well, so we are thinking to update that patch later this week
so it can be added to the main project.
HTH,
Jose Luis Barrueta
On Wed, Mar 2, 2016 at 2:11 PM, Yi Pan wrote:
> Hi, Robert,
>
> The mai
t! I am looking forward to the patch! Could you open an RB to the JIRA?
>
> Thanks a lot!
>
> -Yi
>
> On Wed, Mar 2, 2016 at 2:31 PM, José Barrueta wrote:
>
> > Hi guys,
> >
> > At Stormpath, we made a custom samza 10 version merging SAMZA-41 into it,
> >
Hi all,
I just added a question to SAMZA-870, since we run into the same issue
using Debian GNU/Linux 7 and Java 8 (Oracle 1.8.0_60).
One thing we tried was to not use compression but the we got this error:
Exception in thread "ThreadJob" org.rocksdb.RocksDBException: Corruption:
truncated block
build on RHEL6 and not on Debian.
>
> Have you tried clearing the gradle caches before building again?
>
> Thanks!
> Navina
>
> On Wed, Mar 9, 2016 at 5:06 PM, José Barrueta wrote:
>
> > Hi all,
> >
> > I just added a question to SAMZA-870, since we run int
Ok. I haven't seen this exception before. I can give it a try with the
> SAMZA-41 patch and try it out on my end.
>
> Navina
>
> On Wed, Mar 9, 2016 at 5:27 PM, José Barrueta wrote:
>
> > Hi Navina,
> >
> > Thanks for your quick reply!
> >
> > Act
mza build that you used, and the logs from the failed run to the JIRA?
>
> Thanks a lot!
>
> On Mon, May 2, 2016 at 2:38 PM, José Barrueta wrote:
>
> > Hi!
> >
> > Do you guys know if there has been any updates in these two issues, or
> any
> > other reports
13 matches
Mail list logo
