Hi,
Thanks for your comments. I rethink about including rich functions into
this KIP.
I think once we include rich functions in this KIP and then fix
ProcessorContext in another KIP and incorporate with existing rich
functions, the code will not be backwards compatible.
I see Damian's and your po
GitHub user jeyhunkarimov opened a pull request:
https://github.com/apache/kafka/pull/3109
KAFKA-4144: Allow per stream/table timestamp extractor
A follow up RP to fix
[issue](https://github.com/confluentinc/examples/commit/2cd0b87bc8a7eab0e7199fa0079db6417f0e6b63#commitcomment-2220
[
https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018382#comment-16018382
]
ASF GitHub Bot commented on KAFKA-4144:
---
GitHub user jeyhunkarimov opened a pull req
Dear community,
I want to inform you that because of the case [1] we needed to add an extra
overloaded method to KIP:
*KStreamBuilder.globalTable(final Serde keySerde, final Serde
valSerde, final String topic, final String storeName) *
[1]
https://github.com/confluentinc/examples/commit/2cd0b87bc
[
https://issues.apache.org/jira/browse/KAFKA-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Umesh Chaudhary reassigned KAFKA-4660:
--
Assignee: Umesh Chaudhary
> Improve test coverage KafkaStreams
> --
Dear community,
As we discussed in KIP-149 [DISCUSS] thread [1], I would like to initiate
KIP for rich functions (interfaces) [2].
I would like to get your comments.
[1]
http://search-hadoop.com/m/Kafka/uyzND1PMjdk2CslH12?subj=Re+DISCUSS+KIP+149+Enabling+key+access+in+ValueTransformer+ValueMappe
Kyle Ambroff created KAFKA-5297:
---
Summary: Broker can take a long time to shut down if there are
many active log segments
Key: KAFKA-5297
URL: https://issues.apache.org/jira/browse/KAFKA-5297
Project: K
[
https://issues.apache.org/jira/browse/KAFKA-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018527#comment-16018527
]
Kyle Ambroff commented on KAFKA-5297:
-
Patch incoming.
> Broker can take a long time
[
https://issues.apache.org/jira/browse/KAFKA-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyle Ambroff updated KAFKA-5297:
Attachment: LogSegmentBenchmark.java
Attaching benchmark code in case anyone wants to validate the w
[
https://issues.apache.org/jira/browse/KAFKA-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018528#comment-16018528
]
Kyle Ambroff edited comment on KAFKA-5297 at 5/20/17 4:13 PM:
--
[
https://issues.apache.org/jira/browse/KAFKA-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyle Ambroff updated KAFKA-5297:
Attachment: (was: LogSegmentBenchmark.java)
> Broker can take a long time to shut down if there
[
https://issues.apache.org/jira/browse/KAFKA-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyle Ambroff updated KAFKA-5297:
Attachment: LogSegmentBenchmark.java
> Broker can take a long time to shut down if there are many ac
[
https://issues.apache.org/jira/browse/KAFKA-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyle Ambroff updated KAFKA-5297:
Issue Type: Bug (was: Improvement)
> Broker can take a long time to shut down if there are many act
GitHub user ambroff opened a pull request:
https://github.com/apache/kafka/pull/3110
KAFKA-5297: Reduce time required for shutdown
Avoid reopening and recreating page mappings for index files during
truncation unless it's required by the platform.
In my tests this increa
[
https://issues.apache.org/jira/browse/KAFKA-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018542#comment-16018542
]
ASF GitHub Bot commented on KAFKA-5297:
---
GitHub user ambroff opened a pull request:
[
https://issues.apache.org/jira/browse/KAFKA-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018581#comment-16018581
]
Jorge Quilcate commented on KAFKA-5266:
---
I like 'to-current', I'll implement it.
On
Raymond Conn created KAFKA-5298:
---
Summary: MirrorMaker deadlocks with missing topics
Key: KAFKA-5298
URL: https://issues.apache.org/jira/browse/KAFKA-5298
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018675#comment-16018675
]
Raymond Conn commented on KAFKA-3450:
-
Also it looks like if the {{max.block.ms}} is g
Jyoti created KAFKA-5299:
Summary: MirrorMaker with New.consumer doesn't consume message
from multiple topics whitelisted
Key: KAFKA-5299
URL: https://issues.apache.org/jira/browse/KAFKA-5299
Project: Kafka
GitHub user kkonstantine opened a pull request:
https://github.com/apache/kafka/pull/3111
HOTFIX: Increase timeouts in distributed connect tests.
* There's considerably increased logging in DEBUG mode due to the class
scanning
performed with the new isolation scheme.
You can
20 matches
Mail list logo
