[
https://issues.apache.org/jira/browse/KAFKA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14702992#comment-14702992
]
James Lent commented on KAFKA-1387:
---
Your approach sounds much simpler than mine (which
[
https://issues.apache.org/jira/browse/KAFKA-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani reassigned KAFKA-2441:
-
Assignee: Sriharsha Chintalapani
SSL/TLS in official docs
[
https://issues.apache.org/jira/browse/KAFKA-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani resolved KAFKA-1685.
---
Resolution: Fixed
Implement TLS/SSL tests
---
[
https://issues.apache.org/jira/browse/KAFKA-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703049#comment-14703049
]
Alex Etling commented on KAFKA-1070:
Thank you for the help! I appreciate it.
[
https://issues.apache.org/jira/browse/KAFKA-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani resolved KAFKA-1691.
---
Resolution: Fixed
new java consumer needs ssl support as a client
[
https://issues.apache.org/jira/browse/KAFKA-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703134#comment-14703134
]
Jun Rao commented on KAFKA-1691:
This is done as part of KAFKA-1690.
new java consumer
[
https://issues.apache.org/jira/browse/KAFKA-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1756:
Fix Version/s: (was: 0.8.3)
never allow the replica fetch size to be less than the max message
[
https://issues.apache.org/jira/browse/KAFKA-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703184#comment-14703184
]
Ismael Juma commented on KAFKA-2411:
[~gwenshap], [~junrao] and [~harsha_ch], I filed
[
https://issues.apache.org/jira/browse/KAFKA-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703183#comment-14703183
]
Gwen Shapira commented on KAFKA-2444:
-
[~aauradkar] - can you take a look?
Fail
[
https://issues.apache.org/jira/browse/KAFKA-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1489:
Labels: (was: newbie)
Global threshold on data retention size
[
https://issues.apache.org/jira/browse/KAFKA-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1489:
Fix Version/s: (was: 0.8.3)
Global threshold on data retention size
[
https://issues.apache.org/jira/browse/KAFKA-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703240#comment-14703240
]
Gwen Shapira commented on KAFKA-934:
I'm really not sure. I removed it from 0.8.3 since
Even under the second option, it sounds like we still cannot include the
code and doc changes in one commit?
Guozhang
On Wed, Aug 19, 2015 at 8:56 AM, Manikumar Reddy ku...@nmsworks.co.in
wrote:
oops.. i did not check Ismail's mail.
On Wed, Aug 19, 2015 at 9:25 PM, Manikumar Reddy
[
https://issues.apache.org/jira/browse/KAFKA-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703163#comment-14703163
]
ASF GitHub Bot commented on KAFKA-2411:
---
GitHub user ijuma opened a pull request:
Hi Guozhang,
Thank you for writing the KIP-28 up. (Hope this is the right thread for me to
post some comments. :)
I still have some confusing about the implementation of the Processor:
1. why do we maintain a separate consumer and producer for each worker thread?
— from my understanding,
[
https://issues.apache.org/jira/browse/KAFKA-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1904:
Fix Version/s: (was: 0.8.3)
run sanity failed test
--
[
https://issues.apache.org/jira/browse/KAFKA-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1678:
Fix Version/s: (was: 0.8.3)
add new options for reassign partition to better manager dead
[
https://issues.apache.org/jira/browse/KAFKA-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1714:
Fix Version/s: (was: 0.8.3)
more better bootstrapping of the gradle-wrapper.jar
[
https://issues.apache.org/jira/browse/KAFKA-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1665:
Fix Version/s: (was: 0.8.3)
controller state gets stuck in message after execute
[
https://issues.apache.org/jira/browse/KAFKA-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1659:
Fix Version/s: (was: 0.8.3)
Ability to cleanly abort the KafkaProducer
[
https://issues.apache.org/jira/browse/KAFKA-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1675:
Fix Version/s: (was: 0.8.3)
bootstrapping tidy-up
-
oops.. i did not check Ismail's mail.
On Wed, Aug 19, 2015 at 9:25 PM, Manikumar Reddy ku...@nmsworks.co.in
wrote:
Hi,
We have raised a Apache Infra ticket for migrating site docs from svn
- git .
Currently, the gitwcsub client only supports using the asf-site
branch for site docs.
[
https://issues.apache.org/jira/browse/KAFKA-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1694:
Fix Version/s: (was: 0.8.3)
kafka command line and centralized operations
[
https://issues.apache.org/jira/browse/KAFKA-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1825:
Fix Version/s: (was: 0.8.3)
leadership election state is stale and never recovers without all
[
https://issues.apache.org/jira/browse/KAFKA-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-686:
---
Fix Version/s: (was: 0.8.3)
0.8 Kafka broker should give a better error message when running
[
https://issues.apache.org/jira/browse/KAFKA-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1561:
Fix Version/s: (was: 0.8.3)
Data Loss for Incremented Replica Factor and Leader Election
Hi all,
It looks like it's not feasible to update the code and website in the same
commit given existing limitations of the Apache infra:
[
https://issues.apache.org/jira/browse/KAFKA-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703214#comment-14703214
]
Sriharsha Chintalapani commented on KAFKA-934:
--
[~gwenshap] are we still
[
https://issues.apache.org/jira/browse/KAFKA-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-2218:
Fix Version/s: (was: 0.8.3)
reassignment tool needs to parse and validate the json
[
https://issues.apache.org/jira/browse/KAFKA-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-2219:
Fix Version/s: (was: 0.8.3)
reassign partition fails with offset 0 being asked for but
[
https://issues.apache.org/jira/browse/KAFKA-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-2180:
Fix Version/s: (was: 0.8.3)
topics never create on brokers though it succeeds in tool and is
[
https://issues.apache.org/jira/browse/KAFKA-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1753:
Fix Version/s: (was: 0.8.3)
add --decommission-broker option
[
https://issues.apache.org/jira/browse/KAFKA-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1715:
Fix Version/s: (was: 0.8.3)
better advertising of the bound and working interface
Yeah, so the way this works in few other projects I worked on is:
* The code repo has a /docs directory with the latest revision of the docs
(not multiple versions, just one that matches the latest state of code)
* When you submit a patch that requires doc modification, you modify all
relevant
Gwen Shapira created KAFKA-2445:
---
Summary: Failed test: kafka.producer.ProducerTest
testSendWithDeadBroker FAILED
Key: KAFKA-2445
URL: https://issues.apache.org/jira/browse/KAFKA-2445
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1420:
Fix Version/s: (was: 0.8.3)
Replace AdminUtils.createOrUpdateTopicPartitionAssignmentPathInZK
[
https://issues.apache.org/jira/browse/KAFKA-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1351:
Fix Version/s: (was: 0.8.3)
String.format is very expensive in Scala
[
https://issues.apache.org/jira/browse/KAFKA-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-1751:
Fix Version/s: (was: 0.8.3)
handle broker not exists and topic not exists scenarios
I should clarify: it's not possible unless we add an additional step that
moves the docs from the code repo to the website repo.
Ismael
On Wed, Aug 19, 2015 at 4:42 PM, Ismael Juma ism...@juma.me.uk wrote:
Hi all,
It looks like it's not feasible to update the code and website in the same
Hi,
We have raised a Apache Infra ticket for migrating site docs from svn -
git .
Currently, the gitwcsub client only supports using the asf-site branch
for site docs.
Infra team is suggesting to create new git repo for site docs.
Infra ticket here:
GitHub user ijuma opened a pull request:
https://github.com/apache/kafka/pull/151
KAFKA-2411; remove usage of blocking channel
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ijuma/kafka
Gwen Shapira created KAFKA-2444:
---
Summary: Fail test: kafka.api.QuotasTest
testThrottledProducerConsumer FAILED
Key: KAFKA-2444
URL: https://issues.apache.org/jira/browse/KAFKA-2444
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703192#comment-14703192
]
Aditya Auradkar commented on KAFKA-2444:
[~gwenshap] will do
Fail test:
[
https://issues.apache.org/jira/browse/KAFKA-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-2339:
Fix Version/s: (was: 0.8.3)
broker becomes unavailable if bad data is passed through the
[
https://issues.apache.org/jira/browse/KAFKA-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703132#comment-14703132
]
Jun Rao commented on KAFKA-1685:
This is done as part of KAFKA-1690.
Implement TLS/SSL
yes. we can not. we need two separate github PRs for code and doc changes.
On Wed, Aug 19, 2015 at 9:35 PM, Guozhang Wang wangg...@gmail.com wrote:
Even under the second option, it sounds like we still cannot include the
code and doc changes in one commit?
Guozhang
On Wed, Aug 19, 2015 at
[
https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703327#comment-14703327
]
Aseem Bansal edited comment on KAFKA-2425 at 8/19/15 4:47 PM:
--
The kafka review board returns a 500.
https://reviews.apache.org/r/36652
returns this :
Something broke! (Error 500) It appears something broke when you tried to
go to here. This is either a bug in Review Board or a server configuration
error. Please report this to your administrator
Ashish K Singh created KAFKA-2447:
-
Summary: Add capability to KafkaLog4jAppender to be able to use SSL
Key: KAFKA-2447
URL: https://issues.apache.org/jira/browse/KAFKA-2447
Project: Kafka
On Aug. 19, 2015, 5:48 a.m., Joel Koshy wrote:
core/src/main/scala/kafka/network/SocketServer.scala, line 265
https://reviews.apache.org/r/36652/diff/4/?file=1039545#file1039545line265
I'm also unclear at this point on what the right thing to do here would
be - i.e., log and
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36652/#review95868
---
core/src/main/scala/kafka/network/SocketServer.scala (line 264)
[
https://issues.apache.org/jira/browse/KAFKA-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703327#comment-14703327
]
Aseem Bansal commented on KAFKA-2425:
-
Sorry [~omkreddy] but not getting the time
Hi Guozhang,
Thank you for writing the KIP-28 up. (Hope this is the right thread for me to
post some comments. :)
I still have some confusing about the implementation of the Processor:
1. why do we maintain a separate consumer and producer for each worker thread?
— from my understanding,
Aditya Auradkar created KAFKA-2446:
--
Summary: KAFKA-2205 causes existing Topic config changes to be lost
Key: KAFKA-2446
URL: https://issues.apache.org/jira/browse/KAFKA-2446
Project: Kafka
+1 to what Gwen has suggested. This is what we follow in Flume.
All the latest doc changes are in git, once ready you move changes to
svn to update website.
The only catch is, when you need to update specific changes to website
outside release cycle, need to be a bit careful :)
On Wed, Aug 19,
[
https://issues.apache.org/jira/browse/KAFKA-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703437#comment-14703437
]
Ismael Juma commented on KAFKA-2417:
I'm listing what is already tested below:
*
[
https://issues.apache.org/jira/browse/KAFKA-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703539#comment-14703539
]
Parth Brahmbhatt commented on KAFKA-2145:
-
[~junrao] 3 week reminder ping to
[
https://issues.apache.org/jira/browse/KAFKA-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703691#comment-14703691
]
Guozhang Wang commented on KAFKA-2084:
--
[~auradkar] [~jjkoshy] ClientQuotaManagerTest
[
https://issues.apache.org/jira/browse/KAFKA-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703537#comment-14703537
]
Parth Brahmbhatt commented on KAFKA-2210:
-
[~junrao] [~ijuma] [~eribeiro] One week
[
https://issues.apache.org/jira/browse/KAFKA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703532#comment-14703532
]
Guozhang Wang commented on KAFKA-1387:
--
[~jwlent55] I agree that this fix may be just
Ok, thanks everyone for the feedback. Based on the feedback, I'd recommend
that we do an 0.8.2.2 release including just the two snappy bug fixes.
Jun
On Tue, Aug 18, 2015 at 12:59 PM, Gwen Shapira g...@confluent.io wrote:
Any objections if I leave KAFKA-2114 (setting min.insync.replicas
[
https://issues.apache.org/jira/browse/KAFKA-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703701#comment-14703701
]
Aditya Auradkar commented on KAFKA-2084:
[~guozhang] Will do
byte rate metrics
[
https://issues.apache.org/jira/browse/KAFKA-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-2444.
--
Resolution: Duplicate
Other one is already assigned, not sure if anyone was
[
https://issues.apache.org/jira/browse/KAFKA-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703751#comment-14703751
]
Jun Rao commented on KAFKA-1690:
[~sriharsha], a couple of other followup items. (1)
[
https://issues.apache.org/jira/browse/KAFKA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703767#comment-14703767
]
Flavio Junqueira commented on KAFKA-1387:
-
I'm indeed proposing to get rid of
[
https://issues.apache.org/jira/browse/KAFKA-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703771#comment-14703771
]
Sriharsha Chintalapani commented on KAFKA-1690:
---
[~junrao] do you want send
[
https://issues.apache.org/jira/browse/KAFKA-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703881#comment-14703881
]
Gwen Shapira commented on KAFKA-2367:
-
We haven't really seen an alternative to Avro.
[
https://issues.apache.org/jira/browse/KAFKA-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703890#comment-14703890
]
Jay Kreps commented on KAFKA-2367:
--
Yeah makes sense. Obviously no one is advocating the
[
https://issues.apache.org/jira/browse/KAFKA-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703921#comment-14703921
]
Joel Koshy commented on KAFKA-2084:
---
I pushed a trivial commit to address this. However,
[
https://issues.apache.org/jira/browse/KAFKA-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703940#comment-14703940
]
Guozhang Wang commented on KAFKA-2084:
--
That would be best. Problem is that we
[
https://issues.apache.org/jira/browse/KAFKA-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703965#comment-14703965
]
Joel Koshy commented on KAFKA-2084:
---
Actually I did not mean full-fledged
[
https://issues.apache.org/jira/browse/KAFKA-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Auradkar resolved KAFKA-2085.
Resolution: Fixed
Resolved in KAFKA-2084
Return delay time in QuotaViolationException
[
https://issues.apache.org/jira/browse/KAFKA-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KAFKA-2097 started by Aditya Auradkar.
--
Implement request delays for quota violations
[
https://issues.apache.org/jira/browse/KAFKA-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14704002#comment-14704002
]
Geoff Anderson commented on KAFKA-2330:
---
rsync_excludes should maybe include
Geoff Anderson created KAFKA-2449:
-
Summary: Update mirror maker (MirrorMaker) docs
Key: KAFKA-2449
URL: https://issues.apache.org/jira/browse/KAFKA-2449
Project: Kafka
Issue Type: Bug
Gwen: I remembered it wrong. We would not need another round of voting.
On Wed, Aug 19, 2015 at 3:06 PM, Gwen Shapira g...@confluent.io wrote:
Looking back at this thread, the +1 mention same repo, so I'm not sure a
new vote is required.
On Wed, Aug 19, 2015 at 3:00 PM, Guozhang Wang
[
https://issues.apache.org/jira/browse/KAFKA-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703871#comment-14703871
]
Jay Kreps commented on KAFKA-2367:
--
Okay there are clearly divergent opinions here.
[
https://issues.apache.org/jira/browse/KAFKA-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Auradkar resolved KAFKA-2293.
Resolution: Fixed
Committed to trunk
IllegalFormatConversionException in Partition.scala
[
https://issues.apache.org/jira/browse/KAFKA-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Auradkar resolved KAFKA-2097.
Resolution: Fixed
Resolved in KAFKA-2084
Implement request delays for quota violations
[
https://issues.apache.org/jira/browse/KAFKA-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703901#comment-14703901
]
Ewen Cheslack-Postava commented on KAFKA-2367:
--
Yes.
Add Copycat runtime
[
https://issues.apache.org/jira/browse/KAFKA-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703763#comment-14703763
]
Flavio Junqueira commented on KAFKA-873:
hey [~granthenke], I was thinking we could
+1 for this. Also we can put description of what changes might be required
to make in the current running release. But that might be cumbersome. Just
a thought.
Thanks,
Mayuresh
On Wed, Aug 19, 2015 at 2:29 PM, Jiangjie Qin j...@linkedin.com.invalid
wrote:
I am thinking can we put some notes
Looking back at this thread, the +1 mention same repo, so I'm not sure a
new vote is required.
On Wed, Aug 19, 2015 at 3:00 PM, Guozhang Wang wangg...@gmail.com wrote:
So I think we have two different approaches here. The original proposal
from Aseem is to move website from SVN to a separate
[
https://issues.apache.org/jira/browse/KAFKA-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiangjie Qin updated KAFKA-2448:
Assignee: Flavio Junqueira
BrokerChangeListener missed broker id path ephemeral node deletion
[
https://issues.apache.org/jira/browse/KAFKA-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiangjie Qin updated KAFKA-2448:
Description:
When a broker get bounced, ideally the sequence should be like this:
1.1. Broker
I am thinking can we put some notes in commit message when commit a patch
which introduces introduce some API change or backward compatible change?
It mainly serves two purposes:
1. Easier for people to track the changes they need to make to run a new
version
2. Easier for us to write the release
So I think we have two different approaches here. The original proposal
from Aseem is to move website from SVN to a separate Git repo, and hence
have separate commits on code / doc changes. For that we have accumulated
enough binging +1s to move on; Gwen's proposal is to move website into the
same
Jiangjie Qin created KAFKA-2448:
---
Summary: BrokerChangeListener missed broker id path ephemeral node
deletion event.
Key: KAFKA-2448
URL: https://issues.apache.org/jira/browse/KAFKA-2448
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703831#comment-14703831
]
Jiangjie Qin commented on KAFKA-2448:
-
[~fpj] This issue is potentially related to
[
https://issues.apache.org/jira/browse/KAFKA-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14704011#comment-14704011
]
Gwen Shapira commented on KAFKA-2330:
-
Please add to the README that we need
[
https://issues.apache.org/jira/browse/KAFKA-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14704112#comment-14704112
]
Gwen Shapira commented on KAFKA-2330:
-
+1 and pushed to trunk.
Thanks for the
[
https://issues.apache.org/jira/browse/KAFKA-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-2330:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Vagrantfile sets global configs
[
https://issues.apache.org/jira/browse/KAFKA-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-1688.
Resolution: Duplicate
Closing this since it's being handled in KAFKA-2210, KAFKA-2211, and KAFKA-2212.
On July 21, 2015, 1:58 p.m., Ismael Juma wrote:
clients/src/main/java/org/apache/kafka/common/utils/AppInfoParser.java,
line 27
https://reviews.apache.org/r/35867/diff/4/?file=1011317#file1011317line27
Why isn't this unknown like `version`?
Manikumar Reddy O wrote:
yes we
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/35867/#review95902
---
Can you rebase?
build.gradle (line 389)
[
https://issues.apache.org/jira/browse/KAFKA-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14704033#comment-14704033
]
ASF GitHub Bot commented on KAFKA-2446:
---
GitHub user auradkar opened a pull request:
GitHub user auradkar opened a pull request:
https://github.com/apache/kafka/pull/152
Fix for KAFKA-2446
This bug was introduced while committing KAFKA-2205. Basically, the path
for topic overrides was renamed to topic from topics. However, this causes
existing topic config
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36427/
---
(Updated Aug. 20, 2015, 12:50 a.m.)
Review request for kafka.
Bugs:
[
https://issues.apache.org/jira/browse/KAFKA-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14704066#comment-14704066
]
Ewen Cheslack-Postava commented on KAFKA-2330:
--
Updated reviewboard
[
https://issues.apache.org/jira/browse/KAFKA-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-2330:
-
Attachment: KAFKA-2330_2015-08-19_17:50:17.patch
Vagrantfile sets global configs
1 - 100 of 119 matches
Mail list logo
