[
https://issues.apache.org/jira/browse/CASSANDRA-8777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216219#comment-15216219
]
Paulo Motta commented on CASSANDRA-8777:
----------------------------------------
Thanks for the patch. LGTM, I moved the CHANGES message up to the top (as it
should be), and also made a minor change on the stream error message.
Updated patch and tests are below (will mark as ready to commit when CI is
happy):
||trunk||
|[branch|https://github.com/apache/cassandra/compare/trunk...pauloricardomg:trunk-8777]|
|[testall|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-trunk-8777-testall/lastCompletedBuild/testReport/]|
|[dtest|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-trunk-8777-dtest/lastCompletedBuild/testReport/]|
> Streaming operations should log both endpoint and port associated with the
> operation
> ------------------------------------------------------------------------------------
>
> Key: CASSANDRA-8777
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8777
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jeremy Hanna
> Labels: lhf
> Fix For: 2.1.x
>
> Attachments: 8777-2.2.txt
>
>
> Currently we log the endpoint for a streaming operation. If the port has
> been overridden, it would be valuable to know that that setting is getting
> picked up. Therefore, when logging the endpoint address, it would be nice to
> also log the port it's trying to use.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
