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] [Commented] (CASSANDRA-11912) Remove DatabaseDescriptor import from AbstractType
Date Mon, 30 May 2016 15:36:12 GMT

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

Sylvain Lebresne commented on CASSANDRA-11912:
----------------------------------------------

I don't care terribly either way, but having it in the yaml is certainly more consistent with
how we deal with such setting in general and more particularly with {{native_transport_max_frame_size_in_mb}}
as you said, so I'd also just leave it here. Keeping the original of {{readValue()}} also
ought to be good enough.

> 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