in Java
9, *WildFly OpenSSL still out-performs the one shipped in JRE*.
Like in the Java 8 runs, all default configs and settings were used, not
just for Kafka but even the JRE (i.e. no explicit choice of cipher suites).
[1] https://jaitechwriteups.blogspot.com/2017/10/kafka-with-openssl.html
and
releases?
By the way, why June 2018? :)
-Jaikiran
On 09/11/17 3:14 PM, Ismael Juma wrote:
Hi all,
I'm starting this discussion early because of the potential impact.
Kafka 1.0.0 was just released and the focus was on achieving the original
project vision in terms of features pro
Congratulations Onur!
-Jaikiran
On 06/11/17 10:54 PM, Jun Rao wrote:
Hi, everyone,
The PMC of Apache Kafka is pleased to announce a new Kafka committer Onur
Karaman.
Onur's most significant work is the improvement of Kafka controller, which
is the brain of a Kafka cluster. Over tim
Congratulations Kafka team on the release. Happy to see Kafka reach this
milestone. It has been a pleasure using Kafka and also interacting with
the Kafka team.
-Jaikiran
On 01/11/17 7:57 PM, Guozhang Wang wrote:
The Apache Kafka community is pleased to announce the release for Apache
Kafka
I haven't yet had a chance to try out Java 9, but that's definitely on
my TODO list, maybe sometime this weekend.
Thanks for pointing me to KAFKA-2561. I had missed that.
-Jaikiran
On 30/10/17 4:17 PM, Mickael Maison wrote:
Thanks for sharing, very interesting read.
Did you get a
a (and SSL), so I thought I will bring this to their
notice.
[1] https://jaitechwriteups.blogspot.com/2017/10/kafka-with-openssl.html
-Jaikiran
? That way any new RC release
would mean just changing the version number in our dependencies and
being sure it pulls in the right version.
[1]
https://repository.apache.org/content/groups/staging/org/apache/kafka/kafka_2.12/1.0.0/
-Jaikiran
On 24/10/17 6:30 AM, Guozhang Wang wrote:
H
Github user jaikiran closed the pull request at:
https://github.com/apache/kafka/pull/3043
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user jaikiran opened a pull request:
https://github.com/apache/kafka/pull/3050
(trunk) KAFKA-5232 Fix Log.parseTopicPartitionName to take into account dot
character in topic names of deleted topics
The commit here contains a fix and a test case for the issue reported in
[
https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009314#comment-16009314
]
jaikiran pai commented on KAFKA-5232:
-
One of the crude (but easy) way to repro
[
https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jaikiran pai updated KAFKA-5232:
Status: Patch Available (was: Open)
I just submitted a PR which contains a fix and includes a
GitHub user jaikiran opened a pull request:
https://github.com/apache/kafka/pull/3043
KAFKA-5232 Fix Log.parseTopicPartitionName to take into account dot
character in topic names of deleted topics
The commit here contains a fix and testcase for the issue reported in
https
[
https://issues.apache.org/jira/browse/KAFKA-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jaikiran pai updated KAFKA-5232:
Description:
We are using 0.10.2.0 (but this is reproducible even with 0.10.2.1 and latest
jaikiran pai created KAFKA-5232:
---
Summary: Kafka broker fails to start if a topic containing dot in
its name is marked for delete but hasn't been deleted during previous uptime
Key: KAFKA-5232
URL:
[
https://issues.apache.org/jira/browse/KAFKA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929414#comment-15929414
]
jaikiran pai commented on KAFKA-4631:
-
Thanks [~hachikuji], am glad this made i
Thank you for pointing me to that JIRA. It indeed is the same issue we
discussed in this thread. I'll keep a watch on that JIRA for the code to
be merged.
-Jaikiran
On Thursday 02 March 2017 07:11 PM, Rajini Sivaram wrote:
This issue is being addressed in KAFKA-4631. See
Jaikiran,
What about
1) create topic
2) create consumer1 and do consumer1.partitionsFor() until it succeeds
3) close consumer1
4) create consumer2 and do consumer2.subscribe()
-James
An update on this. This workaround has worked out fine and our initial
tests so far show that it gets us
onsFor, although looked promising, won't work
out. So, I'm going to go back to the metadata.max.age.ms and fiddle with
it a bit to keep it at a low value (was trying to avoid this, since this
then is applicable throughout the lifetime of that consumer).
[1] https://gist.github.com/jaiki
for this, I'll send
a note on what approach I settled on.
-Jaikiran
On Friday 24 February 2017 12:08 PM, James Cheng wrote:
On Feb 23, 2017, at 10:03 PM, Jaikiran Pai wrote:
(Re)posting this from the user mailing list to dev mailing list, hoping for
some inputs from the Kafka dev
topic creation issue. In our case we are explicitly invoking the create
topic operation via the Java API.
-Jaikiran
ACE level which contribute to this, before filing
a JIRA.
-Jaikiran
Ismael
On Tue, Dec 13, 2016 at 9:32 AM, Jaikiran Pai
wrote:
We happened to run into a disk space usage issue with Kafka 0.10.0.1 (the
version we are using) on one of our production setups this morning. Turns
out (log4
On Tuesday 13 December 2016 03:02 PM, Jaikiran Pai wrote:
log4j.logger.kafka.controller=*TRACE,* controllerAppender
log4j.additivity.kafka.controller=false
log4j.logger.state.change.logger=*TRACE*, stateChangeAppender
log4j.additivity.state.change.logger=false
Is it intentional to have
y.state.change.logger=false
Is it intentional to have this at TRACE level for the default shipped
config instead of having something like INFO or maybe DEBUG?
-Jaikiran
e seems to indicate that this is what's happening, either as per
expected semantics or a possible bug.
-Jaikiran
On Wednesday 02 November 2016 08:39 PM, Ismael Juma wrote:
Maybe https://issues.apache.org/jira/browse/KAFKA-4303?
On 2 Nov 2016 10:15 am, "Jaikiran Pai" wrote:
We have b
n in the logs).
Is this expected that the background heart beat sender thread would be
blocked by poll on the consumer (*our poll timeout is 2 minutes*)? Or
did I misread these logs and stacktraces? Let me know if more
logs/details are needed and I can get them.
-Jaikiran
-1.
I would personally like Kafka core to be limited to the core aspects. I
consider REST server like this more a tooling thing than a core aspect
of Kafka and would like it to be outside of Kafka.
-Jaikiran
On Wednesday 26 October 2016 02:46 AM, Harsha Chintalapani wrote:
Hi All
GitHub user jaikiran opened a pull request:
https://github.com/apache/kafka/pull/1837
MINOR: Update the README.md to include a note about GRADLE_USER_HOME
Trying to build the source and publish it to internal Maven repo, I ran
into an issue that I explain in the mailing list
es in that path instead of ~/.gradle folder.
I'll send a PR to the README.md of the project to add a note about this.
-Jaikiran
On Friday 09 September 2016 09:46 AM, Jaikiran Pai wrote:
I am trying to build Kafka 0.10 branch from source to get a SSL fix
and use it for our internal tests.
rty wrong or is something else wrong? Could one of
you who has successfully uploaded this, help me understand how to do it
and what the mavenUrl should point to?
-Jaikiran
Thank you. Just opened one https://github.com/apache/kafka/pull/1825
-Jaikiran
On Tuesday 06 September 2016 10:12 AM, Manikumar Reddy wrote:
We don't need JIRA for minor PRs. Just prefix "MINOR:" to PR title.
On Tue, Sep 6, 2016 at 9:16 AM, Jaikiran Pai
wrote:
Thanks Ismae
GitHub user jaikiran opened a pull request:
https://github.com/apache/kafka/pull/1825
MINOR: Reduce the log level when the peer isn't authenticated but is using
SSL
The commit here changes the log level of a log message from WARN to DEBUG.
As noted in the mail discussion
On Tuesday 06 September 2016 09:42 AM, Jaikiran Pai wrote:
Hi Todd,
Note that this relies on the fix in KAFKA-4050 and switching the PRNG to
SHA1PRNG.
Thanks, I hadn't noticed that JIRA. I'll make sure we use it in our
setup. However, right now, (intentionally) we have single brok
rs? Either way, this is a good hint and something I
hadn't considered in my setup. I'll see if I can get some GC
logs/metrics on our setup for this. Thanks for the input.
-Jaikiran
Thanks
Tom Crayford
Heroku Kafka
On Sun, Sep 4, 2016 at 6:28 PM, Todd Palino wrote:
We'
. I will see if I can narrow to
this down to something more concrete.
-Jaikiran
That said, switching the message format to the newer option (KIP-31 I
believe?) will result in the brokers not needing to recompress message
batches that are produced. This should result in a significant reducti
Thanks Ismael, I'll raise a PR for this. As a process, is there a JIRA
that's expected to be filed for this before I raise a PR or would this
be OK without a JIRA?
-Jaikiran
On Monday 05 September 2016 03:55 PM, Ismael Juma wrote:
Hi Jaikiran,
I agree that this is a valid configu
s a pretty straightforward change and if this change is something
that sounds right, I can go ahead and submit a PR.
P.S: This is both on 0.9.0.1 and latest 0.10.0.1.
-Jaikiran
know the plans around this, we should be able to come up with a plan
of our own for our product.
-Jaikiran
s a pretty straightforward change and if this change is something
that sounds right, I can go ahead and submit a PR.
P.S: This is both on 0.9.0.1 and latest 0.10.0.1.
-Jaikiran
rowse/KAFKA-3539
If solving issues like these will not involve changes to the API, I
think it's safe to move it out of beta label.
-Jaikiran
On Tuesday 30 August 2016 05:09 PM, Ismael Juma wrote:
Thanks for the feedback everyone. Since Harsha said that he is OK either
way and everyone else
Thank you for explaining that, it makes sense.
-Jaikiran
On Friday 26 August 2016 09:02 PM, Rajini Sivaram wrote:
When a port is configured for SSL, broker expects SSL handshake messages
before any Kafka requests are sent. But since the client is using PLAINTEXT
on an SSL port, the client is
[
https://issues.apache.org/jira/browse/KAFKA-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15439247#comment-15439247
]
jaikiran pai commented on KAFKA-4090:
-
Mailing list discussion is here
h
Hi Rajini,
Just filed a JIRA as suggested
https://issues.apache.org/jira/browse/KAFKA-4090. More comments inline.
On Friday 26 August 2016 07:53 PM, Rajini Sivaram wrote:
Jaikiran,
At the moment there is no client-side configuration parameter to restrict
the maximum request size on clients
jaikiran pai created KAFKA-4090:
---
Summary: JVM runs into OOM if (Java) client uses a SSL port
without setting the security protocol
Key: KAFKA-4090
URL: https://issues.apache.org/jira/browse/KAFKA-4090
n issues. I suspect the value being passed over the channel is
incorrect.
Of course this exception is triggered by a user config error but given
that ends up in a (almost unclear) OOM and causing the JVM to go in a
bad state, is there a way the Kafka Java library can handle this better?
Should I file a JIRA for this? I can share a sample application on
github, if it helps.
-Jaikiran
[
https://issues.apache.org/jira/browse/KAFKA-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426538#comment-15426538
]
jaikiran pai commented on KAFKA-4056:
-
[~mimaison], we ran into this on our sy
Created https://issues.apache.org/jira/browse/KAFKA-4056.
-Jaikiran
On Wednesday 17 August 2016 06:28 PM, Ismael Juma wrote:
Yes, please file a JIRA.
Thanks,
Ismael
On Wed, Aug 17, 2016 at 1:46 PM, Jaikiran Pai
wrote:
Thanks for the inputs.
I think it's fine if Kafka selectively
jaikiran pai created KAFKA-4056:
---
Summary: Kafka logs values of sensitive configs like passwords
Key: KAFKA-4056
URL: https://issues.apache.org/jira/browse/KAFKA-4056
Project: Kafka
Issue Type
Thanks for the inputs.
I think it's fine if Kafka selectively logs values for certain configs
and masks others (the passwords). So from what I understand, this looks
more like a bug where it unintentionally ended up logging these values.
Do you want me to file a JIRA for this?
-Jai
Any opinion about this proposed change?
-Jaikiran
On Tuesday 16 August 2016 02:28 PM, Jaikiran Pai wrote:
We are using 0.9.0.1 of Kafka (Java) libraries for our Kafka consumers
and producers. In one of our consumers, our consumer config had a SSL
specific property which ended up being used
ill end up being useful if only the config
name is logged without the value.
Can I add this as a JIRA and provide a patch?
-Jaikiran
Adding the Kafka dev list to cc, hoping they would answer this question.
-Jaikiran
On Friday 10 June 2016 11:18 AM, Jaikiran Pai wrote:
We are using 0.9.0.1 of Kafka server and (Java) clients. Our (Java)
consumers are assigned to dynamic runtime generated groups i.e. the
consumer group name is
On Monday 16 May 2016 04:52 PM, Rajini Sivaram wrote:
Hi Jaikiran,
1) If you delete a topic with no outstanding sends, you will see one WARN
log entry and the topic is immediately removed from the metadata. If you
delete a topic with outstanding sends, you will see a sequence of WARN logs
until
a/clients/NetworkClient.java
and I think we should be fine if we bumped up the log level of that
class in our logging config to be ERROR, since it doesn't log anything
real useful below that level from that class.
-Jaikiran
On Monday 16 May 2016 02:30 PM, Rajini Sivaram wrote
e
application which reproduces this easily on a 0.9.0.1 setup here
https://gist.github.com/jaikiran/45e9ce510c259267b28821b84105a25a.
Let me know if you need more details about this.
-Jaikiran
[
https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257799#comment-15257799
]
jaikiran pai commented on KAFKA-493:
FWIW - we have been seeing a similar issue in
/7/docs/api/java/net/NetworkInterface.html#getInterfaceAddresses%28%29
after looking up the NetworkInterface by name
http://docs.oracle.com/javase/7/docs/api/java/net/NetworkInterface.html#getByName%28java.lang.String%29
Is this something that could be added as an enhancement?
-Jaikiran
ation+Interface
[2]
https://cwiki.apache.org/confluence/display/KAFKA/Security#Security-Authorization
-Jaikiran
Thanks Jun! That works for us.
-Jaikiran
On Tuesday 22 September 2015 03:03 AM, Jun Rao wrote:
0.8.2.2 is already in maven (
http://mvnrepository.com/artifact/org.apache.kafka/kafka_2.10/0.8.2.2) and
the binary download can be found at
https://www.apache.org/dyn/closer.cgi?path=/kafka/0.8.2.2
Thanks Ewen. This helps partly but not fully since the Kafka runtime
itself isn't published to Maven (unless I looked up at the wrong place)
and thus we cannot boot up Kafka as a process, without the binaries
available somewhere.
-Jaikiran
On Monday 21 September 2015 10:41 AM, Ewen Che
often, which we
can use with the bugs fixed, is really going to help.
Thanks to the Kafka dev team for the work they put in. I don't intend to
sound critical about the project (we really like it). I'm just hoping
that the releases happen more often.
-Jaikiran
mote
consumers to the system just "waiting" for new messages, but there's no
message production to the topics)
-Jaikiran
On Friday 18 September 2015 04:34 AM, Brock Noland wrote:
If you are on Linux, you can use the following approach.
1) Get the pid
2) Find the largest c
tacktraces.
-Jaikiran
On Friday 18 September 2015 04:00 AM, Jun Rao wrote:
The selector is probably not the issue. If there is no incoming traffic,
selector.select(300) won't return until after 300ms.
Thanks,
Jun
On Thu, Sep 17, 2015 at 1:13 PM, Jaikiran Pai
wrote:
Sending this to the
Sending this to the dev list since the Kafka dev team might have more
inputs on this one. Can someone please take a look at the issue noted
below and whether the suggested change makes sense?
-Jaikiran
On Tuesday 15 September 2015 12:03 AM, Jaikiran Pai wrote:
We have been using Kafka for a
On Tuesday 01 September 2015 09:51 AM, Aditya Auradkar wrote:
createTopic should also be fine unless you try to create the same topic
concurrently.
Just to be clear - that would imply the AdminUtils _cannot_ be
considered thread-safe, isn't it?
-Jaikiran
On Mon, Aug 31, 2015 at 3:
Recently there was a discussion that 0.8.2.2 will be released soon to
fix the critical issue with compression. Is that still the plan or has
that been shelved?
-Jaikiran
GitHub user jaikiran opened a pull request:
https://github.com/apache/kafka/pull/138
Log the real exception which triggered a reconnect
The commit here improves the logging in SimpleConsumer to log the real
reason why a reconnect was attempted. Relates to
https://issues.apache.org
the latest?
-Jaikiran
[
https://issues.apache.org/jira/browse/KAFKA-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jaikiran pai updated KAFKA-2405:
Status: Patch Available (was: Open)
Pull request sent https://github.com/apache/kafka/pull/111
GitHub user jaikiran opened a pull request:
https://github.com/apache/kafka/pull/111
KAFKA-2405 Don't kill the JVM on session establishment failure
As noted in the JIRA https://issues.apache.org/jira/browse/KAFKA-2405
currently the KafkaHealthCheck causes the JVM to termina
jaikiran pai created KAFKA-2405:
---
Summary: KafkaHealthCheck kills the JVM in
handleSessionEstablishmentError
Key: KAFKA-2405
URL: https://issues.apache.org/jira/browse/KAFKA-2405
Project: Kafka
Thanks for explaining, Ewen.
-Jaikiran
On Thursday 02 July 2015 02:03 PM, Ewen Cheslack-Postava wrote:
Jaikiran,
After the last KIP discussion, I've been tasked with proposing a policy to
address general rules across all public interfaces including APIs, configs,
metrics, and command
Congratulations Gwen.
Gwen has been very helpful in various places (blogs, user mailing lists)
which has helped me (and I'm sure many others) in using Kafka and even
contributing patches. Very well deserved promotion.
-Jaikiran
On Tuesday 07 July 2015 07:36 AM, Guozhang Wang wrote:
Con
lease instead?
-Jaikiran
On Thursday 02 July 2015 06:27 AM, Ashish Singh wrote:
Hey Guys,
In last KIP hangout, we decided on following path for deprecating
ConsumerOffsetChecker.
1. Add deprecation warning to the tool for one release. In this case, the
warning will be added in 0.9.0.
2. Drop it compl
and
> > written up in a KIP. We can't hard code values that folks won't understand
> > without some clear information about why it is 5000
Ok. I'll read through the KIP process and create a new one.
- Jaikiran
---
Hi Joe,
Comments inline.
On Friday 29 May 2015 12:15 PM, Joe Stein wrote:
see below
On Fri, May 29, 2015 at 2:25 AM, Jaikiran Pai
wrote:
Could someone please look at these few review requests and let me know if
any changes are needed:
https://reviews.apache.org/r/34394/ related to
https
There's also this one https://reviews.apache.org/r/34697/ for
https://issues.apache.org/jira/browse/KAFKA-2221 but it's only been up
since a couple of days and is a fairly minor one.
-Jaikiran
[
https://issues.apache.org/jira/browse/KAFKA-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jaikiran pai updated KAFKA-2221:
Attachment: KAFKA-2221.patch
> Log the entire cause which caused a reconnect in the SimpleConsu
[
https://issues.apache.org/jira/browse/KAFKA-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jaikiran pai updated KAFKA-2221:
Status: Patch Available (was: Open)
> Log the entire cause which caused a reconnect in
[
https://issues.apache.org/jira/browse/KAFKA-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14560354#comment-14560354
]
jaikiran pai commented on KAFKA-2221:
-
Created reviewboard https://reviews.apache
---
Thanks,
Jaikiran Pai
jaikiran pai created KAFKA-2221:
---
Summary: Log the entire cause which caused a reconnect in the
SimpleConsumer
Key: KAFKA-2221
URL: https://issues.apache.org/jira/browse/KAFKA-2221
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jaikiran pai updated KAFKA-1907:
Attachment: KAFKA-1907_2015-05-25_09:18:14.patch
> ZkClient can block controlled shutd
es to reconnect to zoookeeper for a maximum of
5 seconds before cleanly shutting down). I've also checked that shutting down
Kafka first, when zookeeper is still up, works fine too.
Thanks,
Jaikiran Pai
[
https://issues.apache.org/jira/browse/KAFKA-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14557954#comment-14557954
]
jaikiran pai commented on KAFKA-1907:
-
Updated reviewboard https://reviews.apache
[
https://issues.apache.org/jira/browse/KAFKA-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555458#comment-14555458
]
jaikiran pai commented on KAFKA-2201:
-
This might be related
http://
27;ve also checked that shutting down
Kafka first, when zookeeper is still up, works fine too.
Thanks,
Jaikiran Pai
[
https://issues.apache.org/jira/browse/KAFKA-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549796#comment-14549796
]
jaikiran pai commented on KAFKA-1907:
-
Created reviewboard https://reviews.apache
[
https://issues.apache.org/jira/browse/KAFKA-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jaikiran pai updated KAFKA-1907:
Attachment: KAFKA-1907.patch
> ZkClient can block controlled shutdown indefinit
[
https://issues.apache.org/jira/browse/KAFKA-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jaikiran pai updated KAFKA-1907:
Status: Patch Available (was: In Progress)
> ZkClient can block controlled shutdown indefinit
ea6d165d8e5c3146d2c65e8ad1a513308334bf6f
Diff: https://reviews.apache.org/r/34394/diff/
Testing
---
Thanks,
Jaikiran Pai
notes the
next version as 0.8.3-SNAPSHOT.
-Jaikiran
this patch
to incorporate Neha's review comments. This is now ready to be reviewed again.
- Jaikiran Pai
On May 18, 2015, 4:42 a.m., Jaikiran Pai wrote:
>
> ---
> This is an automatically generated e-mail. To reply,
at we default the log directory to data/ in the kafka installation
> > directory and possibly encourage storing kafka data under var/ if it must
> > be overridden for production, by changing this commented out value to
> > /var/kafka-logs?
This has now been addressed to
[
https://issues.apache.org/jira/browse/KAFKA-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547526#comment-14547526
]
jaikiran pai commented on KAFKA-1906:
-
Updated reviewboard https://reviews.apache
[
https://issues.apache.org/jira/browse/KAFKA-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jaikiran pai updated KAFKA-1906:
Attachment: KAFKA-1906_2015-05-18_10:11:12.patch
> Default the Kafka log directory to a relat
[
https://issues.apache.org/jira/browse/KAFKA-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jaikiran pai updated KAFKA-1906:
Status: Patch Available (was: In Progress)
> Default the Kafka log directory to a relative p
here and let me know if they run into any issues.
Thanks,
Jaikiran Pai
help in quickly submitting the changes.
-Jaikiran
On Thursday 30 April 2015 06:42 PM, Ismael Juma wrote:
Hi all,
Kafka currently uses a combination of Review Board and JIRA for
contributions and code review. In my opinion, this makes contribution and
code review a bit harder than it has to be.
I
[
https://issues.apache.org/jira/browse/KAFKA-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332503#comment-14332503
]
jaikiran pai commented on KAFKA-1907:
-
Hi [~nehanarkhede], I submitted a patch
the JIRAs that we
expect to be resolved are indeed resolved and then asking the ZkClient
team to do a release might be something that we should do. If this
sounds good and if someone can point me to the exact JIRAs that need to
be verified, then I can look into this. Let me know.
-Jaikiran
O
1 - 100 of 246 matches
Mail list logo
