You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2016/08/15 09:08:20 UTC
[jira] [Updated] (FLINK-4394) RMQSource: The QueueName is not
accessible to subclasses
[ https://issues.apache.org/jira/browse/FLINK-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Metzger updated FLINK-4394:
----------------------------------
Assignee: Dominik Bruhn
> RMQSource: The QueueName is not accessible to subclasses
> --------------------------------------------------------
>
> Key: FLINK-4394
> URL: https://issues.apache.org/jira/browse/FLINK-4394
> Project: Flink
> Issue Type: Bug
> Components: Streaming Connectors
> Affects Versions: 1.1.1
> Reporter: Dominik Bruhn
> Assignee: Dominik Bruhn
>
> In version 1.1.0 we made the RMQSource extensible so that subclasses can configure how they want their queue for RabbitMQ/AMQP create. The subclasses can override
> {code}
> protected void setupQueue() throws IOException {
> channel.queueDeclare(queueName, true, false, false, null);
> }
> {code}
> The problem is, that the queueName property is private. So when override the setupQueue parameter, you don't know what actual queueName was provided. A simple change of the queueName property to protected fixes this.
> PR will follow
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)