[jira] [Created] (KAFKA-9318) Kafka Connect. Add map entry value extraction SMT

Piotr Smolinski created KAFKA-9318: -- Summary: Kafka Connect. Add map entry value extraction SMT Key: KAFKA-9318 URL: https://issues.apache.org/jira/browse/KAFKA-9318 Project: Kafka Issue Typ

[jira] [Created] (KAFKA-8978) When TLS is applied, broker sends the response frame length in separate TLS packet

Piotr Smolinski created KAFKA-8978: -- Summary: When TLS is applied, broker sends the response frame length in separate TLS packet Key: KAFKA-8978 URL: https://issues.apache.org/jira/browse/KAFKA-8978

[jira] [Created] (KAFKA-8979) Fetch response is frequently split into multiple TCP/IP packets

Piotr Smolinski created KAFKA-8979: -- Summary: Fetch response is frequently split into multiple TCP/IP packets Key: KAFKA-8979 URL: https://issues.apache.org/jira/browse/KAFKA-8979 Project: Kafka

[jira] [Commented] (KAFKA-8978) When TLS is applied, broker sends the response frame length in separate TLS packet

[ https://issues.apache.org/jira/browse/KAFKA-8978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16944504#comment-16944504 ] Piotr Smolinski commented on KAFKA-8978: The actual source of the issue is: [htt

[jira] [Commented] (KAFKA-8979) Fetch response is frequently split into multiple TCP/IP packets

[ https://issues.apache.org/jira/browse/KAFKA-8979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16944525#comment-16944525 ] Piotr Smolinski commented on KAFKA-8979: The problem seems to be in the toSent()

[jira] [Comment Edited] (KAFKA-8978) When TLS is applied, broker sends the response frame length in separate TLS packet

[ https://issues.apache.org/jira/browse/KAFKA-8978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16944504#comment-16944504 ] Piotr Smolinski edited comment on KAFKA-8978 at 10/4/19 9:07 PM: --

[jira] [Created] (KAFKA-9067) BigDecimal conversion unnecessarily enforces the scale

Piotr Smolinski created KAFKA-9067: -- Summary: BigDecimal conversion unnecessarily enforces the scale Key: KAFKA-9067 URL: https://issues.apache.org/jira/browse/KAFKA-9067 Project: Kafka Iss

[jira] [Created] (KAFKA-10062) Add a method to retrieve the current timestamp as known by the Streams app

Piotr Smolinski created KAFKA-10062: --- Summary: Add a method to retrieve the current timestamp as known by the Streams app Key: KAFKA-10062 URL: https://issues.apache.org/jira/browse/KAFKA-10062 Proj

[jira] [Commented] (KAFKA-13372) failed authentication due to: SSL handshake failed

[ https://issues.apache.org/jira/browse/KAFKA-13372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428084#comment-17428084 ] Piotr Smolinski commented on KAFKA-13372: - Try checking the TLS server endpoint 

[jira] [Commented] (KAFKA-10062) Add a method to retrieve the current timestamp as known by the Streams app

[ https://issues.apache.org/jira/browse/KAFKA-10062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17136432#comment-17136432 ] Piotr Smolinski commented on KAFKA-10062: - The motivation is to use the same sou

[jira] [Commented] (KAFKA-10062) Add a method to retrieve the current timestamp as known by the Streams app

[ https://issues.apache.org/jira/browse/KAFKA-10062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17136446#comment-17136446 ] Piotr Smolinski commented on KAFKA-10062: - BTW, the SystemTime class might also

[jira] [Created] (KAFKA-10176) kafka-topics command requires --zookeeper for --alter --topic --config

Piotr Smolinski created KAFKA-10176: --- Summary: kafka-topics command requires --zookeeper for --alter --topic --config Key: KAFKA-10176 URL: https://issues.apache.org/jira/browse/KAFKA-10176 Project:

[jira] [Commented] (KAFKA-10176) kafka-topics command requires --zookeeper for --alter --topic --config

[ https://issues.apache.org/jira/browse/KAFKA-10176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140272#comment-17140272 ] Piotr Smolinski commented on KAFKA-10176: - I raised the corresponding ticket for

[jira] [Resolved] (KAFKA-10176) kafka-topics command requires --zookeeper for --alter --topic --config

[ https://issues.apache.org/jira/browse/KAFKA-10176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Smolinski resolved KAFKA-10176. - Resolution: Won't Fix Closing, as the feature has been deprecated in Kafka 0.9 and the p

[jira] [Created] (KAFKA-13607) Cannot use PEM certificate coding when parent defined file-based

Piotr Smolinski created KAFKA-13607: --- Summary: Cannot use PEM certificate coding when parent defined file-based Key: KAFKA-13607 URL: https://issues.apache.org/jira/browse/KAFKA-13607 Project: Kafka

[jira] [Updated] (KAFKA-13607) Cannot use PEM certificate coding when parent defined file-based

[ https://issues.apache.org/jira/browse/KAFKA-13607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Smolinski updated KAFKA-13607: Description: The problem applies to the situation when we create a Kafka client based on

[jira] [Created] (KAFKA-15814) SASL Kerberos authentication cannot be used with load balanced bootstrap

Piotr Smolinski created KAFKA-15814: --- Summary: SASL Kerberos authentication cannot be used with load balanced bootstrap Key: KAFKA-15814 URL: https://issues.apache.org/jira/browse/KAFKA-15814 Projec