cassandra-commits mailing list archives

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

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

Stefania commented on CASSANDRA-11912:
--------------------------------------

CASSANDRA-9530 has not been released yet.

However, I would prefer to keep the yaml property if [~jjordan] is happy with the original
overload of {{readValue}} that doesn't enforce any limit. The reason is that from the user
point of view, if they need to change the native protocol size in the yaml, then they also
need to set a system property, which is really a poor experience. I do agree that this is
something that shouldn't really happen though, so we could remove the yaml property if needed.
[~slebresne] WDYT?

> 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