{"action":"created","issue":{"url":"https://api.github.com/repos/Blizzard/node-rdkafka/issues/18","repository_url":"https://api.github.com/repos/Blizzard/node-rdkafka","labels_url":"https://api.github.com/repos/Blizzard/node-rdkafka/issues/18/labels{/name}","comments_url":"https://api.github.com/repos/Blizzard/node-rdkafka/issues/18/comments","events_url":"https://api.github.com/repos/Blizzard/node-rdkafka/issues/18/events","html_url":"https://github.com/Blizzard/node-rdkafka/issues/18","id":172745517,"number":18,"title":"Manual offset and partition assignment?","user":{"login":"ottomata","id":1626054,"avatar_url":"https://avatars.githubusercontent.com/u/1626054?v=3","gravatar_id":"","url":"https://api.github.com/users/ottomata","html_url":"https://github.com/ottomata","followers_url":"https://api.github.com/users/ottomata/followers","following_url":"https://api.github.com/users/ottomata/following{/other_user}","gists_url":"https://api.github.com/users/ottomata/gists{/gist_id}","starred_url":"https://api.github.com/users/ottomata/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ottomata/subscriptions","organizations_url":"https://api.github.com/users/ottomata/orgs","repos_url":"https://api.github.com/users/ottomata/repos","events_url":"https://api.github.com/users/ottomata/events{/privacy}","received_events_url":"https://api.github.com/users/ottomata/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-08-23T16:27:03Z","updated_at":"2016-08-23T16:57:26Z","closed_at":null,"body":"This might be a feature request, and it might not be possible.\r\n\r\nMy use case needs 'simple consumer' like behavior.  I don't want Kafka to manage consumer group rebalancing, and I won't be doing any offset commits.  I do want consumers to be able to provide topic, partition, and offset from which they will begin consuming, so that clients can manage their own offsets.  When the protocol eventually supports consuming based on event timestamps, I'd like to support that as well.\r\n\r\nIs this possible?  I see `KafkaConsumer.prototype.assign ` is a function, but I don't see anything using it, and my attempts to do so leave me in `Erroneous state` from librdkafka.  I _think_ this is either because the offsets aren't actually passed to librdkafka's assign, or because of some internal `subscribed` state that is not being updated.\r\n\r\nIs doing something like `consumer.assign([ { topic: 'test', partition: 0, offset: 1102583 } ])` possible?\r\n\r\nAlso, if can I disable auto consumer group rebalancing?  I'm looking for a way to override the rebalance_cb, but I don't see that."},"comment":{"url":"https://api.github.com/repos/Blizzard/node-rdkafka/issues/comments/241800513","html_url":"https://github.com/Blizzard/node-rdkafka/issues/18#issuecomment-241800513","issue_url":"https://api.github.com/repos/Blizzard/node-rdkafka/issues/18","id":241800513,"user":{"login":"webmakersteve","id":6353085,"avatar_url":"https://avatars.githubusercontent.com/u/6353085?v=3","gravatar_id":"","url":"https://api.github.com/users/webmakersteve","html_url":"https://github.com/webmakersteve","followers_url":"https://api.github.com/users/webmakersteve/followers","following_url":"https://api.github.com/users/webmakersteve/following{/other_user}","gists_url":"https://api.github.com/users/webmakersteve/gists{/gist_id}","starred_url":"https://api.github.com/users/webmakersteve/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/webmakersteve/subscriptions","organizations_url":"https://api.github.com/users/webmakersteve/orgs","repos_url":"https://api.github.com/users/webmakersteve/repos","events_url":"https://api.github.com/users/webmakersteve/events{/privacy}","received_events_url":"https://api.github.com/users/webmakersteve/received_events","type":"User","site_admin":false},"created_at":"2016-08-23T16:57:26Z","updated_at":"2016-08-23T16:57:26Z","body":"`assign` should be the way to do this. If it isn't working it's a bug. I haven't tested it much because we don't use it.\r\n\r\n`librdkafka` also has a Simple Consumer, however, that does not have managed offsets and partitions. I planned on eventually implementing this if there was a desire for it (this is why the property is `Kafka.KafkaConsumer` and not `Kafka.Consumer`).\r\n\r\nIn any event, it's likely that the internal subscribed state is not being updated, as you said. I'll take a look at this and get back to you :)"}}
{"actor":{"display_login":"webmakersteve"}}