[jira] [Created] (KAFKA-12404) Provision to propagate error message from Authorizer to clients
Giri created KAFKA-12404: Summary: Provision to propagate error message from Authorizer to clients Key: KAFKA-12404 URL: https://issues.apache.org/jira/browse/KAFKA-12404 Project: Kafka Issue Type: Improvement Components: clients, protocol, security Affects Versions: 2.6.0 Reporter: Giri Only some of the APIs (create topic, delete topic ) carry forward the error thrown from the Authorizer to the client. It would be better to convey specific error message when available instead of generic error message. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-4822) Kafka producer implementation without additional threads and control of when data is sent to kafka (similar to sync producer of 0.8.)
[ https://issues.apache.org/jira/browse/KAFKA-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giri updated KAFKA-4822: Summary: Kafka producer implementation without additional threads and control of when data is sent to kafka (similar to sync producer of 0.8.) (was: Kafka producer implementation without additional threads and control of when data is sent to kafka, similar to sync producer of 0.8.) > Kafka producer implementation without additional threads and control of when > data is sent to kafka (similar to sync producer of 0.8.) > - > > Key: KAFKA-4822 > URL: https://issues.apache.org/jira/browse/KAFKA-4822 > Project: Kafka > Issue Type: New Feature > Components: producer >Affects Versions: 0.9.0.0, 0.9.0.1, 0.10.0.0, 0.10.0.1, 0.10.1.0, 0.10.1.1 >Reporter: Giri >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KAFKA-4822) Kafka producer implementation without additional threads and control of when data is sent to kafka, similar to sync producer of 0.8.
[ https://issues.apache.org/jira/browse/KAFKA-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giri updated KAFKA-4822: Summary: Kafka producer implementation without additional threads and control of when data is sent to kafka, similar to sync producer of 0.8. (was: Kafka producer implementation without additional threads, similar to sync producer of 0.8.) > Kafka producer implementation without additional threads and control of when > data is sent to kafka, similar to sync producer of 0.8. > > > Key: KAFKA-4822 > URL: https://issues.apache.org/jira/browse/KAFKA-4822 > Project: Kafka > Issue Type: New Feature > Components: producer >Affects Versions: 0.9.0.0, 0.9.0.1, 0.10.0.0, 0.10.0.1, 0.10.1.0, 0.10.1.1 >Reporter: Giri >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KAFKA-4822) Kafka producer implementation without additional threads, similar to sync producer of 0.8.
[ https://issues.apache.org/jira/browse/KAFKA-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890139#comment-15890139 ] Giri commented on KAFKA-4822: - A producer implementation with finer control will be helpful in the above like cases. > Kafka producer implementation without additional threads, similar to sync > producer of 0.8. > -- > > Key: KAFKA-4822 > URL: https://issues.apache.org/jira/browse/KAFKA-4822 > Project: Kafka > Issue Type: New Feature > Components: producer >Affects Versions: 0.9.0.0, 0.9.0.1, 0.10.0.0, 0.10.0.1, 0.10.1.0, 0.10.1.1 >Reporter: Giri >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KAFKA-4822) Kafka producer implementation without additional threads, similar to sync producer of 0.8.
[ https://issues.apache.org/jira/browse/KAFKA-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890130#comment-15890130 ] Giri commented on KAFKA-4822: - i understand that the sync can be achieved by the above workaround, but still another thread will be spawned per producer to send the data in background. i have a case where a predefined set of threads (40 to 80 depending on the machine conf) receive data from a persistent medium and this data is sent to kafka (1 producer per thread) and i have to commit the position of the persistent medium to protect against restarts. I have achieved this in 0.8 sync producer by storing the data from persistent medium in list and after some content is cached i sent to kafka as batch and committed the position in the persistent medium. But now i do not have explicit control over when the data will be sent to kafka as data is completely handled by the new network thread and also the batch full and new batch are not visible to user (lost at KafkaProducer.doSend()). > Kafka producer implementation without additional threads, similar to sync > producer of 0.8. > -- > > Key: KAFKA-4822 > URL: https://issues.apache.org/jira/browse/KAFKA-4822 > Project: Kafka > Issue Type: New Feature > Components: producer >Affects Versions: 0.9.0.0, 0.9.0.1, 0.10.0.0, 0.10.0.1, 0.10.1.0, 0.10.1.1 >Reporter: Giri >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KAFKA-4822) Kafka producer implementation without additional threads, similar to sync producer of 0.8.
[ https://issues.apache.org/jira/browse/KAFKA-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giri updated KAFKA-4822: Priority: Minor (was: Major) > Kafka producer implementation without additional threads, similar to sync > producer of 0.8. > -- > > Key: KAFKA-4822 > URL: https://issues.apache.org/jira/browse/KAFKA-4822 > Project: Kafka > Issue Type: New Feature > Components: producer >Affects Versions: 0.9.0.0, 0.9.0.1, 0.10.0.0, 0.10.0.1, 0.10.1.0, 0.10.1.1 >Reporter: Giri >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KAFKA-4822) Kafka producer implementation without additional threads, similar to sync producer of 0.8.
[ https://issues.apache.org/jira/browse/KAFKA-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giri updated KAFKA-4822: Affects Version/s: 0.9.0.0 0.9.0.1 0.10.0.0 0.10.0.1 0.10.1.0 0.10.1.1 > Kafka producer implementation without additional threads, similar to sync > producer of 0.8. > -- > > Key: KAFKA-4822 > URL: https://issues.apache.org/jira/browse/KAFKA-4822 > Project: Kafka > Issue Type: New Feature > Components: producer >Affects Versions: 0.9.0.0, 0.9.0.1, 0.10.0.0, 0.10.0.1, 0.10.1.0, 0.10.1.1 >Reporter: Giri > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KAFKA-4822) Kafka producer implementation without additional threads, similar to sync producer of 0.8.
Giri created KAFKA-4822: --- Summary: Kafka producer implementation without additional threads, similar to sync producer of 0.8. Key: KAFKA-4822 URL: https://issues.apache.org/jira/browse/KAFKA-4822 Project: Kafka Issue Type: New Feature Components: producer Reporter: Giri -- This message was sent by Atlassian JIRA (v6.3.15#6346)
