GitHub user kamilszymanski opened a pull request:
https://github.com/apache/kafka/pull/1722
remove incomplete gradle wrapper infrastructure
Since jar files (including gradle-wrapper.jar) have to be excluded from
source releases current gradle wrapper infrastructure was incomplete re
[
https://issues.apache.org/jira/browse/KAFKA-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418477#comment-15418477
]
Michal Turek commented on KAFKA-3916:
-
Hi Jason and others,
I have finally found the
[
https://issues.apache.org/jira/browse/KAFKA-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418276#comment-15418276
]
William Yu commented on KAFKA-3937:
---
You're referring to the Kafka consumer when you say
Mayuresh,
I was thinking of the following.
If P1 has data and P2 is throttled, we will return empty data for P2 and
send the response back immediately. The follower will issue the next fetch
request immediately, but the leader won't return any data in P2 until the
quota is not exceeded. We are no
Jun Rao created KAFKA-4035:
--
Summary: AclCommand should allow Describe operation on groups
Key: KAFKA-4035
URL: https://issues.apache.org/jira/browse/KAFKA-4035
Project: Kafka
Issue Type: Bug
GitHub user ewencp opened a pull request:
https://github.com/apache/kafka/pull/1721
KAFKA-3845: KIP-75: Add per-connector converters
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ewencp/kafka
kafka-3845-per-connector-converter
Hi,
The only concrete example i can think of is a case for limiting disk usage.
Say, i had something like Connect running that was tracking changes in a
database. Downstream i don't really care about every change, i just want
the latest values, so compaction could be enabled. However, the kafka
cl
[
https://issues.apache.org/jira/browse/KAFKA-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damian Guy reassigned KAFKA-3595:
-
Assignee: Damian Guy
> Add capability to specify replication compact option for stream store
> --
[
https://issues.apache.org/jira/browse/KAFKA-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damian Guy reassigned KAFKA-3452:
-
Assignee: Damian Guy
> Support session windows besides time interval windows
> --
[
https://issues.apache.org/jira/browse/KAFKA-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418352#comment-15418352
]
ASF GitHub Bot commented on KAFKA-3845:
---
GitHub user ewencp opened a pull request:
GitHub user hachikuji opened a pull request:
https://github.com/apache/kafka/pull/1720
KAFKA-4034: Avoid unnecessary consumer coordinator lookup
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hachikuji/kafka KAFKA-4034
Alternat
Hi, Andrey,
One potential benefit of keeping the per partition limit is for Kafka
stream. When reading messages from different partitions, KStream prefers to
read from partitions with smaller timestamps first and only advances the
KStream timestamp when it sees at least one message from every part
Andrey
To make progress, I suggest you keep the partition-level limit in, at least for
now, and keep it on the FetchRequest too.
B
> On 10 Aug 2016, at 18:55, Andrey L. Neporada wrote:
>
> Hi, Jun!
>
> Thanks for feedback!
>
>> On 10 Aug 2016, at 17:42, Jun Rao wrote:
>>
>> Hi, Andrey,
Hi Mayuresh
So, we’re not actually delaying the FetchResponse, on the leader, unless it is
empty i.e. less min.bytes, ready to be sent, for both throttled and
non-thorttled partitions.
So there shouldn’t be any need for the leader to ask the follower to delay. If
there are bytes to be transmit
Github user mweirauch closed the pull request at:
https://github.com/apache/kafka/pull/1625
---
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 e
[
https://issues.apache.org/jira/browse/KAFKA-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damian Guy resolved KAFKA-3909.
---
Resolution: Fixed
> Queryable state for Kafka Streams
> -
>
>
I am 100% pro smart Java clients that support KIP-35 and can use it to
work with newer brokers. If this JIRA makes sense as a step in that
direction, I think its great and remove my objection. I didn't see
anything that looked like a plan toward full forward-backward
compatibility, which is why I
Hi!
> On 12 Aug 2016, at 04:29, Jun Rao wrote:
>
> Hi, Andrey,
>
> One potential benefit of keeping the per partition limit is for Kafka
> stream. When reading messages from different partitions, KStream prefers to
> read from partitions with smaller timestamps first and only advances the
> KSt
Thanks!
Will do.
> On 12 Aug 2016, at 08:29, Ben Stopford wrote:
>
> Andrey
>
> To make progress, I suggest you keep the partition-level limit in, at least
> for now, and keep it on the FetchRequest too.
>
> B
>
That's a good point Jun and I agree that it makes sense to keep both limits
in that case.
Ismael
On Fri, Aug 12, 2016 at 2:29 AM, Jun Rao wrote:
> Hi, Andrey,
>
> One potential benefit of keeping the per partition limit is for Kafka
> stream. When reading messages from different partitions, KSt
[
https://issues.apache.org/jira/browse/KAFKA-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418678#comment-15418678
]
Ismael Juma commented on KAFKA-3937:
[~williamyu], is your topic compressed?
> Kafka
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/1718
---
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 enab
[
https://issues.apache.org/jira/browse/KAFKA-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418685#comment-15418685
]
ASF GitHub Bot commented on KAFKA-4031:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/KAFKA-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-4031:
---
Fix Version/s: (was: 0.10.0.2)
0.10.1.0
> Check DirectBuffer's cleaner to be no
[
https://issues.apache.org/jira/browse/KAFKA-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-4031.
Resolution: Fixed
Reviewer: Ismael Juma
> Check DirectBuffer's cleaner to be not null before u
[
https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418751#comment-15418751
]
Manikumar Reddy commented on KAFKA-3959:
looks like this is done on purpose. Whil
[
https://issues.apache.org/jira/browse/KAFKA-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418766#comment-15418766
]
William Yu edited comment on KAFKA-3937 at 8/12/16 12:43 PM:
-
[
https://issues.apache.org/jira/browse/KAFKA-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418766#comment-15418766
]
William Yu commented on KAFKA-3937:
---
[~ijuma], yes the topic is compressed, are producer
[
https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418819#comment-15418819
]
Ismael Juma commented on KAFKA-3959:
The current behaviour "minimum of (available brok
[
https://issues.apache.org/jira/browse/KAFKA-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418824#comment-15418824
]
Ismael Juma commented on KAFKA-3937:
Seems like this one then. It's the first time we'
[
https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418751#comment-15418751
]
Manikumar Reddy edited comment on KAFKA-3959 at 8/12/16 1:27 PM:
---
[
https://issues.apache.org/jira/browse/KAFKA-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy reassigned KAFKA-4035:
--
Assignee: Manikumar Reddy
> AclCommand should allow Describe operation on groups
>
[
https://issues.apache.org/jira/browse/KAFKA-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418836#comment-15418836
]
William Yu commented on KAFKA-3937:
---
FYI: My brokers and client are both on kafka: 0.9.0
Hi Jason,
It is still not clear to me how adding a callback would help. You could
remove the periodic task, but you would still need to scan the entire cache
to remove the expired offsets. Am i missing something?
Thanks,
Damian
On 11 August 2016 at 10:00, Damian Guy wrote:
> Hi Jason,
>
> Tha
GitHub user omkreddy opened a pull request:
https://github.com/apache/kafka/pull/1723
KAFKA-4035: AclCommand should allow Describe operation on groups
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/omkreddy/kafka KAFKA-4035
Alt
[
https://issues.apache.org/jira/browse/KAFKA-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418906#comment-15418906
]
ASF GitHub Bot commented on KAFKA-4035:
---
GitHub user omkreddy opened a pull request:
[
https://issues.apache.org/jira/browse/KAFKA-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-4035:
---
Status: Patch Available (was: Open)
> AclCommand should allow Describe operation on groups
>
[
https://issues.apache.org/jira/browse/KAFKA-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-4035:
---
Affects Version/s: 0.9.0.0
0.10.0.0
0.10.0.1
> A
Most of the work in the patch is to enhance NetworkClient to maintain api
versions supported by brokers it has connections to. When a broker
disconnects, its api versions info is removed and when it reconnects that
info is fetched again. In short, with these changes Network Client at any
given poin
[
https://issues.apache.org/jira/browse/KAFKA-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418941#comment-15418941
]
Ashish K Singh commented on KAFKA-2629:
---
[~bharatviswa] the way we do it is that for
[
https://issues.apache.org/jira/browse/KAFKA-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418943#comment-15418943
]
Ashish K Singh commented on KAFKA-2629:
---
[~harsha_ch] any thoughts?
> Enable gettin
[
https://issues.apache.org/jira/browse/KAFKA-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-4012:
---
Status: Patch Available (was: Open)
> KerberosShortNamer should implement toString()
> --
Github user hsun-cnnxty closed the pull request at:
https://github.com/apache/kafka/pull/1666
---
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
[
https://issues.apache.org/jira/browse/KAFKA-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418965#comment-15418965
]
ASF GitHub Bot commented on KAFKA-3991:
---
Github user hsun-cnnxty closed the pull req
GitHub user hsun-cnnxty reopened a pull request:
https://github.com/apache/kafka/pull/1666
[KAFKA-3991]: allow MirrorMaker to have custom producer
Please see jira: https://issues.apache.org/jira/browse/KAFKA-3991
You can merge this pull request into a Git repository by running:
[
https://issues.apache.org/jira/browse/KAFKA-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418966#comment-15418966
]
ASF GitHub Bot commented on KAFKA-3991:
---
GitHub user hsun-cnnxty reopened a pull req
Hi,
Can you add me as a contributor to the Kafka project.
Thanks
Shashank
Hi, Andrey,
Why shouldn't the client library do reordering? It seems that if
ReplicaFetcher thread does round-robin, the consumer client should do that
too?
Thanks,
Jun
On Fri, Aug 12, 2016 at 3:56 AM, Andrey L. Neporada <
anepor...@yandex-team.ru> wrote:
> Hi!
>
> > On 12 Aug 2016, at 04:29,
Hi, Damian,
I was just wondering if we should disable size-based retention in the
compact_and_delete mode. So, it sounds like that there could be a use case
for that. Since by default, the size-based retention is infinite, I think
we can just leave the KIP as it is.
Thanks,
Jun
On Fri, Aug 12,
GitHub user resetius opened a pull request:
https://github.com/apache/kafka/pull/1724
[KAFKA-3997] log partition name on truncation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/resetius/kafka KAFKA-3997
Alternatively you can
[
https://issues.apache.org/jira/browse/KAFKA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419025#comment-15419025
]
ASF GitHub Bot commented on KAFKA-3997:
---
GitHub user resetius opened a pull request:
Thanks Jun
On Fri, 12 Aug 2016 at 16:41 Jun Rao wrote:
> Hi, Damian,
>
> I was just wondering if we should disable size-based retention in the
> compact_and_delete mode. So, it sounds like that there could be a use case
> for that. Since by default, the size-based retention is infinite, I think
Hi All,
I am new to the Kafka community group development and was wondering how do I
get my pull request reviewed/processed?
https://github.com/apache/kafka/pull/1539
Am I missing any steps or is it just the backlog?
Thanks,Jayesh
[
https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419057#comment-15419057
]
Onur Karaman commented on KAFKA-3959:
-
Perfect timing! [~toddpalino] and I hit this be
[
https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419066#comment-15419066
]
James Cheng commented on KAFKA-3959:
You mentioned
{bq}
but __consumer_offsets append
[
https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419066#comment-15419066
]
James Cheng edited comment on KAFKA-3959 at 8/12/16 4:12 PM:
-
Hi!
> On 12 Aug 2016, at 18:32, Jun Rao wrote:
>
> Hi, Andrey,
>
> Why shouldn't the client library do reordering? It seems that if
> ReplicaFetcher thread does round-robin, the consumer client should do that
> too?
>
IMHO the client library is not a good place to implement such logic.
For ex
[
https://issues.apache.org/jira/browse/KAFKA-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419116#comment-15419116
]
Dru P commented on KAFKA-3545:
--
[~gfodor] and [~guozhang] - How can I contribute to this proj
[
https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419108#comment-15419108
]
Ismael Juma commented on KAFKA-3959:
[~onurkaraman], I would agree. [~guozhang] propos
[
https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419124#comment-15419124
]
Onur Karaman commented on KAFKA-3959:
-
Another options is to offload the responsibilit
I think one of the hard parts is that while we agree that a call to
ApiVersions is required, I don't think there is agreement on how to
use the response.
In kafka-python, for example, to support backwards compatibility we
set a single "api" configuration value during the client constructor.
This v
[
https://issues.apache.org/jira/browse/KAFKA-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419134#comment-15419134
]
Sriharsha Chintalapani commented on KAFKA-2629:
---
[~singhashish] happy to rev
[
https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419140#comment-15419140
]
Manikumar Reddy commented on KAFKA-3959:
Yes, min.insync.replicas applicable to
Hi, Andrey,
Yes, I agree that it's more work for the client to do the round-robin logic
since it has to be stateful. However, that applies to both the consumer
client and the replica fetch thread. I just feel that it's weird to use one
strategy in the replica fetch thread and another in the consum
[
https://issues.apache.org/jira/browse/KAFKA-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419157#comment-15419157
]
Dru P commented on KAFKA-3408:
--
[~sdhzlzhk] The information you've provided is insufficient t
How would time releases relate to versions? (Major, minor, API
compatibility, etc).
On Thu, Aug 11, 2016 at 9:37 AM, Guozhang Wang wrote:
> I think we do not need to make the same guarantee as for "how old of your
> Kafka version that you can upgrade to the latest in one shot" (just call it
>
GitHub user tcrayford opened a pull request:
https://github.com/apache/kafka/pull/1725
WIP KAFKA-3894: split log segment to avoid crashing cleaner thread
https://issues.apache.org/jira/browse/KAFKA-3894
This is a temporary PR, to see what Jenkins has to say about this work i
[
https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419166#comment-15419166
]
ASF GitHub Bot commented on KAFKA-3894:
---
GitHub user tcrayford opened a pull request
Hi!
> On 12 Aug 2016, at 20:22, Jun Rao wrote:
>
> Hi, Andrey,
>
> Yes, I agree that it's more work for the client to do the round-robin logic
> since it has to be stateful. However, that applies to both the consumer
> client and the replica fetch thread. I just feel that it's weird to use one
>
GitHub user vahidhashemian opened a pull request:
https://github.com/apache/kafka/pull/1726
WIP: KAFKA-4033: KIP-70: Revise Partition Assignment Semantics on New
Consumer's Subscription Change
You can merge this pull request into a Git repository by running:
$ git pull https:
[
https://issues.apache.org/jira/browse/KAFKA-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419250#comment-15419250
]
ASF GitHub Bot commented on KAFKA-4033:
---
GitHub user vahidhashemian opened a pull re
GitHub user ewencp opened a pull request:
https://github.com/apache/kafka/pull/1727
KAFKA-3847: Use a separate producer per source task
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ewencp/kafka kafka-3847-per-task-producers
A
[
https://issues.apache.org/jira/browse/KAFKA-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-3847:
-
Status: Patch Available (was: Open)
> Connect tasks should not share a producer
>
[
https://issues.apache.org/jira/browse/KAFKA-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419261#comment-15419261
]
ASF GitHub Bot commented on KAFKA-3847:
---
GitHub user ewencp opened a pull request:
Hey Damian,
That's true, but it would avoid the need to write tombstones for the
expired offsets I guess. I'm actually not sure it's a great idea anyway.
One thing we've talked about is not expiring any offsets as long as a group
is alive, which would require some custom expiration logic. There's
[
https://issues.apache.org/jira/browse/KAFKA-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419348#comment-15419348
]
Ismael Juma commented on KAFKA-4032:
cc [~granthenke]
> Uncaught exceptions when auto
[
https://issues.apache.org/jira/browse/KAFKA-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke reassigned KAFKA-4032:
--
Assignee: Grant Henke
> Uncaught exceptions when autocreating topics
>
[
https://issues.apache.org/jira/browse/KAFKA-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419350#comment-15419350
]
Grant Henke commented on KAFKA-4032:
I will make a patch for this shortly
> Uncaught
Hi all,
I've added KIP-75 - Add per-connector Converters
https://cwiki.apache.org/confluence/display/KAFKA/KIP-75+-+Add+per-connector+Converters
This is a very small completely backwards compatible change, a patch is
already available https://github.com/apache/kafka/pull/1721, and I think
probab
[
https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419365#comment-15419365
]
Todd Palino commented on KAFKA-3959:
Agree with Onur 100% here. We've been running int
Sounds sensible to me.
Ismael
On Fri, Aug 12, 2016 at 8:56 PM, Ewen Cheslack-Postava
wrote:
> Hi all,
>
> I've added KIP-75 - Add per-connector Converters
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-
> 75+-+Add+per-connector+Converters
>
> This is a very small completely backwards
Good question!
My thoughts are... bugfix releases will be done "as needed" based on
community feedback
Feature releases will be a minor release by default 0.11, 0.12 - unless:
1. We manage to break compatibility completely (we shouldn't) in which
case we need to bump to 1.X
2. We do something tot
[
https://issues.apache.org/jira/browse/KAFKA-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419424#comment-15419424
]
kambiz shahri commented on KAFKA-3408:
--
Yes sure.
> consumer rebalance fail
> --
Hi everyone,
We would like to invite you to a Stream Processing Meetup at
LinkedIn’s *Mountain
View campus on Tuesday, August 23 at 6pm*. Please RSVP here (only if you
intend to attend in person):
https://www.meetup.com/Stream-Processing-Meetup-LinkedIn/events/232864129
We have three great talks
[
https://issues.apache.org/jira/browse/KAFKA-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419429#comment-15419429
]
Amey commented on KAFKA-3408:
-
I also tried but can't reproduce this. Surely we can collaborat
[
https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419441#comment-15419441
]
Onur Karaman commented on KAFKA-3959:
-
btw I can pick this one up once we agree on the
Jason Gustafson created KAFKA-4036:
--
Summary: Unsafe dictionary access in VerifiableConsumer service
Key: KAFKA-4036
URL: https://issues.apache.org/jira/browse/KAFKA-4036
Project: Kafka
Issu
[
https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419471#comment-15419471
]
Grant Henke commented on KAFKA-3959:
I would like to present an alternative option. Th
Hi there,
I created a broker as stand by using Kafka Mirror maker but same messages gets
consumed by both Source broker and mirror broker.
Ex:
I send 1000 messages let's say offset value 1 to 1000 and consumed 500
messages from the source broker. Now my broker goes down and want to read rest
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/1727
---
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 enab
[
https://issues.apache.org/jira/browse/KAFKA-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-3847:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 17
[
https://issues.apache.org/jira/browse/KAFKA-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419482#comment-15419482
]
ASF GitHub Bot commented on KAFKA-3847:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/KAFKA-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419489#comment-15419489
]
Ewen Cheslack-Postava commented on KAFKA-3408:
--
[~dpnchl] I've added you as a
Right now, our major releases are really indicated in the second digit, not
in the leading 0. So 0.10 is a major, 0.10.1 is a minor and 0.10.0.1 is a
bug fix.
Thanks,
Jun
On Fri, Aug 12, 2016 at 1:17 PM, Gwen Shapira wrote:
> Good question!
>
> My thoughts are... bugfix releases will be done "
[
https://issues.apache.org/jira/browse/KAFKA-2946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-2946:
---
Resolution: Fixed
Fix Version/s: 0.10.1.0
Status: Resolved (was: Patch Available)
Issue res
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/1616
---
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 enab
[
https://issues.apache.org/jira/browse/KAFKA-2946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419508#comment-15419508
]
ASF GitHub Bot commented on KAFKA-2946:
---
Github user asfgit closed the pull request
Interesting, so you are suggesting that we drop Kafka's current versioning
scheme (0.major.minor.patch)? I can see the reasoning for doing so now.
However, I think I'd prefer to do that when we do the 1.x bump, which I
think we should do once exactly-once lands. That way people only have to
re-lea
I'm not convinced that time-based releases for this type of development are
the right thing.
Something like Ubuntu, where all components are moving targets needs to
decide to freeze and release without having full coordination from the
participants. There is no guarantee from Canonical that the i
GitHub user norwood opened a pull request:
https://github.com/apache/kafka/pull/1728
MINOR: add describe to valid group acl operations
@junrao
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/norwood/kafka
add-describe-to-valid-g
1 - 100 of 131 matches
Mail list logo
