[
https://issues.apache.org/jira/browse/CASSANDRA-8083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14163635#comment-14163635
]
Michael Shuler commented on CASSANDRA-8083:
-------------------------------------------
The cassandra20 RPM depends only on 'java' which is satisfied by either
java-1.6.0-openjdk or java-1.7.0-openjdk - yum just ignorantly picks the first
one in the list. The option of depending specifically on java-1.7.0-openjdk
would mean that users that have installed Oracle's JRE/JDK package would still
get OpenJDK pulled in.
The "fix" for the cassandra21 RPM was to not depend on anything. There is no
java dependency at all. This is technically wrong, since Cassandra, of course,
depends on a functional JRE, but depending on nothing avoids the RPM dependency
doing the "wrong thing", as you have found.
The behavior you found is precisely why the DSC installation documentation
instructs the user to install java7 as a prerequisite to installing DSC.
http://www.datastax.com/documentation/cassandra/2.0/cassandra/install/installRHEL_t.html
http://www.datastax.com/documentation/cassandra/2.0/cassandra/install/installJreRHEL.html
The same prerequisite exists for the cassandra21 RPM - java needs to be
installed first - but, with no 'java' dependency in the package, the incorrect
OpenJDK will not be pulled in, if the user fails to follow the steps. Cassandra
will fail to start with no java installed, of course.
I'll look at the same "fix" in cassandra20 RPM - removing the 'java' dependency
altogether. I'd rather have a simple "oops, I forgot to install java" and the
user install exactly what is required, than the package doing the wrong thing,
and the user wondering what happened.
> OpenJDK 6 Dependency in dsc20 RPM
> ---------------------------------
>
> Key: CASSANDRA-8083
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8083
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
> Environment: Packages pulled from the community repo at
> http://rpm.datastax.com/community as per the installation guidelines.
> Reporter: Timo Beckers
> Assignee: Michael Shuler
> Priority: Minor
> Fix For: 2.0.10
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> According to https://issues.apache.org/jira/browse/CASSANDRA-6925 and
> https://issues.apache.org/jira/browse/CASSANDRA-7243, the Cassandra project
> only produces platform-agnostic .tar.gz. The person in the second ticket was
> referred to https://support.datastax.com/home to report RPM issues, but this
> ticketing system requires a login to post and registration is not open. I
> realize this is not the right issue tracker to post this on, but I hope to
> reach the community repo maintainer through this one.
> The problem I'm facing only seems to occur for the 'cassandra20' package from
> the Datastax community repo. On a fresh CentOS installation with no prior
> Java stack installed:
> # yum install dsc20
> Installing:
> dsc20
> Installing for dependencies:
> java-1.6.0-openjdk
> ...
> cassandra20
> This inevitably results in the following log message:
> "Cassandra 2.0 and later require Java 7 or later."
> and sometimes
> "Unsupported major.minor version 51.0"
> The issue seems to be with the 'cassandra20' package that depends on
> openjdk6. I noticed the same behaviour with dsc21 a couple weeks ago, but
> this seems to be fixed already. Could you please take a look or assign this
> to a person who could?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
