Re: Samza 0.12.0 artifact for scala 2.10 in maven central

Hi Maskim, +1 to your suggestion. I've created a JIRA here : https://issues.apache.org/jira/browse/SAMZA-1163. We will work on publishing samza-0.12 build supporting scala 2.10 version. Thanks.

Re: What happened when start a samza job?

Hi ShuQi, If you suspect the container is not making progress, A thread dump of the impacted container is super-helpful to debug this further. Can you please share thread dumps? On Wed, Mar 22, 2017 at 6:03 PM, 舒琦 wrote: > Hi, > > I’m using samza 0.12 and kafka

Re: Samza 0.12.0 artifact for scala 2.10 in maven central

Hi Maksim, >> maven central shows that samza 0.12.0 build exists for scala 2.11 only This was not a mis-build (as was stated in the release notes for 0.12). >> it would be nice to have builds for both supported scala versions +1 to this suggestion. Thanks for the feedback. We will to get to

What happened when start a samza job?

Hi, I’m using samza 0.12 and kafka 0.10. after running for several days, one of our job was restarted and it seems stuck in the “Get latest offset”. And after almost 30 minutes, it still stuck there. 2017-03-23 08:24:04.503 [main] KafkaUtil [INFO] Successfully validated topic

[GitHub] samza pull request #95: SAMZA-1161: Adding metrics into LocalStoreMonitor.

GitHub user shanthoosh opened a pull request: https://github.com/apache/samza/pull/95 SAMZA-1161: Adding metrics into LocalStoreMonitor. Rocksdb LocalStoreMonitor is responsible for clearing up unused local task partition stores. Metrics are required to understand the behavior of

[GitHub] samza pull request #89: SAMZA-1149: upgrade mockito from 1.8.4 to 1.10.19

Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/89 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Samza 0.12.0 artifact for scala 2.10 in maven central

Hi guys! As far as I can get from samza source code it’s scala 2.10 compatible. But maven central shows that samza 0.12.0 build exists for scala 2.11 only. Is it intended or mis-build? I think it would be nice to have builds for both supported scala versions, because scala itself is not backward

[GitHub] samza pull request #93: samza-1156: Improve ApplicationRunner method naming ...

Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/93 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is