[
https://issues.apache.org/jira/browse/SAMZA-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940070#comment-14940070
]
Navina Ramesh commented on SAMZA-784:
-------------------------------------
Hi [~jblasi] ,
When you clone from the fir repository, it pulls the master branch, which in
Samza has the latest code. Hence, you are getting 0.10 when you clone and
build.
The RocksDB issue mentioned in SAMZA-747 affects only 0.10.0 (master branch)
and is not seen in versions < 0.10.0. Are you suggesting that you are running
into the same issue in Samza 0.8 ?
Thanks!
> Posible installation bug in version 0.10.0
> ------------------------------------------
>
> Key: SAMZA-784
> URL: https://issues.apache.org/jira/browse/SAMZA-784
> Project: Samza
> Issue Type: Bug
> Components: test
> Affects Versions: 0.10.0
> Reporter: Jordi Blasi Uribarri
> Priority: Minor
> Labels: build, newbie
>
> When installing Samza with the default options:
> git clone http://git-wip-us.apache.org/repos/asf/samza.git
> cd samza
> ./gradlew clean build
> I obtained the version 0.10.0.
> During the installation process I saw the same error that got when installing
> the 0.8 version, which was referenced in this case.
> SAMZA-747 <https://issues.apache.org/jira/browse/SAMZA-747
> I bypassed it by comenting the code inside the code inside
> TestRocksDBKeyValueStore.scala .
> In version 0.9.1 I got no error.
> Currently I cannot reproduce it as my platform is being used for another
> project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
