[
https://issues.apache.org/jira/browse/SAMZA-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061495#comment-14061495
]
Yan Fang commented on SAMZA-332:
--------------------------------
As discussed in SAMZA-318, we are thinking of using the stable release (0.7.0)
for the hello-samza and allow to pass version number if we want to change to
0.8.0-SNAPSHOT. See
[comment|https://issues.apache.org/jira/browse/SAMZA-318?focusedCommentId=14054204&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14054204].
Haven't committed the patch.
However, now it seems more tricky because changing version number actually will
fail the job as we need the dependency. Maybe it's the time to add one more
branch for hello-samza? I agree on Jakob's suggestion for branching
{quote}
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
{quote}
> 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)
