cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Capwell (Jira)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-15505) Add message interceptors to in-jvm dtests
Date Thu, 16 Jan 2020 16:11:00 GMT

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

David Capwell commented on CASSANDRA-15505:
-------------------------------------------

Quickly scanning the patch, is there a test you are writing which needs this?  The api looks
like it still requires you to have the right class path setup to work with the messages, so
calling run in like I do in failing repair test is kinda the same. What is this new abstraction
trying to solve?

iMessage is serializable now but didn’t see any existing messages being updated (scanned
on phone sorry); is there at concerns of this, mostly from maintenance and requires having
messages have two serializers (Cassandra and java)?

> Add message interceptors to in-jvm dtests
> -----------------------------------------
>
>                 Key: CASSANDRA-15505
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15505
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Test/dtest
>            Reporter: Alex Petrov
>            Assignee: Alex Petrov
>            Priority: Normal
>
> Currently we only have means to filter messages in in-jvm tests. We need a facility to
intercept and modify the messages between nodes for testing purposes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message