Hi Yi,
Perfect, I'll rebase the branch to master tonight.
- José Luis
On Mon, May 2, 2016 at 2:55 PM Yi Pan wrote:
> Hi, Jose,
>
> Sorry for the delay. I left a comment on SAMZA-41.
>
> As for SAMZA-870, could you add your detailed job config file, the version
> of samza build that you used, a
Hi, Jose,
Sorry for the delay. I left a comment on SAMZA-41.
As for SAMZA-870, could you add your detailed job config file, the version
of samza 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 y
Hi!
Do you guys know if there has been any updates in these two issues, or any
other reports around SAMZA-870? For SAMZA-41 any comments on it?
Thank you!
- José Luis
On Wed, Mar 9, 2016 at 5:31 PM Navina Ramesh
wrote:
> Ah my bad. I didn't read your exception properly.
>
> Ok. I haven't seen
Ah my bad. I didn't read your exception properly.
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!
>
> Actually this problem
Hi Navina,
Thanks for your quick reply!
Actually this problem occurs at runtime while deploying our samza jobs in
our staging environment, we are deploying a custom samza 0.10.0 version
with SAMZA-41 in it.
We ran the same job with samza 0.9.1 and we didn't have any issues in it.
Thanks for yo
Hi Jose,
I will review the patch to SAMZA-41 today. Regarding the RocksDB issue, I
haven't encountered this issue after we pulled in the latest rocksdb
release. Then again, I was trying to build on RHEL6 and not on Debian.
Have you tried clearing the gradle caches before building again?
Thanks!
N
