[
https://issues.apache.org/jira/browse/SAMZA-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Homan updated SAMZA-332:
------------------------------
Attachment: SAMZA-332.patch
Quick patch to add in the necessary dependencies. I'm not sure we ever decided
what to do re: master on hello-samza versus the development version of samza
proper. Perhaps we should have a branch on hello-samza that tracks what's
happening on trunk? That way, new users download the code and get master,
which points to the latest ASF release. We (the devs) can switch to the other
branch and apply patches there. Once a new release is done, we merge that dev
branch back to master and start the whole cycle over again?
> Wikipedia stats job fails on master due to lack of samza-kv-leveldb package
> in pom
> ----------------------------------------------------------------------------------
>
> Key: SAMZA-332
> URL: https://issues.apache.org/jira/browse/SAMZA-332
> Project: Samza
> Issue Type: Bug
> Components: hello-samza
> Reporter: Jakob Homan
> Attachments: SAMZA-332.patch
>
>
> Post SAMZA-256, building running the stats job fails at container start time
> as the config references
> org.apache.samza.storage.kv.KeyValueStorageEngineFactory, which is now
> located in the samza-kv-leveldb project, which is not included in the pom's
> dependency.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
