Re: [DISCUSS] KIP-87 - Add Compaction Tombstone Flag

@Mayuresh i don't think you've missed anything - as per earlier in the discussion. We're providing new api versions, but not planning on bumping the magic number as there is no structural changes, we are simply using up a new attribute bit (as like adding new compression support just uses up ad

[jira] [Updated] (KAFKA-4346) Add foreachValue method to KStream

[ https://issues.apache.org/jira/browse/KAFKA-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4346: Labels: newbie (was: ) > Add foreachValue method to KStream > -- >

[jira] [Updated] (KAFKA-4346) Add foreachValue method to KStream

[ https://issues.apache.org/jira/browse/KAFKA-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4346: Assignee: (was: Guozhang Wang) > Add foreachValue method to KStream > --

[jira] [Updated] (KAFKA-4217) KStream.transform equivalent of flatMap

[ https://issues.apache.org/jira/browse/KAFKA-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4217: Assignee: (was: Guozhang Wang) > KStream.transform equivalent of flatMap > -

[jira] [Resolved] (KAFKA-4369) ZkClient is not closed upon streams shutdown

[ https://issues.apache.org/jira/browse/KAFKA-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska resolved KAFKA-4369. - Resolution: Won't Fix > ZkClient is not closed upon streams shutdown > ---

[GitHub] kafka pull request #2124: KAFKA-4359: Removed commit interval

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/2124 KAFKA-4359: Removed commit interval You can merge this pull request into a Git repository by running: $ git pull https://github.com/enothereska/kafka KAFKA-4359-intergration-tests-commit1

[jira] [Work started] (KAFKA-4359) Streams integration tests should not use commit interval of 1

[ https://issues.apache.org/jira/browse/KAFKA-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4359 started by Eno Thereska. --- > Streams integration tests should not use commit interval of 1 > -

[jira] [Commented] (KAFKA-4359) Streams integration tests should not use commit interval of 1

[ https://issues.apache.org/jira/browse/KAFKA-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657007#comment-15657007 ] ASF GitHub Bot commented on KAFKA-4359: --- GitHub user enothereska opened a pull reque

[jira] [Updated] (KAFKA-4317) RocksDB checkpoint files lost on kill -9

[ https://issues.apache.org/jira/browse/KAFKA-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4317: Assignee: (was: Guozhang Wang) > RocksDB checkpoint files lost on kill -9 >

[jira] [Updated] (KAFKA-4273) Streams DSL - Add TTL / retention period support for intermediate topics and state stores

[ https://issues.apache.org/jira/browse/KAFKA-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4273: Assignee: (was: Guozhang Wang) > Streams DSL - Add TTL / retention period support for intermedia

[jira] [Updated] (KAFKA-4281) Should be able to forward aggregation values immediately

[ https://issues.apache.org/jira/browse/KAFKA-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4281: Assignee: (was: Guozhang Wang) > Should be able to forward aggregation values immediately >

[jira] [Updated] (KAFKA-4240) Remove disableLogging from API

[ https://issues.apache.org/jira/browse/KAFKA-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4240: Assignee: Guozhang Wang (was: Eno Thereska) > Remove disableLogging from API >

[jira] [Resolved] (KAFKA-4263) QueryableStateIntegrationTest.concurrentAccess is failing occasionally in jenkins builds

[ https://issues.apache.org/jira/browse/KAFKA-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska resolved KAFKA-4263. - Resolution: Not A Problem > QueryableStateIntegrationTest.concurrentAccess is failing occasionally

[jira] [Updated] (KAFKA-4219) Permit setting of event time in stream processor

[ https://issues.apache.org/jira/browse/KAFKA-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4219: Assignee: (was: Guozhang Wang) > Permit setting of event time in stream processor >

[jira] [Commented] (KAFKA-4263) QueryableStateIntegrationTest.concurrentAccess is failing occasionally in jenkins builds

[ https://issues.apache.org/jira/browse/KAFKA-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657015#comment-15657015 ] Eno Thereska commented on KAFKA-4263: - Haven't seen this. Closing for now. > Queryabl

[jira] [Updated] (KAFKA-4218) Enable access to key in {{ValueTransformer}}

[ https://issues.apache.org/jira/browse/KAFKA-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4218: Assignee: (was: Guozhang Wang) > Enable access to key in {{ValueTransformer}} >

[jira] [Commented] (KAFKA-4186) Transient failure in KStreamAggregationIntegrationTest.shouldGroupByKey

[ https://issues.apache.org/jira/browse/KAFKA-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657022#comment-15657022 ] Eno Thereska commented on KAFKA-4186: - I haven't seen this happen. Is it still an issu

[jira] [Updated] (KAFKA-4182) Move the change logger our of RocksDB stores

[ https://issues.apache.org/jira/browse/KAFKA-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4182: Assignee: (was: Guozhang Wang) > Move the change logger our of RocksDB stores >

Re: [VOTE] KIP-72 - Allow putting a bound on memory consumed by Incoming requests

Radai, 11. The KIP talks about a new server configuration parameter *memory.pool.class.name *which is not in the implementation. Is it still the case that the pool will be configurable? 12. Personally I would prefer not to have a garbage collected pool that hides b

[jira] [Updated] (KAFKA-4144) Allow per stream/table timestamp extractor

[ https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4144: Assignee: (was: Guozhang Wang) > Allow per stream/table timestamp extractor > --

[jira] [Resolved] (KAFKA-4181) Processors punctuate() methods call multiple times

[ https://issues.apache.org/jira/browse/KAFKA-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska resolved KAFKA-4181. - Resolution: Not A Problem > Processors punctuate() methods call multiple times > -

Re: [DISCUSS] KIP-84: Support SASL/SCRAM mechanisms

I think all the comments and suggestions on this thread have now been incorporated into the KIP. If there are no objections, I will start the voting process on Monday. Regards, Rajini On Tue, Nov 8, 2016 at 9:20 PM, Rajini Sivaram wrote: > Jun, > > Have added a sub-section on delegation token

[GitHub] kafka pull request #2122: failing to close this iterator causes leaks in roc...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2122 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Updated] (KAFKA-3739) Add no-arg constructor for library provided serdes

[ https://issues.apache.org/jira/browse/KAFKA-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3739: Assignee: (was: Liquan Pei) > Add no-arg constructor for library provided serdes > -

[jira] [Updated] (KAFKA-3705) Support non-key joining in KTable

[ https://issues.apache.org/jira/browse/KAFKA-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3705: Assignee: (was: Liquan Pei) > Support non-key joining in KTable > --

[jira] [Commented] (KAFKA-3262) Make KafkaStreams debugging friendly

[ https://issues.apache.org/jira/browse/KAFKA-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657242#comment-15657242 ] Eno Thereska commented on KAFKA-3262: - This is now fixed with KIP-62 > Make KafkaStre

[jira] [Updated] (KAFKA-4199) When a window store segment is dropped we should also clear any corresponding cached entries

[ https://issues.apache.org/jira/browse/KAFKA-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4199: Assignee: (was: Guozhang Wang) > When a window store segment is dropped we should also clear any

[jira] [Updated] (KAFKA-3835) Streams is creating two ProducerRecords for each send via RecordCollector

[ https://issues.apache.org/jira/browse/KAFKA-3835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3835: Labels: newbie (was: ) > Streams is creating two ProducerRecords for each send via RecordCollector

[jira] [Updated] (KAFKA-3625) Move kafka-streams test fixtures into a published package

[ https://issues.apache.org/jira/browse/KAFKA-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3625: Assignee: (was: Guozhang Wang) > Move kafka-streams test fixtures into a published package > ---

[jira] [Updated] (KAFKA-3534) Deserialize on demand when default time extractor used

[ https://issues.apache.org/jira/browse/KAFKA-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3534: Assignee: (was: Guozhang Wang) > Deserialize on demand when default time extractor used > --

[jira] [Resolved] (KAFKA-3262) Make KafkaStreams debugging friendly

[ https://issues.apache.org/jira/browse/KAFKA-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska resolved KAFKA-3262. - Resolution: Duplicate > Make KafkaStreams debugging friendly > ---

[jira] [Updated] (KAFKA-4304) Extend Interactive Queries for return latest update timestamp per key

[ https://issues.apache.org/jira/browse/KAFKA-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4304: Assignee: (was: Guozhang Wang) > Extend Interactive Queries for return latest update timestamp p

[jira] [Updated] (KAFKA-3835) Streams is creating two ProducerRecords for each send via RecordCollector

[ https://issues.apache.org/jira/browse/KAFKA-3835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3835: Assignee: (was: Guozhang Wang) > Streams is creating two ProducerRecords for each send via Recor

[jira] [Created] (KAFKA-4398) offsetsForTimes returns false starting offset when timestamp of messages are not monotonically increasing

huxi created KAFKA-4398: --- Summary: offsetsForTimes returns false starting offset when timestamp of messages are not monotonically increasing Key: KAFKA-4398 URL: https://issues.apache.org/jira/browse/KAFKA-4398

[jira] [Commented] (KAFKA-4398) offsetsForTimes returns false starting offset when timestamp of messages are not monotonically increasing

[ https://issues.apache.org/jira/browse/KAFKA-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657350#comment-15657350 ] huxi commented on KAFKA-4398: - [~becket_qin] Does it make any sense? > offsetsForTimes return

Build failed in Jenkins: kafka-trunk-jdk8 #1035

See Changes: [wangguoz] HOTFIX: failing to close this iterator causes leaks in rocksdb -- [...truncated 3872 lines...] kafka.integration.SaslPlaintextTopicMetadataTest > testIsrAfterBrokerShut

Build failed in Jenkins: kafka-trunk-jdk7 #1684

See Changes: [wangguoz] HOTFIX: failing to close this iterator causes leaks in rocksdb -- [...truncated 14337 lines...] org.apache.kafka.streams.processor.internals.StreamsMetadataStateTest > s

Build failed in Jenkins: kafka-0.10.1-jdk7 #85

See Changes: [wangguoz] HOTFIX: failing to close this iterator causes leaks in rocksdb -- [...truncated 12159 lines...] org.apache.kafka.common.security.ssl.SslFactoryTest > testClientMode STARTE

Re: [DISCUSS] KIP-87 - Add Compaction Tombstone Flag

Sounds good Michael. Thanks, Mayuresh On Fri, Nov 11, 2016 at 12:48 AM, Michael Pearce wrote: > @Mayuresh i don't think you've missed anything - > > as per earlier in the discussion. > > We're providing new api versions, but not planning on bumping the magic > number as there is no structural

[GitHub] kafka pull request #2081: MINOR: Extend mirror maker test to include interce...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2081 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-4107) Support offset reset capability in Kafka Connect

[ https://issues.apache.org/jira/browse/KAFKA-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657561#comment-15657561 ] Chris Riccomini commented on KAFKA-4107: Agreed. We've had this need as well, and

Re: [VOTE] KIP-72 - Allow putting a bound on memory consumed by Incoming requests

jun's #1 + rajini's #11 - the new config param is to enable changing the pool implentation class. as i said in my response to jun i will make the default pool impl be the simple one, and this param is to allow a user (more likely a dev) to change it. both the simple pool and the "gc pool" make basi

Re: [VOTE] KIP-72 - Allow putting a bound on memory consumed by Incoming requests

Hey Radai, +1 on deprecating and eventually removing the old config. The intention was absolutely bounding memory usage. I think having two ways of doing this, one that gives a crisp bound on memory and one that is hard to reason about is pretty confusing. I think people will really appreciate hav

Re: [DISCUSS] KIP-87 - Add Compaction Tombstone Flag

Hey Michael, The way Kafka implements backwards compatibility is to let the brokers support old protocols. So the brokers have to support older clients that do not understand the new attribute bit. That means we will not be able to get away with the null value as a tombstone. So we need a good def

[jira] [Updated] (KAFKA-4379) Remove caching of dirty and removed keys from StoreChangeLogger

[ https://issues.apache.org/jira/browse/KAFKA-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4379: - Resolution: Fixed Fix Version/s: (was: 0.10.1.1) 0.10.2.0

[GitHub] kafka pull request #2103: KAFKA-4379: Remove caching of dirty and removed ke...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2103 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-4379) Remove caching of dirty and removed keys from StoreChangeLogger

[ https://issues.apache.org/jira/browse/KAFKA-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657717#comment-15657717 ] ASF GitHub Bot commented on KAFKA-4379: --- Github user asfgit closed the pull request

[jira] [Commented] (KAFKA-3994) Deadlock between consumer heartbeat expiration and offset commit.

[ https://issues.apache.org/jira/browse/KAFKA-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657721#comment-15657721 ] mjuarez commented on KAFKA-3994: Just tried this patch against the stock 0.10.1.0 branch,

[jira] [Resolved] (KAFKA-4081) Consumer API consumer new interface commitSyn does not verify the validity of offset

[ https://issues.apache.org/jira/browse/KAFKA-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-4081. Resolution: Fixed Fix Version/s: 0.10.2.0 Issue resolved by pull request 1827 [https:

[GitHub] kafka pull request #1827: KAFKA-4081: Consumer API consumer new interface co...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1827 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-4081) Consumer API consumer new interface commitSyn does not verify the validity of offset

[ https://issues.apache.org/jira/browse/KAFKA-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657766#comment-15657766 ] ASF GitHub Bot commented on KAFKA-4081: --- Github user asfgit closed the pull request

[jira] [Commented] (KAFKA-4398) offsetsForTimes returns false starting offset when timestamp of messages are not monotonically increasing

[ https://issues.apache.org/jira/browse/KAFKA-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657795#comment-15657795 ] Jiangjie Qin commented on KAFKA-4398: - [~huxi_2b] I am not sure I understand the issue

Jenkins build is back to normal : kafka-trunk-jdk8 #1036

See

[jira] [Commented] (KAFKA-3729) Auto-configure non-default SerDes passed alongside the topology builder

[ https://issues.apache.org/jira/browse/KAFKA-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657814#comment-15657814 ] Guozhang Wang commented on KAFKA-3729: -- [~bharatviswa] are you still working on this

[jira] [Updated] (KAFKA-4322) StateRestoreCallback begin and end indication

[ https://issues.apache.org/jira/browse/KAFKA-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4322: - Assignee: Mark Shelton (was: Guozhang Wang) > StateRestoreCallback begin and end indication > ---

Build failed in Jenkins: kafka-trunk-jdk7 #1685

See Changes: [me] MINOR: Extend mirror maker test to include interceptors -- [...truncated 14337 lines...] org.apache.kafka.streams.processor.internals.StreamsMetadataStateTest > shouldThrowWhe

[jira] [Commented] (KAFKA-2076) Add an API to new consumer to allow user get high watermark of partitions.

[ https://issues.apache.org/jira/browse/KAFKA-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657823#comment-15657823 ] Jeff Widman commented on KAFKA-2076: It'd be great to see this move forward. > Add an

[jira] [Assigned] (KAFKA-4355) StreamThread intermittently dies with "Topic not found during partition assignment" when broker restarted

[ https://issues.apache.org/jira/browse/KAFKA-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reassigned KAFKA-4355: --- Assignee: Eno Thereska (was: Guozhang Wang) > StreamThread intermittently dies with "Topic n

[jira] [Commented] (KAFKA-4322) StateRestoreCallback begin and end indication

[ https://issues.apache.org/jira/browse/KAFKA-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657841#comment-15657841 ] Guozhang Wang commented on KAFKA-4322: -- [~markshelton] Thanks for proposing this tick

[GitHub] kafka pull request #1972: KAFKA-3224: New log deletion policy based on times...

Github user bill-warshaw closed the pull request at: https://github.com/apache/kafka/pull/1972 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature i

[jira] [Commented] (KAFKA-3224) Add timestamp-based log deletion policy

[ https://issues.apache.org/jira/browse/KAFKA-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657889#comment-15657889 ] ASF GitHub Bot commented on KAFKA-3224: --- Github user bill-warshaw closed the pull re

[jira] [Commented] (KAFKA-2076) Add an API to new consumer to allow user get high watermark of partitions.

[ https://issues.apache.org/jira/browse/KAFKA-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657963#comment-15657963 ] Jiangjie Qin commented on KAFKA-2076: - [~jeffwidman] The consumer actually are able to

[jira] [Resolved] (KAFKA-2076) Add an API to new consumer to allow user get high watermark of partitions.

[ https://issues.apache.org/jira/browse/KAFKA-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-2076. - Resolution: Fixed Fix Version/s: 0.10.1.0 After KIP-79(https://cwiki.apache.org/confluence

Re: [VOTE] KIP-72 - Allow putting a bound on memory consumed by Incoming requests

13. At the moment, I think channels are not muted if: channel.receive != null && channel.receive.buffer != null This mutes all channels that aren't holding onto a incomplete buffer. They may or may not have read the 4-byte size. I was thinking you could avoid muting channels if: channel.re

[jira] [Created] (KAFKA-4399) Deadlock between cleanupGroupMetadata and offset commit

Alexey Ozeritskiy created KAFKA-4399: Summary: Deadlock between cleanupGroupMetadata and offset commit Key: KAFKA-4399 URL: https://issues.apache.org/jira/browse/KAFKA-4399 Project: Kafka

[jira] [Updated] (KAFKA-4399) Deadlock between cleanupGroupMetadata and offset commit

[ https://issues.apache.org/jira/browse/KAFKA-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-4399: - Attachment: deadlock-stack > Deadlock between cleanupGroupMetadata and offset commit > ---

[GitHub] kafka pull request #2125: KAFKA-4399; deadlock cleanupGroupMetadata and offs...

GitHub user resetius opened a pull request: https://github.com/apache/kafka/pull/2125 KAFKA-4399; deadlock cleanupGroupMetadata and offset commit fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/resetius/kafka KAFKA-4399 Al

[jira] [Commented] (KAFKA-4399) Deadlock between cleanupGroupMetadata and offset commit

[ https://issues.apache.org/jira/browse/KAFKA-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658021#comment-15658021 ] ASF GitHub Bot commented on KAFKA-4399: --- GitHub user resetius opened a pull request:

[jira] [Commented] (KAFKA-4399) Deadlock between cleanupGroupMetadata and offset commit

[ https://issues.apache.org/jira/browse/KAFKA-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658027#comment-15658027 ] Alexey Ozeritskiy commented on KAFKA-4399: -- The simplest way to fix it is to move

[jira] [Updated] (KAFKA-4399) Deadlock between cleanupGroupMetadata and offset commit

[ https://issues.apache.org/jira/browse/KAFKA-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-4399: - Status: Patch Available (was: Open) > Deadlock between cleanupGroupMetadata and offset co

[jira] [Commented] (KAFKA-4399) Deadlock between cleanupGroupMetadata and offset commit

[ https://issues.apache.org/jira/browse/KAFKA-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658044#comment-15658044 ] Alexey Ozeritskiy commented on KAFKA-4399: -- As for now I think you can use the fo

Jenkins build is back to normal : kafka-trunk-jdk7 #1686

See

Build failed in Jenkins: kafka-trunk-jdk8 #1037

See Changes: [wangguoz] KAFKA-4379: Remove caching of dirty and removed keys from [jason] KAFKA-4081; KafkaConsumer should not allow negative offsets to be -- [...truncated 14328 lines...] org

[jira] [Updated] (KAFKA-4219) Permit setting of event time in stream processor

[ https://issues.apache.org/jira/browse/KAFKA-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4219: - Labels: api user-experience (was: ) > Permit setting of event time in stream processor >

[jira] [Updated] (KAFKA-4281) Should be able to forward aggregation values immediately

[ https://issues.apache.org/jira/browse/KAFKA-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4281: - Status: Patch Available (was: Open) > Should be able to forward aggregation values immediately >

[jira] [Updated] (KAFKA-4219) Permit setting of event time in stream processor

[ https://issues.apache.org/jira/browse/KAFKA-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4219: - Labels: api (was: api user-experience) > Permit setting of event time in stream processor > -

[jira] [Updated] (KAFKA-4281) Should be able to forward aggregation values immediately

[ https://issues.apache.org/jira/browse/KAFKA-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4281: - Assignee: Greg Fodor > Should be able to forward aggregation values immediately >

[jira] [Commented] (KAFKA-4281) Should be able to forward aggregation values immediately

[ https://issues.apache.org/jira/browse/KAFKA-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658156#comment-15658156 ] Guozhang Wang commented on KAFKA-4281: -- As a hinder-thought of KIP-63, I think it is

[jira] [Updated] (KAFKA-4270) ClassCast for Agregation

[ https://issues.apache.org/jira/browse/KAFKA-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4270: - Labels: architecture (was: ) > ClassCast for Agregation > > >

[jira] [Updated] (KAFKA-4270) ClassCast for Agregation

[ https://issues.apache.org/jira/browse/KAFKA-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4270: - Priority: Critical (was: Major) > ClassCast for Agregation > > >

Re: [VOTE] KIP-72 - Allow putting a bound on memory consumed by Incoming requests

ok, i've made the following changes: 1. memory.pool.class.name has been removed 2. the code now only uses SimpleMemoryPool. the gc variant is left (unused) as a developement aid and is unsettable via configuration. 3. I've resolved the issue of stale data getting stuck in intermediate (ssl) buffer

[jira] [Updated] (KAFKA-3522) Consider adding version information into rocksDB storage format

[ https://issues.apache.org/jira/browse/KAFKA-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3522: - Priority: Critical (was: Major) > Consider adding version information into rocksDB storage format

[jira] [Updated] (KAFKA-4240) Remove disableLogging from API

[ https://issues.apache.org/jira/browse/KAFKA-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4240: - Assignee: (was: Guozhang Wang) > Remove disableLogging from API >

[jira] [Updated] (KAFKA-4317) RocksDB checkpoint files lost on kill -9

[ https://issues.apache.org/jira/browse/KAFKA-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4317: - Priority: Critical (was: Major) > RocksDB checkpoint files lost on kill -9 >

[jira] [Updated] (KAFKA-4212) Add a key-value store that is a TTL persistent cache

[ https://issues.apache.org/jira/browse/KAFKA-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4212: - Assignee: (was: Guozhang Wang) > Add a key-value store that is a TTL persistent cache > --

[jira] [Updated] (KAFKA-4212) Add a key-value store that is a TTL persistent cache

[ https://issues.apache.org/jira/browse/KAFKA-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4212: - Labels: api (was: ) > Add a key-value store that is a TTL persistent cache >

[GitHub] kafka pull request #2126: MINOR: Fix export command for additional env vars ...

GitHub user kkonstantine opened a pull request: https://github.com/apache/kafka/pull/2126 MINOR: Fix export command for additional env vars in connect system tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/kkonstantine/kafk

[jira] [Commented] (KAFKA-4120) byte[] keys in RocksDB state stores do not work as expected

[ https://issues.apache.org/jira/browse/KAFKA-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658318#comment-15658318 ] Guozhang Wang commented on KAFKA-4120: -- Marking it as resolved after 0.10.1.0. [~elev

[jira] [Resolved] (KAFKA-4120) byte[] keys in RocksDB state stores do not work as expected

[ https://issues.apache.org/jira/browse/KAFKA-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4120. -- Resolution: Fixed Fix Version/s: 0.10.1.0 > byte[] keys in RocksDB state stores do not wo

[jira] [Updated] (KAFKA-4346) Add foreachValue method to KStream

[ https://issues.apache.org/jira/browse/KAFKA-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4346: - Assignee: Xavier Léauté > Add foreachValue method to KStream > --

[GitHub] kafka pull request #2126: MINOR: Fix export command for additional env vars ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2126 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Created] (KAFKA-4400) Prefix for sink task consumer groups should be configurable

Ewen Cheslack-Postava created KAFKA-4400: Summary: Prefix for sink task consumer groups should be configurable Key: KAFKA-4400 URL: https://issues.apache.org/jira/browse/KAFKA-4400 Project: Ka

Subscribe to Kafka

Newbie developer to kafka.

Jenkins build is back to normal : kafka-trunk-jdk8 #1038

See

[jira] [Commented] (KAFKA-4398) offsetsForTimes returns false starting offset when timestamp of messages are not monotonically increasing

[ https://issues.apache.org/jira/browse/KAFKA-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658690#comment-15658690 ] huxi commented on KAFKA-4398: - [~becket_qin] Based on the current design, you are definitely r

[Subscribe]

Please subscribe me to this group

Re: [DISCUSS] KIP-87 - Add Compaction Tombstone Flag

I think "In second stage we move on to supporting only the attribute flag for log compaction." means that it will no longer support request from older clients. Thanks, Mayuresh On Fri, Nov 11, 2016 at 10:02 AM, Becket Qin wrote: > Hey Michael, > > The way Kafka implements backwards compatibili

[jira] [Comment Edited] (KAFKA-2076) Add an API to new consumer to allow user get high watermark of partitions.

[ https://issues.apache.org/jira/browse/KAFKA-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658812#comment-15658812 ] Jeff Widman edited comment on KAFKA-2076 at 11/12/16 2:21 AM: --

[jira] [Commented] (KAFKA-2076) Add an API to new consumer to allow user get high watermark of partitions.

[ https://issues.apache.org/jira/browse/KAFKA-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658812#comment-15658812 ] Jeff Widman commented on KAFKA-2076: Thanks [~becket_qin], BTW great presentation at t

[jira] [Comment Edited] (KAFKA-2076) Add an API to new consumer to allow user get high watermark of partitions.

[ https://issues.apache.org/jira/browse/KAFKA-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658812#comment-15658812 ] Jeff Widman edited comment on KAFKA-2076 at 11/12/16 2:22 AM: --

  1   2   >