Good point Jay. More specifically we were already implementing without the
checked exception, we'd need to override close() in the Serializer and
Deserializer interfaces and omit the throws clause. That definitely makes
them source compatible. Not sure about binary compatibility, I couldn't
find a
On Tue, Apr 28, 2015 at 1:03 PM, Ewen Cheslack-Postava e...@confluent.io
wrote:
Good point Jay. More specifically we were already implementing without the
checked exception, we'd need to override close() in the Serializer and
Deserializer interfaces and omit the throws clause. That definitely
sorry for the previous empty msg.
Jay's idea should work. basically, we override the close method in
Serializer interface.
public interface SerializerT extends Closeable {
@Override
public void close();
}
On Tue, Apr 28, 2015 at 1:10 PM, Steven Wu stevenz...@gmail.com wrote:
On Tue,
[
https://issues.apache.org/jira/browse/KAFKA-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-2153:
--
Attachment: KAFKA-2153.patch
kafka-patch-review tool uploads a patch even if it is empty
[
https://issues.apache.org/jira/browse/KAFKA-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518320#comment-14518320
]
Ashish K Singh commented on KAFKA-2153:
---
Created reviewboard
[
https://issues.apache.org/jira/browse/KAFKA-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish K Singh updated KAFKA-2153:
--
Status: Patch Available (was: Open)
kafka-patch-review tool uploads a patch even if it is
[
https://issues.apache.org/jira/browse/KAFKA-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518314#comment-14518314
]
Jay Kreps commented on KAFKA-1660:
--
Here was the source of my paranoia about r/w locks
[
https://issues.apache.org/jira/browse/KAFKA-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Zhen Wu updated KAFKA-2151:
--
Resolution: Duplicate
Status: Resolved (was: Patch Available)
close this one as
[
https://issues.apache.org/jira/browse/KAFKA-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518484#comment-14518484
]
Jiangjie Qin commented on KAFKA-1660:
-
Thanks for the reference, Jay. Totally agreed.
There are actually two advantages from using SSL/TLS compared to SASL to secure
the communication channel:
* Security: SSL/TLS offers Perfect Forward Secrecy when using EDH to establish
encryption keys. The confidentiality of the past sessions still holds even if
the long term private key of
[
https://issues.apache.org/jira/browse/KAFKA-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518533#comment-14518533
]
Steven Zhen Wu commented on KAFKA-2121:
---
Created reviewboard
[
https://issues.apache.org/jira/browse/KAFKA-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Zhen Wu updated KAFKA-2121:
--
Status: Patch Available (was: Reopened)
prevent potential resource leak in KafkaProducer and
[
https://issues.apache.org/jira/browse/KAFKA-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Zhen Wu updated KAFKA-2121:
--
Attachment: KAFKA-2121.patch
prevent potential resource leak in KafkaProducer and
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/33654/
---
Review request for kafka.
Bugs: KAFKA-2121
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/33645/
---
Review request for kafka.
Bugs: KAFKA-2153
[
https://issues.apache.org/jira/browse/KAFKA-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518343#comment-14518343
]
Emmett Butler commented on KAFKA-2154:
--
I've been able to replicate this issue on
Based on recent suggestion by Joel, I am experimenting with using flush() to
simulate batched-sync behavior.
The essence of my single threaded producer code is :
for (int i = 0; i numRecords;) {
// 1- Send a batch
for(int batchCounter=0; batchCounterbatchSz;
Hey everyone,
Wrote up a KIP to update topic, client and broker configs dynamically via
Zookeeper.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-21+-+Dynamic+Configuration
Please read and provide feedback.
Thanks,
Aditya
PS: I've intentionally kept this discussion separate from KIP-5
Updated KIP-12 is here
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=51809888 . My
new proposal talks about Channel having two layers one is TransportLayer and
another Authentication Layer.
If users want to do authentication without encryption they can use
- Event size = 1kB.
- broker and client running on different machines (identical config, 32
cores, 256GB ram, 6x 1500rpm disk, 10gigEhernet)
- Don't readily have number for old batch sync API for the same params.
But can get it soon. However .. does it matter ?
-roshan
On 4/28/15 6:57
[
https://issues.apache.org/jira/browse/KAFKA-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-1621:
-
Resolution: Fixed
Assignee: Rekha Joshi
Status: Resolved (was: Patch Available)
See https://builds.apache.org/job/KafkaPreCommit/93/changes
Changes:
[nehanarkhede] KAFKA-1621 : Standardize --messages option. Closes #58
--
[...truncated 1275 lines...]
kafka.network.SocketServerTest testMaxConnectionsPerIPOverrides PASSED
[
https://issues.apache.org/jira/browse/KAFKA-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518184#comment-14518184
]
David Hay commented on KAFKA-1835:
--
[~smiklosovic] I've worked around the issue by
I have filed a bug report with Oracle on this issue today. I have not yet been
assigned a bug number. I thought the issue might be of general interest to the
Kafka community and I have a suggestion for a configuration change that works
around the issue in case other people tun into it.
Guys,
A quick summary of our today's meeting.
There were no additional issues/questions. The only item about which
we are not 100% sure is multiple instructions for one topic in one
request case.
It was proposed by Jun to explain reasons behind not allowing users doing
that again
here in mailing
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/33620/
---
Review request for kafka.
Bugs: KAFKA-1690
Thank you for your reply, Gwen.
1. Complex rule systems can be difficult to reason about and therefore end up
being less secure. The rule Deny always wins is very easy to grasp.
Yes, I'm agreed with your point: we should not make the rule complex.
2. We currently don't have any mechanism for
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/30196/
---
(Updated April 28, 2015, 5:28 p.m.)
Review request for kafka and Joel Koshy.
[
https://issues.apache.org/jira/browse/KAFKA-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517479#comment-14517479
]
Aditya A Auradkar commented on KAFKA-1886:
--
Updated reviewboard
On Feb. 7, 2015, 4:22 p.m., Neha Narkhede wrote:
core/src/test/scala/unit/kafka/integration/PrimitiveApiTest.scala, line 295
https://reviews.apache.org/r/30196/diff/2/?file=844610#file844610line295
Why do you need the sleep here? We try to avoid blindly sleeping in
Kafka tests
[
https://issues.apache.org/jira/browse/KAFKA-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517489#comment-14517489
]
Aditya Auradkar commented on KAFKA-1886:
[~nehanarkhede] I've updated the patch.
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/33634/
---
Review request for kafka.
Bugs: KAFKA-2129
[
https://issues.apache.org/jira/browse/KAFKA-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517557#comment-14517557
]
Tim Brooks commented on KAFKA-2129:
---
Created reviewboard
[
https://issues.apache.org/jira/browse/KAFKA-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Brooks updated KAFKA-2129:
--
Priority: Major (was: Minor)
Consumer could make multiple concurrent metadata requests
I think recent discussion showed some need for topic namespaces - for
example, Jun's use case for reserving topic names for specific users
discussed under authorization.
I think some discussion should happen on namespaces vs more full-fledged
topic-hierarchy.
I like the simplicity of namespaces,
[
https://issues.apache.org/jira/browse/KAFKA-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Brooks updated KAFKA-2129:
--
Attachment: KAFKA-2129.patch
Consumer could make multiple concurrent metadata requests
[
https://issues.apache.org/jira/browse/KAFKA-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Brooks updated KAFKA-2129:
--
Assignee: Tim Brooks
Status: Patch Available (was: Open)
Consumer could make multiple
[
https://issues.apache.org/jira/browse/KAFKA-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya A Auradkar updated KAFKA-1886:
-
Attachment: KAFKA-1886_2015-04-28_10:27:39.patch
SimpleConsumer swallowing
Hi all,
I've been looking at how a Kafka cluster could be used be deployed so that it
can be used by multiple tenants. Specifically: a scheme where the clients
belonging to each tenant receive the impression they are operating against
their own cluster. The ongoing security and quota work
[
https://issues.apache.org/jira/browse/KAFKA-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517553#comment-14517553
]
Tim Brooks commented on KAFKA-2129:
---
It kind of looks like this is a larger issue than
See https://builds.apache.org/job/Kafka-trunk/481/changes
Changes:
[nehanarkhede] KAFKA-1621 : Standardize --messages option. Closes #58
--
[...truncated 1267 lines...]
kafka.network.SocketServerTest testMaxConnectionsPerIPOverrides PASSED
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/30196/
---
(Updated April 28, 2015, 5:27 p.m.)
Review request for kafka and Joel Koshy.
[
https://issues.apache.org/jira/browse/KAFKA-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517613#comment-14517613
]
Neelesh Srinivas Salian commented on KAFKA-2145:
Had some clarification
[
https://issues.apache.org/jira/browse/KAFKA-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517627#comment-14517627
]
Stefan Miklosovic commented on KAFKA-1835:
--
Is there actually any workaround? I
[
https://issues.apache.org/jira/browse/KAFKA-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517647#comment-14517647
]
Ewen Cheslack-Postava commented on KAFKA-2121:
--
I'd give people some more
Keith Bourgoin created KAFKA-2154:
-
Summary: MetadataResponse is Empty on a Fresh Cluster
Key: KAFKA-2154
URL: https://issues.apache.org/jira/browse/KAFKA-2154
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Bourgoin updated KAFKA-2154:
--
Description:
When I start a fresh cluster using {{bin/kafka-server-start.sh}} and issue a
[
https://issues.apache.org/jira/browse/KAFKA-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517596#comment-14517596
]
Steven Zhen Wu commented on KAFKA-2121:
---
[~ewencp] I am ok to reverse the change on
[
https://issues.apache.org/jira/browse/KAFKA-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neelesh Srinivas Salian reassigned KAFKA-2145:
--
Assignee: Neelesh Srinivas Salian
An option to add topic owners.
[
https://issues.apache.org/jira/browse/KAFKA-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14517659#comment-14517659
]
Ewen Cheslack-Postava commented on KAFKA-1843:
--
A closely related and easily
I suggested the change to Closeable mainly to avoid some verbosity and
redundancy in the code since we have to call close() on multiple components
and without a common interface, the error handling code is repeated. Using
Closeable does make the code cleaner and more maintainable, but the issue
[
https://issues.apache.org/jira/browse/KAFKA-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14516563#comment-14516563
]
Gwen Shapira commented on KAFKA-1928:
-
Updated reviewboard
[
https://issues.apache.org/jira/browse/KAFKA-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1928:
Status: Patch Available (was: In Progress)
Move kafka.network over to using the network classes
Guys,
It seems that there are no open questions left so prior to our weekly call
let me summarize what I'm going to implement as part of phase one for KIP-4.
1. Add 3 new Wire Protocol requests - Create-, Alter- and DeleteTopicRequest
2. Topic requests are batch requests, errors are returned
Hey guys,
You can implement Closable without the checked exception. Having close()
methods throw checked exceptions isn't very useful unless there is a way
for the caller to recover. In this case there really isn't, right?
-Jay
On Mon, Apr 27, 2015 at 5:51 PM, Guozhang Wang wangg...@gmail.com
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/33634/#review81869
---
Ship it!
Your analysis sounds right, looks like the missing
[
https://issues.apache.org/jira/browse/KAFKA-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated KAFKA-1690:
--
Status: Patch Available (was: In Progress)
new java producer needs ssl
[
https://issues.apache.org/jira/browse/KAFKA-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14516587#comment-14516587
]
Sriharsha Chintalapani commented on KAFKA-1690:
---
Created reviewboard
[
https://issues.apache.org/jira/browse/KAFKA-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated KAFKA-1690:
--
Attachment: KAFKA-1690.patch
new java producer needs ssl support as a client
59 matches
Mail list logo
