cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-9768) Expose ConsistencyLevel.fromCode()
Date Thu, 09 Jul 2015 11:54:04 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-9768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sylvain Lebresne resolved CASSANDRA-9768.
-----------------------------------------
    Resolution: Invalid

Drivers, including the java one, are separate project from Cassandra. And Cassandra internal
code is not meant to be used as a library, so I'm not really sure what would be the point
of this. If you're suggesting this would allow the java driver to use the Cassandra enum,
then fyi the java driver absolutely do not want to depend on the Cassandra jar, so the fact
it has isn't own {{ConsistencyLevel}} class is a feature there.

> Expose ConsistencyLevel.fromCode()
> ----------------------------------
>
>                 Key: CASSANDRA-9768
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9768
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Drivers (now out of tree)
>         Environment: Cassandra 2.0.16
> Java driver 2.1.6
> Ubuntu 15.04
>            Reporter: Ajay
>             Fix For: 2.1.6
>
>
> Currently ConsistencyLevel is exposed as enum. But for REST APIs or configuration, it
will be a  number. Expose ConsistencyLevel.fromCode() as a public API so that we can get the
enum based on the provided configuration.
> Right to workaround, we having another enum or map to hold the number and ConsistencyLevel
num of Java driver.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message