cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremiah Jordan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11912) Remove DatabaseDescriptor import from AbstractType
Date Mon, 30 May 2016 13:54:12 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-11912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306688#comment-15306688
] 

Jeremiah Jordan commented on CASSANDRA-11912:
---------------------------------------------

Changing the interface on read value changers that public interface in a patch release, breaking
existing code. Has this gone out in a release yet?  If we want to do this I think we need
to do it as a system property or something like that. This setting isn't something that will
normally be used and we can document how to set it in the yaml description of the native protocol
max size.  And then get rid of the yaml property.

> Remove DatabaseDescriptor import from AbstractType
> --------------------------------------------------
>
>                 Key: CASSANDRA-11912
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11912
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Configuration, Core
>            Reporter: Jeremiah Jordan
>            Assignee: Alex Petrov
>             Fix For: 3.0.x, 3.x
>
>
> CASSANDRA-9530 added an import of DatabaseDescriptor in AbstractType, this import breaks
Thrift based java code which uses AbstractType based classes to deserialize types.  The max
size value should be give to AbstractType in some other way that doesn't require importing
DatabaseDescriptor.



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

Mime
View raw message