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 pas
[
https://issues.apache.org/jira/browse/KAFKA-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Balint Molnar reassigned KAFKA-4814:
Assignee: Balint Molnar
> ZookeeperLeaderElector not respecting zookeeper.set.acl
> ---
[
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
> produce
[
https://issues.apache.org/jira/browse/KAFKA-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889871#comment-15889871
]
huxi commented on KAFKA-4822:
-
For KafkaProducer, all writes are asynchronous by default. Snip
Aneesh created KAFKA-4823:
-
Summary: Creating Kafka Producer on application running on Java 1.6
Key: KAFKA-4823
URL: https://issues.apache.org/jira/browse/KAFKA-4823
Project: Kafka
Issue Type: Bug
+1 (non binding).
Thanks
Eno
> On 28 Feb 2017, at 17:22, Matthias J. Sax wrote:
>
> +1
>
> Thanks a lot for the KIP!
>
> -Matthias
>
>
> On 2/28/17 1:35 AM, Damian Guy wrote:
>> Thanks for the KIP Jeyhun!
>>
>> +1
>>
>> On Tue, 28 Feb 2017 at 08:59 Jeyhun Karimov wrote:
>>
>>> Dear commu
+1, thanks.
Eno
> On 28 Feb 2017, at 17:17, Guozhang Wang wrote:
>
> ＋1
>
> On Tue, Feb 28, 2017 at 4:28 AM, Tom Crayford wrote:
>
>> +1 (non-binding)
>>
>> On Tue, 28 Feb 2017 at 11:42, Molnár Bálint
>> wrote:
>>
>>> +1
>>>
>>> 2017-02-28 12:17 GMT+01:00 Dongjin Lee :
>>>
>>
[
https://issues.apache.org/jira/browse/KAFKA-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KAFKA-1954 stopped by Balint Molnar.
> Speed Up The Unit Tests
> ---
>
> Key: KAFK
[
https://issues.apache.org/jira/browse/KAFKA-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KAFKA-1548 stopped by Balint Molnar.
> Refactor the "replica_id" in requests
> -
>
Hi Guozhang,
Thanks for the KIP! This is an important feature for Kafka Streams and will
help to unlock a bunch of use cases.
I have some concerns/questions:
1. Producer per task: I'm worried about the overhead this is going to
put on both the streams app and the Kafka Brokers. You can eas
GitHub user cvaliente opened a pull request:
https://github.com/apache/kafka/pull/2621
KAFKA-4800: Streams State transition ASCII diagrams need fixing and
polishing
added tags to not break javadoc display of the ASCII diagrams.
see broken ascii here:
https://kafka.apache.o
[
https://issues.apache.org/jira/browse/KAFKA-4800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889997#comment-15889997
]
ASF GitHub Bot commented on KAFKA-4800:
---
GitHub user cvaliente opened a pull request
Hi all,
I have just created KIP-130 to add a new method to the KafkaStreams API in
order to expose the states of threads and active tasks.
https://cwiki.apache.org/confluence/display/KAFKA/KIP+130%3A+Expose+states+of+active+tasks+to+KafkaStreams+public+API
Thanks,
--
Florian HUSSONNOIS
+1 (non-binding)
On Tue, Feb 28, 2017 at 6:56 PM, Apurva Mehta wrote:
> +1 (non-binding) for 0.11.0
>
> I do agree with Ismael's point that exactly-once should go through one
> release of stabilization before bumping the version to 1.0.
>
> Thanks,
> Apurva
>
> On Mon, Feb 27, 2017 at 7:47 PM, I
+1
Thanks,
Bill
On Wed, Mar 1, 2017 at 5:42 AM, Eno Thereska wrote:
> +1, thanks.
>
> Eno
> > On 28 Feb 2017, at 17:17, Guozhang Wang wrote:
> >
> > ＋1
> >
> > On Tue, Feb 28, 2017 at 4:28 AM, Tom Crayford
> wrote:
> >
> >> +1 (non-binding)
> >>
> >> On Tue, 28 Feb 2017 at 11:42, Molnár Bálin
Thanks Florian,
Have you had a chance to look at the new state methods in 0.10.2, e.g.,
KafkaStreams.state()?
Thanks
Eno
> On 1 Mar 2017, at 11:54, Florian Hussonnois wrote:
>
> Hi all,
>
> I have just created KIP-130 to add a new method to the KafkaStreams API in
> order to expose the state
+1
Thanks
Bill
On Wed, Mar 1, 2017 at 5:06 AM, Eno Thereska wrote:
> +1 (non binding).
>
> Thanks
> Eno
> > On 28 Feb 2017, at 17:22, Matthias J. Sax wrote:
> >
> > +1
> >
> > Thanks a lot for the KIP!
> >
> > -Matthias
> >
> >
> > On 2/28/17 1:35 AM, Damian Guy wrote:
> >> Thanks for the KIP
+1 (non-binding)
Jozef
P.S. I volunteer to help with this KIP.
Sent from [ProtonMail](https://protonmail.ch), encrypted email based in
Switzerland.
Original Message
Subject: Re: [VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11
Local Time: March 1, 2017 1:46 PM
UTC
[
https://issues.apache.org/jira/browse/KAFKA-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890130#comment-15890130
]
Giri commented on KAFKA-4822:
-
i understand that the sync can be achieved by the above workaro
[
https://issues.apache.org/jira/browse/KAFKA-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890139#comment-15890139
]
Giri commented on KAFKA-4822:
-
A producer implementation with finer control will be helpful in
Hi Eno,
Yes, but the state() method only returns the global state of the
KafkaStream application (ie: CREATED, RUNNING, REBALANCING,
PENDING_SHUTDOWN, NOT_RUNNING).
An alternative to this KIP would be to change this method to return more
information instead of adding a new method.
2017-03-01 13:
[
https://issues.apache.org/jira/browse/KAFKA-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890172#comment-15890172
]
Ismael Juma edited comment on KAFKA-4822 at 3/1/17 1:38 PM:
Th
[
https://issues.apache.org/jira/browse/KAFKA-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890172#comment-15890172
]
Ismael Juma commented on KAFKA-4822:
The data is sent as soon as possible by default (
Colin,
Thank you for the feedback. Since we are reusing the existing
throttle_time_ms field for produce/fetch responses, changing this to
microseconds would be a breaking change. Since we don't currently plan to
throttle at sub-millisecond intervals, perhaps it makes sense to keep the
value consis
Github user rajinisivaram closed the pull request at:
https://github.com/apache/kafka/pull/2608
---
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
[
https://issues.apache.org/jira/browse/KAFKA-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890202#comment-15890202
]
ASF GitHub Bot commented on KAFKA-4779:
---
Github user rajinisivaram closed the pull r
GitHub user rajinisivaram opened a pull request:
https://github.com/apache/kafka/pull/2622
KAFKA-4631: Request metadata in consumer if topic/partitions unavailable
If leader node of one more more partitions in a consumer subscription are
temporarily unavailable, request metadata ref
[
https://issues.apache.org/jira/browse/KAFKA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890223#comment-15890223
]
ASF GitHub Bot commented on KAFKA-4631:
---
GitHub user rajinisivaram opened a pull req
+1 (non-binding)
Thanks for the KIP!
On Wed, Mar 1, 2017 at 1:49 PM, Bill Bejeck wrote:
> +1
>
> Thanks
> Bill
>
> On Wed, Mar 1, 2017 at 5:06 AM, Eno Thereska
> wrote:
>
> > +1 (non binding).
> >
> > Thanks
> > Eno
> > > On 28 Feb 2017, at 17:22, Matthias J. Sax
> wrote:
> > >
> > > +1
> > >
[
https://issues.apache.org/jira/browse/KAFKA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890234#comment-15890234
]
Rajini Sivaram commented on KAFKA-4631:
---
The attached PR solves the issue in the sec
Hi Dong,
When you say "logStartOffset", do you mean "log_begin_offset "? I could
only find the latter in the KIP. If so, would log_start_offset be a better
name?
Ismael
On Tue, Feb 28, 2017 at 4:26 AM, Dong Lin wrote:
> Hi Jun and everyone,
>
> I would like to change the KIP in the following w
[
https://issues.apache.org/jira/browse/KAFKA-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890242#comment-15890242
]
bernie huang commented on KAFKA-4823:
-
Do you use jdk1.7 package your application jar
Hi Becket,
Thanks for sharing your thoughts. More inline.
On Wed, Mar 1, 2017 at 2:54 AM, Becket Qin wrote:
> As you can imagine if the ProducerRecord has a value as a List and the
> Interceptor.onSend() can actually add an element to the List. If the
> producer.send() is called on the same Pro
[
https://issues.apache.org/jira/browse/KAFKA-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890350#comment-15890350
]
Aneesh commented on KAFKA-4823:
---
[~bernie huang] if I use jdk 1.7 to package my jar file, th
Clemens Valiente created KAFKA-4824:
---
Summary: add unique identifier to clientId
Key: KAFKA-4824
URL: https://issues.apache.org/jira/browse/KAFKA-4824
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clemens Valiente reassigned KAFKA-4824:
---
Assignee: Clemens Valiente
> add unique identifier to clientId
>
[
https://issues.apache.org/jira/browse/KAFKA-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890387#comment-15890387
]
Clemens Valiente commented on KAFKA-4824:
-
duplicate of KAFKA-4117
> add unique i
[
https://issues.apache.org/jira/browse/KAFKA-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clemens Valiente resolved KAFKA-4824.
-
Resolution: Duplicate
> add unique identifier to clientId
> --
[
https://issues.apache.org/jira/browse/KAFKA-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clemens Valiente closed KAFKA-4824.
---
> add unique identifier to clientId
> -
>
> Key: K
[
https://issues.apache.org/jira/browse/KAFKA-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890422#comment-15890422
]
Aneesh commented on KAFKA-4823:
---
[~bernie huang] I use JDK1.6 to compile my app jar,still it
[
https://issues.apache.org/jira/browse/KAFKA-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890468#comment-15890468
]
Ismael Juma commented on KAFKA-4823:
If you can't upgrade the Java version in the clie
[
https://issues.apache.org/jira/browse/KAFKA-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890540#comment-15890540
]
Andrew Olson commented on KAFKA-4092:
-
Note that this Jira is being reverted in 0.10.2
Ben Stopford created KAFKA-4825:
---
Summary: Likely Data Loss in ReassignPartitionsTest System Test
Key: KAFKA-4825
URL: https://issues.apache.org/jira/browse/KAFKA-4825
Project: Kafka
Issue Type
Hi Ismael,
I actually mean log_start_offset. I realized that it is a better name after
I start implementation because "logStartOffset" is already used in
Log.scala and LogCleanerManager.scala. So I changed it from
log_begin_offset to log_start_offset in the patch. But I forgot to update
the KIP an
[
https://issues.apache.org/jira/browse/KAFKA-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-4823:
-
Component/s: (was: KafkaConnect)
> Creating Kafka Producer on application runn
[
https://issues.apache.org/jira/browse/KAFKA-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890661#comment-15890661
]
Ben Stopford commented on KAFKA-4825:
-
This could be a result of KIP-101
(https://cwi
[
https://issues.apache.org/jira/browse/KAFKA-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890699#comment-15890699
]
Aneesh commented on KAFKA-4823:
---
[~ijuma] Kafka 0.8.2.0 worked for me.I did go through REST
Colin P. McCabe created KAFKA-4826:
--
Summary: Fix some findbugs warnings in Kafka Streams
Key: KAFKA-4826
URL: https://issues.apache.org/jira/browse/KAFKA-4826
Project: Kafka
Issue Type: Bug
GitHub user cmccabe opened a pull request:
https://github.com/apache/kafka/pull/2623
KAFKA-4826. Fix some findbugs warnings in Kafka Streams
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cmccabe/kafka KAFKA-4826
Alternatively
[
https://issues.apache.org/jira/browse/KAFKA-4826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890725#comment-15890725
]
ASF GitHub Bot commented on KAFKA-4826:
---
GitHub user cmccabe opened a pull request:
[
https://issues.apache.org/jira/browse/KAFKA-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890746#comment-15890746
]
Xu Zhang commented on KAFKA-3686:
-
Any update there? I think we have the same issue.
> Ka
Aymeric Bouvet created KAFKA-4827:
-
Summary: Kafka connect: Escape special characters in connector name
Key: KAFKA-4827
URL: https://issues.apache.org/jira/browse/KAFKA-4827
Project: Kafka
Is
[
https://issues.apache.org/jira/browse/KAFKA-4826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-4826:
---
Component/s: streams
> Fix some findbugs warnings in Kafka Streams
> -
[
https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aymeric Bouvet updated KAFKA-4827:
--
Summary: Kafka connect: error with special characters in connector name
(was: Kafka connect: Es
[
https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aymeric Bouvet updated KAFKA-4827:
--
Description:
When creating a connector, if the connector name (and possibly other
properties) e
Hamidreza Afzali created KAFKA-4828:
---
Summary: ProcessorTopologyTestDriver does not work when using
.through()
Key: KAFKA-4828
URL: https://issues.apache.org/jira/browse/KAFKA-4828
Project: Kafka
@michael:
i used void because im used to java beans. thinking about it, i dont see
much use for returning false from adding a header: if the headers are in
read-only you should probably thrown an IllegalStateException because lets
face it, 99% of users dont check return values.
returning "this" is
Hi there,
I wonder if it makes sense to give the option to disable auto
repartitioning while doing groupBy.
I understand with https://issues.apache.org/jira/browse/KAFKA-3561,
an internal topic for repartition will be automatically created and synced
to brokers, which is useful when aggregation k
If you use stream.groupByKey() then there will be no repartitioning as long
as there have been no key changing operations preceding it, i.e, map,
selectKey, flatMap, transform. If you use stream.groupBy(...) then we see
it as a key changing operation, hence we need to repartition the data.
On Wed,
[
https://issues.apache.org/jira/browse/KAFKA-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Quilcate updated KAFKA-4743:
--
Description:
Add an external tool to reset Consumer Group offsets, and achieve rewind over
the
GitHub user jeqo opened a pull request:
https://github.com/apache/kafka/pull/2624
KAFKA-4743: Add Reset Consumer Group Offsets tooling [KIP-122]
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jeqo/kafka
feature/rewind-consumer-
[
https://issues.apache.org/jira/browse/KAFKA-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890839#comment-15890839
]
ASF GitHub Bot commented on KAFKA-4743:
---
GitHub user jeqo opened a pull request:
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/2609
---
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-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890856#comment-15890856
]
ASF GitHub Bot commented on KAFKA-4677:
---
Github user asfgit closed the pull request
FYI: The difference between `groupBy` (may trigger re-partitioning) vs.
`groupByKey` (does not trigger re-partitioning) also applies to:
- `map` vs. `mapValues`
- `flatMap` vs. `flatMapValues`
On Wed, Mar 1, 2017 at 8:15 PM, Damian Guy wrote:
> If you use stream.groupByKey() then there will b
Steven Schlansker created KAFKA-4829:
Summary: Improve logging of StreamTask commits
Key: KAFKA-4829
URL: https://issues.apache.org/jira/browse/KAFKA-4829
Project: Kafka
Issue Type: Impro
[
https://issues.apache.org/jira/browse/KAFKA-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Schlansker updated KAFKA-4829:
-
Description:
Currently I see this every commit interval:
{code}
2017-02-28T21:27:16.659Z
[
https://issues.apache.org/jira/browse/KAFKA-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Schlansker updated KAFKA-4829:
-
Description:
Currently I see this every commit interval:
{code}
2017-02-28T21:27:16.659Z
[
https://issues.apache.org/jira/browse/KAFKA-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-4829:
-
Labels: user-experience (was: )
> Improve logging of StreamTask commits
> ---
It should be:
groupBy -> always trigger repartitioning
groupByKey -> maybe trigger repartitioning
And there will not be two repartitioning topics. The repartitioning will
be done by the groupBy/groupByKey operation, and thus, in the
aggregation step we know that data is correctly partitioned and
[
https://issues.apache.org/jira/browse/KAFKA-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890917#comment-15890917
]
Guozhang Wang commented on KAFKA-4829:
--
I'd like to expand the scope of this JIRA a b
Guozhang Wang created KAFKA-4830:
Summary: Augment KStream.print() to allow users pass in extra
parameters in the printed string
Key: KAFKA-4830
URL: https://issues.apache.org/jira/browse/KAFKA-4830
P
GitHub user sharad-develop opened a pull request:
https://github.com/apache/kafka/pull/2625
KAFKA:4623- Change default unclean.leader.election.enabled from True to
False
KAFKA:4623- Change default unclean.leader.election.enabled from True to
False
You can merge this pull request i
Guozhang Wang created KAFKA-4831:
Summary: Extract WindowedSerde to public APIs
Key: KAFKA-4831
URL: https://issues.apache.org/jira/browse/KAFKA-4831
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890935#comment-15890935
]
Jeff Widman commented on KAFKA-4677:
Is KIP-54 related since it also implements a stic
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/2611
---
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-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890965#comment-15890965
]
Sharad commented on KAFKA-4706:
---
[~mjsax] Need a bit of review of the solution. Is it ok if
[
https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891025#comment-15891025
]
Sharad commented on KAFKA-4623:
---
Rebased.
PR submitted:
https://github.com/apache/kafka/pull
Github user sharad-develop closed the pull request at:
https://github.com/apache/kafka/pull/2625
---
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
[
https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharad updated KAFKA-4623:
--
Comment: was deleted
(was: https://github.com/apache/kafka/pull/2470)
> Change Default unclean.leader.election.
Hi Ismael,
Thanks for the reply. Please see the comments inline.
On Wed, Mar 1, 2017 at 6:47 AM, Ismael Juma wrote:
> Hi Becket,
>
> Thanks for sharing your thoughts. More inline.
>
> On Wed, Mar 1, 2017 at 2:54 AM, Becket Qin wrote:
>
> > As you can imagine if the ProducerRecord has a value a
[
https://issues.apache.org/jira/browse/KAFKA-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891031#comment-15891031
]
Matthias J. Sax commented on KAFKA-4677:
Streams used it's own partition assigner
[
https://issues.apache.org/jira/browse/KAFKA-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891048#comment-15891048
]
Matthias J. Sax commented on KAFKA-4706:
Yes.
> Unify StreamsKafkaClient instance
Thanks for the KIP.
I am wondering a little bit, why you need to expose this information.
Can you describe some use cases?
Would it be worth to unify this new API with KafkaStreams#state() to get
the overall state of an application without the need to call two
different methods? Not sure how this
Hi all,
I have updated the KIP to include a script that allows user to purge data
by providing a map from partition to offset. I think this script may be
convenience and useful, e.g., if user simply wants to purge all data of
given partitions from command line. I am wondering if anyone object this
Hi Ewen,
Thanks for the KIP, I think it will be useful :)
I'm just wondering if we can add support not just for bytes schema,
but also for a struct that contains bytes? I'm thinking of the
scenario of using a connector to grab BLOBs out of a DB - I think you
end up with this structure if you use
Hi all,
Thanks for commenting, everyone. Does anyone have more questions or
comments, or should we vote? The latest proposal is up at
https://cwiki.apache.org/confluence/display/KAFKA/KIP-117%3A+Add+a+public+AdminClient+API+for+Kafka+admin+operations
best,
Colin
On Thu, Feb 16, 2017, at 15:00
Hey Jun,
Do you think it is OK to keep the existing wire protocol in the KIP? I am
wondering if we can initiate vote for this KIP.
Thanks,
Dong
On Tue, Feb 28, 2017 at 2:41 PM, Dong Lin wrote:
> Hey Jun,
>
> I just realized that StopReplicaRequest itself doesn't specify the
> replicaId in th
[
https://issues.apache.org/jira/browse/KAFKA-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891151#comment-15891151
]
Matthias J. Sax commented on KAFKA-4828:
I am not sure if the JIRA title and error
That makes sense. I didn't see that this field already existed in some
of the replies-- good clarification.
best,
On Wed, Mar 1, 2017, at 05:41, Rajini Sivaram wrote:
> Colin,
>
> Thank you for the feedback. Since we are reusing the existing
> throttle_time_ms field for produce/fetch responses
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/2603
---
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
Hi Matthias,
First, I will answer to your last question.
The main reason to have both TaskState#assignment and
TaskState#consumedOffsetsByPartition is that tasks have no consumed offsets
until at least one message is consumed for each partition even if previous
offsets exist for the consumer grou
quick comment on the request objects:
i see "abstract class NewTopic" and "class NewTopicWithReplication" and "
NewTopicWithReplicaAssignments"
1. since the result object is called CreateTopicResults should these be
called *Request?
2. this seems like a suboptimal approach to me. imagine we add a
[
https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891355#comment-15891355
]
mjuarez commented on KAFKA-2729:
We are also running into this problem in our staging clus
+1 (binding)
-Ewen
On Wed, Mar 1, 2017 at 4:56 AM, Jozef.koval
wrote:
> +1 (non-binding)
>
> Jozef
>
> P.S. I volunteer to help with this KIP.
>
>
> Sent from [ProtonMail](https://protonmail.ch), encrypted email based in
> Switzerland.
>
>
>
> Original Message
> Subject: Re: [
+1 (non-binding)
On Wed, Mar 1, 2017 at 4:41 PM, Ewen Cheslack-Postava
wrote:
> +1 (binding)
>
> -Ewen
>
> On Wed, Mar 1, 2017 at 4:56 AM, Jozef.koval
> wrote:
>
> > +1 (non-binding)
> >
> > Jozef
> >
> > P.S. I volunteer to help with this KIP.
> >
> >
> > Sent from [ProtonMail](https://protonm
Thanks everyone for the feedback. Since everyone was in favour and we had
covered this particular case in the time-based release plan[1], I went
ahead and updated the wiki page to specify the next version as 0.11.0.0.
I'll update JIRA versions and the KIP page soon.
Ismael
[1] "We change the mess
+1
Thanks Ismael for volunteering to run the next time based release.
On Wed, Mar 1, 2017 at 4:51 PM, Ismael Juma wrote:
> Thanks everyone for the feedback. Since everyone was in favour and we had
> covered this particular case in the time-based release plan[1], I went
> ahead and updated the w
Guozhang,
I'm fine w/ adjusting if people want to, but it ends up being more code
since we also need to convert SerializationExceptions to DataExceptions and
the only thing the toConnectData method even does is specific to Connect
(adding the SchemaAndValue).
Gwen -- isn't that an SMT? ExtractFie
[
https://issues.apache.org/jira/browse/KAFKA-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891428#comment-15891428
]
Helena Edelson commented on KAFKA-4396:
---
I ran into this as well. Re-deploying with
1 - 100 of 111 matches
Mail list logo
