{"action":"created","issue":{"url":"https://api.github.com/repos/spring-cloud/spring-cloud-stream-binder-rabbit/issues/18","repository_url":"https://api.github.com/repos/spring-cloud/spring-cloud-stream-binder-rabbit","labels_url":"https://api.github.com/repos/spring-cloud/spring-cloud-stream-binder-rabbit/issues/18/labels{/name}","comments_url":"https://api.github.com/repos/spring-cloud/spring-cloud-stream-binder-rabbit/issues/18/comments","events_url":"https://api.github.com/repos/spring-cloud/spring-cloud-stream-binder-rabbit/issues/18/events","html_url":"https://github.com/spring-cloud/spring-cloud-stream-binder-rabbit/issues/18","id":183045455,"number":18,"title":"There is no option to configure the routing key for anonymous queue binding","user":{"login":"SirWayne","id":6340898,"avatar_url":"https://avatars.githubusercontent.com/u/6340898?v=3","gravatar_id":"","url":"https://api.github.com/users/SirWayne","html_url":"https://github.com/SirWayne","followers_url":"https://api.github.com/users/SirWayne/followers","following_url":"https://api.github.com/users/SirWayne/following{/other_user}","gists_url":"https://api.github.com/users/SirWayne/gists{/gist_id}","starred_url":"https://api.github.com/users/SirWayne/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SirWayne/subscriptions","organizations_url":"https://api.github.com/users/SirWayne/orgs","repos_url":"https://api.github.com/users/SirWayne/repos","events_url":"https://api.github.com/users/SirWayne/events{/privacy}","received_events_url":"https://api.github.com/users/SirWayne/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-10-14T13:07:57Z","updated_at":"2016-10-17T22:00:18Z","closed_at":null,"body":"Currently the anonymous queue is always bound to all topics (#).  The topic is harcoded in RabbitMessageChannelBinder\r\n`declareBinding(queue.getName(), BindingBuilder.bind(queue).to(exchange).with(\"#\"));`\r\nSpring Cloud Bus uses Spring Cloud Stream to broadcast the messages (e.g. events)\r\n\r\nAlso so :\r\n\r\nFor some use cases it might be helpful to filter messages by topic. For example multiple nodes are publishing events but not every node is interested in all of them. Is it possible to introduce a binder property to configure the routing key?  "},"comment":{"url":"https://api.github.com/repos/spring-cloud/spring-cloud-stream-binder-rabbit/issues/comments/254347506","html_url":"https://github.com/spring-cloud/spring-cloud-stream-binder-rabbit/issues/18#issuecomment-254347506","issue_url":"https://api.github.com/repos/spring-cloud/spring-cloud-stream-binder-rabbit/issues/18","id":254347506,"user":{"login":"mbogoevici","id":159684,"avatar_url":"https://avatars.githubusercontent.com/u/159684?v=3","gravatar_id":"","url":"https://api.github.com/users/mbogoevici","html_url":"https://github.com/mbogoevici","followers_url":"https://api.github.com/users/mbogoevici/followers","following_url":"https://api.github.com/users/mbogoevici/following{/other_user}","gists_url":"https://api.github.com/users/mbogoevici/gists{/gist_id}","starred_url":"https://api.github.com/users/mbogoevici/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mbogoevici/subscriptions","organizations_url":"https://api.github.com/users/mbogoevici/orgs","repos_url":"https://api.github.com/users/mbogoevici/repos","events_url":"https://api.github.com/users/mbogoevici/events{/privacy}","received_events_url":"https://api.github.com/users/mbogoevici/received_events","type":"User","site_admin":false},"created_at":"2016-10-17T22:00:18Z","updated_at":"2016-10-17T22:00:18Z","body":"Hi @SirWayne,\r\n\r\nThanks for the issue and PR. Can you provide some details about this issue? The original premise is:\r\n\r\n> Currently the anonymous queue is always bound to all topics (#). \r\n\r\nIn the current implementation, an anonymous queue will receive all the messages sent to a given topic exchange. Publishers add the exchange name as the routing key for the message. In your solution, the user can choose between using the hash or the routing key on the queue - however, as far as I can tell, regardless of their choice, they will receive all messages - because all messages have the same routing key. Also, it seems like being able to set the routing key explicitly (rather than a boolean flag) is a more flexible option (but it would have to be known by the publisher). \r\n\r\n\r\nCan you provide some detail about your use case?\r\n\r\nThanks,\r\nMarius. "}}
{"actor":{"display_login":"mbogoevici"}}