[GitHub] kafka pull request #4232: KAFKA-6233 :Removed unnecessary null check

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4232 ---

Re: SessionKeySchema#segmentsToSearch()

For `SessionKeySchema#segmentsToSearch`: for session store, multiple sessions may merge together when receiving late arrived records. When I looked at the code, it seems that we have merged the sessions during aggregations to effectively move the sessions between segments. So I'm not 100% certain

Re: SessionKeySchema#segmentsToSearch()

For `getMinSegmentGreaterThanEqualToTimestamp` , the email was indeed meant for #4162. Pardon. On Sun, Nov 19, 2017 at 11:55 AM, Guozhang Wang wrote: > For `SessionKeySchema#segmentsToSearch`: for session store, multiple > sessions may merge together when receiving late

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

See

[jira] [Resolved] (KAFKA-6233) Removed unnecessary null check

[ https://issues.apache.org/jira/browse/KAFKA-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-6233. -- Resolution: Fixed Fix Version/s: 1.1.0 Issue resolved by pull request 4232

Re: [DISCUSS] KIP-213 Support non-key joining in KTable

Hello Jan, I think I get your point about the cumbersome that CombinedKey would introduce for serialization and tooling based on serdes. What I'm still wondering is the underlying of joinPrefixFakers mapper: from your latest comment it seems this mapper will be a one-time mapper: we use this to

Re: KIP-199 - Could offset management be part of the Connect REST API?

Hi Gunnar, I agree with you that the goal should be to implement offset management capabilities in the rest interface. I believe Randall's intention with this KIP was to lay the groundwork for accessing and changing offsets in Connect and then build on that functionality once the changes

[GitHub] kafka pull request #4236: testing...

Github user jawalesumit closed the pull request at: https://github.com/apache/kafka/pull/4236 ---

[jira] [Created] (KAFKA-6234) Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpoint

Guozhang Wang created KAFKA-6234: Summary: Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpoint Key: KAFKA-6234 URL: https://issues.apache.org/jira/browse/KAFKA-6234

Request to add to contributor's list...

Hello I have some free time & want to try to contribute to Kafka via resolving issues, and contributing to documentation. Please give me access rights for work with issues in JIRA & wiki edit rights My JIRA name is alexott Thank you -- With best wishes, Alex Ott http://alexott.blogspot.com/

[jira] [Created] (KAFKA-6235) Kafka should have an emergency retention setting for max disk used

Antony Stubbs created KAFKA-6235: Summary: Kafka should have an emergency retention setting for max disk used Key: KAFKA-6235 URL: https://issues.apache.org/jira/browse/KAFKA-6235 Project: Kafka

Re: [VOTE] KIP-159: Introducing Rich functions to Streams

Jan: which approach are you referring to as "the approach that is on the table would be perfect"? Note that in today's PAPI layer we are already effectively exposing the record context which has the issues that we have been discussing right now, and its semantics is always referring to the

[GitHub] kafka pull request #4237: KAFKA-6207 : Include start of record when RecordIs...

GitHub user jawalesumit opened a pull request: https://github.com/apache/kafka/pull/4237 KAFKA-6207 : Include start of record when RecordIsTooLarge When a message is too large to be sent (at org.apache.kafka.clients.producer.KafkaProducer#doSend), the RecordTooLargeException

[jira] [Resolved] (KAFKA-6223) Please delete old releases from mirroring system

[ https://issues.apache.org/jira/browse/KAFKA-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6223. Resolution: Fixed > Please delete old releases from mirroring system >

[GitHub] kafka pull request #4234: KAFKA-6207 : Include start of record when RecordIs...

Github user jawalesumit closed the pull request at: https://github.com/apache/kafka/pull/4234 ---

[GitHub] kafka pull request #4235: KAFKA-6207 : Include start of record when RecordIs...

GitHub user jawalesumit opened a pull request: https://github.com/apache/kafka/pull/4235 KAFKA-6207 : Include start of record when RecordIsTooLarge When a message is too large to be sent (at org.apache.kafka.clients.producer.KafkaProducer#doSend), the RecordTooLargeException

[GitHub] kafka pull request #4235: KAFKA-6207 : Include start of record when RecordIs...

Github user jawalesumit closed the pull request at: https://github.com/apache/kafka/pull/4235 ---

Re: [ANNOUNCE] Apache Kafka 0.11.0.2 Released

Thanks for running the release, Rajini! And with a single RC. :) Ismael On Fri, Nov 17, 2017 at 7:15 PM, Rajini Sivaram wrote: > The Apache Kafka community is pleased to announce the release for Apache > Kafka > 0.11.0.2. > > > This is a bug fix release and it includes

[GitHub] kafka pull request #4236: testing...

GitHub user jawalesumit opened a pull request: https://github.com/apache/kafka/pull/4236 testing... *More detailed description of your change, if necessary. The PR title and PR message become the squashed commit message, so use a separate comment to ping reviewers.*

答复: 答复: 答复: [DISCUSS]KIP-223 - Add per-topic min lead and per-partition lead metrics to KafkaConsumer

Jun, Thanks for the comments. Do you think it'd better to add topic/partition tags for those metrics as well as keep the prefix? If those prefixes should really be removed, does this KIP need to do the same thing for `lag` ones? 发件人: Jun Rao

Re: Kafka 0.9.0.1 partitions shrink and expand frequently after restart the broker

someone can help to analysis it？ > 在 2017年11月10日，上午11:08，Json Tu 写道： > > I‘m so sorry for my poor english. > > what I really means is my broker machine is configured as 8 core 16G. but my > jvm configure is as below. > java -Xmx1G -Xms1G -server -XX:+UseG1GC

[jira] [Created] (KAFKA-6236) stream not picking data from topic - after rebalancing

DHRUV BANSAL created KAFKA-6236: --- Summary: stream not picking data from topic - after rebalancing Key: KAFKA-6236 URL: https://issues.apache.org/jira/browse/KAFKA-6236 Project: Kafka Issue

[GitHub] kafka pull request #4238: KAFKA-6234: Increased timeout value for lowWaterma...

GitHub user soenkeliebau opened a pull request: https://github.com/apache/kafka/pull/4238 KAFKA-6234: Increased timeout value for lowWatermark response to avoid test failing occasionally Increase timeout to fix flaky integration test testLogStartOffsetCheckpoint. You can merge