etrics+for+in-sync+and+assigned+replica+count
>
> Xavier
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
[
https://issues.apache.org/jira/browse/KAFKA-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-4451:
Labels: reliability (was: )
> Recovering empty replica yields negative offsets in index of comp
1
> branch with a few internal hotfix patches and a few cherry picked fixes...
> Including the final keyword removal patch.
>
> Nacho
>
>
> On Tue, Nov 29, 2016, 5:15 PM Gwen Shapira <g...@confluent.io> wrote:
>>
>> btw. is LinkedIn no longer running from trun
; > > method. Someone overrides the `topic` method and it all works as
>> >> > > > expected.
>> >> > > > > In a subsequent release, we change `toString` to use the field
>> >> > directly
>> >> > > > > (like it's done for other fields like `key` and `value`) and it
>> >> will
>> >> > > > break
>> >> > > > > `toString` for this user. One may wonder: why would one
>> override a
>> >> > > method
>> >> > > > > like `topic`? That is a good question, but part of the exercise
>> is
>> >> > > > deciding
>> >> > > > > how we approach these issues. We could make the methods final
>> and
>> >> > > > eliminate
>> >> > > > > the possibility, we could document it so that users can choose
>> to
>> >> do
>> >> > > > weird
>> >> > > > > things if they want, etc.
>> >> > > > >
>> >> > > > > Another thing that is usually good to think about is the
>> >> expectation
>> >> > > for
>> >> > > > > `equals` and `hashCode`. What if subclasses implement them to
>> have
>> >> > > value
>> >> > > > > semantics instead of identity semantics. Is that OK or would it
>> >> break
>> >> > > > > things?
>> >> > > > >
>> >> > > > > Designing for implementation inheritance is generally complex
>> >> > although
>> >> > > > for
>> >> > > > > simple "record" like classes, it can be easier by following a
>> few
>> >> > > > > guidelines.
>> >> > > > >
>> >> > > > > Ismael
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Nacho - Ignacio Solis - iso...@igso.net
>> >> >
>> >>
>> >
>> >
>> >
>> > --
>> > Nacho - Ignacio Solis - iso...@igso.net
>> >
>>
>>
>>
>> --
>> Nacho - Ignacio Solis - iso...@igso.net
>>
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
Hey Kafka Community,
I'm trying to take a pulse on the current state of the Kafka clients ecosystem.
Which languages are most popular in our community? What does the
community value in clients?
You can help me out by filling in the survey:
https://goo.gl/forms/cZg1CJyf1PuqivTg2
I will lock the
[
https://issues.apache.org/jira/browse/KAFKA-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703313#comment-15703313
]
Gwen Shapira commented on KAFKA-4436:
-
One of the goals in making KafkaStreams part of Apache Kafka
or if this is available somwhere on your
> website.
>
> Greatly appreciated!
>
> Costa Tsirbas
> 514.443.1439
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
aken precautions to minimise the risk of transmitting software
> viruses, but we advise you to carry out your own virus checks on any
> attachment to this message.
> We cannot accept liability for any loss or damage caused by software viruses.
>
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
using delegation tokens.
>
> Thank you...
>
> Regards,
>
> Rajini
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
+1 (binding)
On Nov 9, 2016 2:17 PM, "Shikhar Bhushan" wrote:
> Hi,
>
> I would like to initiate a vote on KIP-89
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-
> 89%3A+Allow+sink+connectors+to+decouple+flush+and+offset+commit
>
> Best,
>
> Shikhar
>
v 8, 2016 at 9:03 PM, James Cheng <wushuja...@gmail.com> wrote:
>
>>
>>
>>
>> > On Nov 8, 2016, at 5:54 PM, Gwen Shapira <g...@confluent.io> wrote:
>> >
>> > Thank you so much for this clear and fair summary of the arguments.
>>
uja...@gmail.com> wrote:
>
>
>
>> On Nov 8, 2016, at 5:54 PM, Gwen Shapira <g...@confluent.io> wrote:
>>
>> Thank you so much for this clear and fair summary of the arguments.
>>
>> I'm in favor of ints. Not a deal-breaker, but in favor.
>>
&
the
>> use of strings vs ints as keys, then I would cave in and accept strings. If
>> we do so, I would like to limit string keys to 128 bytes in length. This
>> way 1) I could use a 3 letter string if I wanted (effectively using 4 total
>> bytes), 2) limit overall impact o
t;> "opt-in") and revisit this at a later date
>>
>> On Mon, Nov 7, 2016 at 2:32 PM, Gwen Shapira <g...@confluent.io> wrote:
>>
>>> Hey Radai,
>>>
>>> Looking at the proposal, it looks like a major question is still
>>> u
Forgot to mention: Thank you for quantifying the trade-off - it is
helpful and important regardless of what we end up deciding.
On Tue, Nov 8, 2016 at 3:12 PM, Sean McCauliff
<smccaul...@linkedin.com.invalid> wrote:
> On Tue, Nov 8, 2016 at 2:15 PM, Gwen Shapira <g...@conflue
nk it what you meant by
"confluent.profile_id"), but this can still be done with just ints.
On Tue, Nov 8, 2016 at 3:12 PM, Sean McCauliff
<smccaul...@linkedin.com.invalid> wrote:
> On Tue, Nov 8, 2016 at 2:15 PM, Gwen Shapira <g...@confluent.io> wrote:
>
>> Since Kafka specific
> 3. if you were going to go with a wrapper format you really dont
>> > need to
>> > > > bother with a kip (just open source your own client stack from #2
>> > above
>> > > so
>> > > > others could stop re-inventing it)
>
retrieving from / releasing to said
> pool instead of allocating memory) are generally useful beyond the scope of
> this KIP for both performance issues (allocating lots of short-lived large
> buffers is a performance bottleneck) and other areas where memory limits
> are a problem (KIP-81)
>
> Thank you,
>
> Radai.
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
for any pointers on the simplest way of getting Avro
> encoded events written to Kafka from a Kafka Connect source connector/task.
>
> Also in the task which creates SourceRecords, I'm choosing
> Schema.BYTES_SCHEMA for the 4th arg in the constructor. But I'm not clear
> what this
> > > every
> > > > single socket it should just read until it has a given amount of
> memory
> > > > used then bail out early. It can come back and read more from the
> other
> > > > sockets after those messages are processed.
> > > >
> &
M, Jun Rao <j...@confluent.io>
> wrote:
> > > >> >
> > > >> > > Hi, Rajini,
> > > >> > >
> > > >> > > Thanks for the proposal. Looks good overall and seems quite
> useful
> > > >> (e.g.
> > > >> > > for supporting delegation
to have you on board as a committer and look forward to your
> continued participation!
>
> Joel
>
--
*Gwen Shapira*
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter <https://twitter.com/ConfluentInc> | blog
<http://www.confluent.io/blog>
Oops. Sorry, didn't notice the 72h voting period has passed. You can
disregard.
Gwen
On Sat, Oct 29, 2016 at 4:29 PM, Gwen Shapira <g...@confluent.io> wrote:
> -1
>
> Kafka's development model is a good fit for critical path and
> well-established APIs. It doesn't work a
T Server implementation in Apache Kafka.
>
> Thanks,
> Harsha
>
--
*Gwen Shapira*
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter <https://twitter.com/ConfluentInc> | blog
<http://www.confluent.io/blog>
t; Thank you...
>
> Regards,
>
> Rajini
>
--
*Gwen Shapira*
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter <https://twitter.com/ConfluentInc> | blog
<http://www.confluent.io/blog>
name of IG Markets Limited (a company
> registered in England and Wales, company number 04008957) and IG Index
> Limited (a company registered in England and Wales, company number
> 01190902). Registered address at Cannon Bridge House, 25 Dowgate Hill,
> London EC4R 2YA. Both IG Ma
Gwen Shapira created KAFKA-4308:
---
Summary: Inconsistent parameters between console producer and
consumer
Key: KAFKA-4308
URL: https://issues.apache.org/jira/browse/KAFKA-4308
Project: Kafka
Gwen Shapira created KAFKA-4307:
---
Summary: Inconsistent parameters between console producer and
consumer
Key: KAFKA-4307
URL: https://issues.apache.org/jira/browse/KAFKA-4307
Project: Kafka
ag;h=
>>> 50f30a44f31fca1bd9189d2814388d51bd56b06b
>>>
>>> * Documentation:
>>> http://kafka.apache.org/0101/documentation.html
>>>
>>> * Protocol:
>>> http://kafka.apache.org/0101/protocol.html
>>>
>>> * Tests:
>>
Gwen Shapira created KAFKA-4306:
---
Summary: Connect workers won't shut down if brokers are not
available
Key: KAFKA-4306
URL: https://issues.apache.org/jira/browse/KAFKA-4306
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15573476#comment-15573476
]
Gwen Shapira commented on KAFKA-4280:
-
Looking forward to the documentation PR :)
> Add REST resou
tores more pluggable rather
> than require users to override the whole SaslServer. I was going to look
> into this later, but I can do it as part of this KIP. Will update the KIP
> with a pluggable interface.
>
> Thank you,
>
> Rajini
>
>
> On Fri, Oct 7, 2016 at 11:37
Gwen Shapira created KAFKA-4280:
---
Summary: Add REST resource for showing available connector plugin
configs
Key: KAFKA-4280
URL: https://issues.apache.org/jira/browse/KAFKA-4280
Project: Kafka
Gwen Shapira created KAFKA-4279:
---
Summary: REST endpoint to list converter plugins
Key: KAFKA-4279
URL: https://issues.apache.org/jira/browse/KAFKA-4279
Project: Kafka
Issue Type: Bug
Gwen Shapira created KAFKA-4278:
---
Summary: Undocumented REST resources
Key: KAFKA-4278
URL: https://issues.apache.org/jira/browse/KAFKA-4278
Project: Kafka
Issue Type: Bug
Components
Gwen Shapira created KAFKA-4276:
---
Summary: REST configuration not visible in connector properties
config files
Key: KAFKA-4276
URL: https://issues.apache.org/jira/browse/KAFKA-4276
Project: Kafka
d KIP-84 to add SCRAM-SHA-1 and SCRAM-SHA-256 SASL
> mechanisms to Kafka:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-84%3A+Support+SASL+SCRAM+mechanisms
>
>
> Comments and suggestions are welcome.
>
> Thank you...
>
> Regards,
>
> Rajini
--
Gw
any
>> > > > > > use
>> > > > > > > > cases where that would occur. I imagine most use cases would
>> > > > involve
>> > > > > > > > truncating the log after taking
apache.org/confluence/display/KAFKA/KIP-85%3A+Dynamic+JAAS+configuration+for+Kafka+clients
>
>
>
> Comments and suggestions are welcome.
>
> Thank you...
>
> Regards,
>
> Rajini
>
>
>
> Unless stated otherwise above:
> IBM United Kingdom Limited
[
https://issues.apache.org/jira/browse/KAFKA-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira resolved KAFKA-3302.
-
Resolution: Duplicate
Closing as duplicate since Rajini already has a PR out.
> Pass kerbe
mail is strictly confidential and
>>>
>>> for
>>>>>>
>>>>>> the use of the addressee only, unless otherwise indicated. If you are
>>>>
>>>> not
>>>>>>
>>>>>> the intended recipient, please do not read, copy, use or disclose to
>>>>
>>>> others
>>>>>>
>>>>>> this message or any attachment. Please also notify the sender by
>>>>
>>>> replying
>>>>>>
>>>>>> to this email or by telephone (+44(020 7896 0011) and then delete the
>>>>
>>>> email
>>>>>>
>>>>>> and any copies of it. Opinions, conclusion (etc) that do not relate to
>>>>
>>>> the
>>>>>>
>>>>>> official business of this company shall be understood as neither given
>>>>
>>>> nor
>>>>>>
>>>>>> endorsed by it. IG is a trading name of IG Markets Limited (a company
>>>>>> registered in England and Wales, company number 04008957) and IG Index
>>>>>> Limited (a company registered in England and Wales, company number
>>>>>> 01190902). Registered address at Cannon Bridge House, 25 Dowgate Hill,
>>>>>> London EC4R 2YA. Both IG Markets Limited (register number 195355) and
>>>
>>> IG
>>>>>>
>>>>>> Index Limited (register number 114059) are authorised and regulated by
>>>>
>>>> the
>>>>>>
>>>>>> Financial Conduct Authority.
>>>>>>
>>> The information contained in this email is strictly confidential and for
>>> the use of the addressee only, unless otherwise indicated. If you are not
>>> the intended recipient, please do not read, copy, use or disclose to
>>> others
>>> this message or any attachment. Please also notify the sender by replying
>>> to this email or by telephone (+44(020 7896 0011) and then delete the
>>> email
>>> and any copies of it. Opinions, conclusion (etc) that do not relate to
>>> the
>>> official business of this company shall be understood as neither given
>>> nor
>>> endorsed by it. IG is a trading name of IG Markets Limited (a company
>>> registered in England and Wales, company number 04008957) and IG Index
>>> Limited (a company registered in England and Wales, company number
>>> 01190902). Registered address at Cannon Bridge House, 25 Dowgate Hill,
>>> London EC4R 2YA. Both IG Markets Limited (register number 195355) and IG
>>> Index Limited (register number 114059) are authorised and regulated by
>>> the
>>> Financial Conduct Authority.
>>>
>
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
t; > perhaps be easier to use for system test writers than Clojure (under
>> > Jepsen). The Ambry <https://github.com/linkedin/ambry> project at
>> LinkedIn
>> > uses it extensively (and I think has added several more failure scenarios
>> > which don't se
ted in the github repo). Anyway, I think we
> should at least enumerate what we want to test and evaluate the
> alternatives before reinventing.
>
> Thanks,
>
> Joel
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
Hi Team Kafka,
I just merged PR 20 to our website - which gives it a new (and IMO
pretty snazzy) look and feel. Thanks to Derrick Or for contributing
the update.
I had to do a hard-refresh (shift-f5 on my mac) to get the new look to
load properly - so if stuff looks off, try it.
Comments and
[
https://issues.apache.org/jira/browse/KAFKA-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15546983#comment-15546983
]
Gwen Shapira commented on KAFKA-4244:
-
#3 is done - merged PR 20 to the site with the snazzy new look
[
https://issues.apache.org/jira/browse/KAFKA-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15546873#comment-15546873
]
Gwen Shapira commented on KAFKA-4244:
-
Update:
Change #1 is pending review and change #2 proved
Gwen Shapira created KAFKA-4244:
---
Summary: Update our website look & feel
Key: KAFKA-4244
URL: https://issues.apache.org/jira/browse/KAFKA-4244
Project: Kafka
Issue Type: Improve
there.
Comments, improvements, and contributions are welcome and encouraged.
--
Gwen Shapira
ke will be helpful.
>>
>> On Thu, Sep 15, 2016 at 3:20 PM, Gwen Shapira <g...@confluent.io> wrote:
>>
>> > Hi Guys,
>> >
>> > This discussion was dead for a while. Are there still contentious
>> > points? If not, why are there no votes?
&g
ffort to prune the list early next
>> week, so if there are any critical issues you know about, make sure they
>> are marked as such.
>>
>> Thanks,
>> Jason
>>
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
> > > > > > > >
>>> > > > > > > > 5. What is the impersonation proposal (it wasn't in the KIP
>>> but
>>> > > was
>>> > > > > > > > discussed
>>> > > > > > > > in this thread)?
>>> > > >
head and included KIP-55 since Jun said it may have a chance, but
> note that in-progress KIPs will only be included if they are ready by the
> feature freeze date (Sep. 17). We'll evaluate KIP-79 once we see Becket's
> patch.
>
> Thanks,
> Jason
>
--
*Gwen Shapira
s feature-complete.
>
> Thanks
> Eno
>
--
*Gwen Shapira*
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter <https://twitter.com/ConfluentInc> | blog
<http://www.confluent.io/blog>
d. It's important to
> mention that two +1s were cast by Gwen and Sriram:
>
> http://mail-archives.apache.org/mod_mbox/kafka-dev/201609.
> mbox/%3CCAD5tkZbLv7fvH4q%2BKe%2B%3DJMgGq%2BZT2t34e0WRUsCT1ErhtKOg1w%
> 40mail.gmail.com%3E
>
--
*Gwen Shapira*
Product Manager | Confluen
apache.org/confluence/display/KAFKA/KIP-78%3A+Cluster+Id
>
> As explained in the KIP and discussion thread, we see this as a good first
> step that can serve as a foundation for future improvements.
>
> Thanks,
> Ismael
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
[
https://issues.apache.org/jira/browse/KAFKA-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468842#comment-15468842
]
Gwen Shapira commented on KAFKA-4132:
-
Assigning to [~iwrigley], as he volunteered off-list. I hope
[
https://issues.apache.org/jira/browse/KAFKA-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-4132:
Assignee: Ian Wrigley
> Make our upgrade docs more factual and less sc
Well deserved, Jason. Looking forward to your future contributions :)
On Tue, Sep 6, 2016 at 3:29 PM, Guozhang Wang wrote:
> Welcome, and really happy to have you onboard Jason!
>
>
> Guozhang
>
> On Tue, Sep 6, 2016 at 3:25 PM, Neha Narkhede wrote:
>
>>
Gwen Shapira created KAFKA-4132:
---
Summary: Make our upgrade docs more factual and less scary
Key: KAFKA-4132
URL: https://issues.apache.org/jira/browse/KAFKA-4132
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-3538:
Affects Version/s: (was: 0.10.1.0)
0.10.0.0
Issue Type
ms.
>> > > However, this has sufficed for our needs so far and others have
>> expressed
>> > > their satisfaction on the JIRA.
>> > >
>> > >- Executable decrypts a file that stores encrypted passwords.
>> > >- The secret to decrypt
gt; Please take a look. Your feedback is appreciated.
>
> Thanks,
> Ismael
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
[
https://issues.apache.org/jira/browse/KAFKA-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira resolved KAFKA-3742.
-
Resolution: Fixed
Fix Version/s: 0.10.1.0
Issue resolved by pull request 1717
[https
[
https://issues.apache.org/jira/browse/KAFKA-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-4070:
Assignee: Shikhar Bhushan
> Implement a useful Struct.toStr
[
https://issues.apache.org/jira/browse/KAFKA-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira resolved KAFKA-4070.
-
Resolution: Fixed
Fix Version/s: 0.10.1.0
Issue resolved by pull request 1790
[https
[
https://issues.apache.org/jira/browse/KAFKA-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-4052:
Resolution: Fixed
Fix Version/s: 0.10.1.0
Status: Resolved (was: Patch Available
using Connect and Streams in
>> production. That means the new Java Consumer too. :)
>>
>> Ismael
>>
>> On Thu, Aug 25, 2016 at 5:09 PM, Gwen Shapira <g...@confluent.io> wrote:
>>
>> > Originally, we suggested keeping the beta label until we
>>
>>> Because the cost of doing this for a larger number of releases is
>>> relatively low, I still think we should go for 6 here (our code currently
>>> supports 5 versions as I said in a previous message, so we're close to that
>>> target already). I'm gener
he zookeeper
> command-line option is present (for compatibility). This is similar to what
> we did it for the new producer in 0.9.0.0, but backwards compatible.
>
> Thoughts?
>
> Ismael
>
> [1] http://kafka.apache.org/documentation.html#consumerapi
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
.org/jira/browse/KAFKA-2629
> POC: https://github.com/apache/kafka/pull/1770
>
> Thanks
>
> --
>
> Regards,
> Ashish
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
t major release, and removed in the major release
> after that.
>
> Because of the success of LTS models in this and other open source
> projects, I would suggest implementing a formal LTS plan for Kafka too.
>
> Regards,
> --Vahid
>
>
>
> From: Gwen Shapira
[
https://issues.apache.org/jira/browse/KAFKA-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-4051:
Resolution: Fixed
Fix Version/s: 0.10.1.0
Status: Resolved (was: Patch Available
Replication+Quotas>
>
> Ben
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
[
https://issues.apache.org/jira/browse/KAFKA-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira resolved KAFKA-4053.
-
Resolution: Fixed
Fix Version/s: (was: 0.10.0.2)
0.10.1.0
Issue
[
https://issues.apache.org/jira/browse/KAFKA-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira resolved KAFKA-4056.
-
Resolution: Fixed
Fix Version/s: 0.10.1.0
Issue resolved by pull request 1759
[https
gt;> Jun
>>
>> On Tue, Aug 16, 2016 at 1:32 PM, Andrey L. Neporada <
>> anepor...@yandex-team.ru> wrote:
>>
>>> Hi!
>>>
>>> I would like to initiate the voting process for KIP-74:
>>> https://cwiki.apache.org/confluence/displ
[
https://issues.apache.org/jira/browse/KAFKA-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-3845:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request
[
https://issues.apache.org/jira/browse/KAFKA-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427554#comment-15427554
]
Gwen Shapira commented on KAFKA-4051:
-
I was definitely concerned about complete replacement
ce into that. I don’t think anyone will disagree that
> the controller needs a sizable amount of work. This definitely wouldn’t be
> the first project to separate out the brains from the dumb worker processes.
>
> -Todd
>
>
> On Thu, Aug 18, 2016 at 10:53 AM, Gwen Shapira <g..
;>>>> thanks
>> > > >>>>>>>>>>>>>> for clarifying. For completeness, can we add this
>> > > >> detail
>> > > >>> to
>> > > >>>>> the
>> > > >>>>>>>> doc -
>> > > >>>>>>>>
; <javascript:;>> wrote:
>> >
>> > > Congratulations Gwen! Great news.
>> > >
>> > > Ismael
>> > >
>> > > On 18 Aug 2016 2:44 am, "Jun Rao" <j...@confluent.io <javascript:;>>
>> > wrote:
&
sort of a
> catch-22 because the bootstrap is required to connect to a Kafka cluster
> (as opposed to zookeeper) and at that point the Metadata returned assumes
> an endpoint of the connecting security protocol. Is that an acceptable
> limitation?
> Thanks,Grant
> On Wed, Aug 1
the output from the command with
> various options.Thank you,Jayesh Thakrar
>
>
>
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
finally,
>>> there is the fact that working on Apache projects should be
>>> FUN. It should be someplace where you aren't beholden to,
>>> or under, some artificial schedule.
>>>
>>> If time-based releases are put in place, and held to under
>>> un
with a +1 (binding).
>
> --
> Thanks,
> Ewen
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
the clients,
>> > the
>> > > server, streams, connect, etc there is enough parallelism that this
>> will
>> > be
>> > > important.
>> > >
>> > > I think this also gives a lot more predictability to people who
>> > cont
>- Use the api versions info from NetworkClient to enable/ disable
>> >feature sets, something similar to what librdkafka already has. This
>> will
>> >need much broader testing.
>> >
>> > Note that both of the aforementioned steps have be
5+-+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
> probably not very controversial. Any feedback would be appreciated.
>
> --
> Thanks,
iewed/processed?
> https://github.com/apache/kafka/pull/1539
>
> Am I missing any steps or is it just the backlog?
> Thanks,Jayesh
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
o need to fix how often (and when)
> this process happens. We just know that for a release to happen we'll have
> 4 weeks advance notice.
>
> Nacho
>
>
>
> On Fri, Aug 12, 2016 at 1:17 PM, Gwen Shapira <g...@confluent.io> wrote:
>
>> Good question!
>>
>
[
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
ms that each
>> > branch should really only need one or or a maximum of two bug fix
>> releases.
>> > After that, users are welcome to upgrade to a new feature release (and
>> > hopefully to the most current) to get non-critical fixes and features. An
>>
nk that is some value
> add. In future, the api versions info can be used to take smarter decisions.
>
> On Wed, Aug 10, 2016 at 11:04 PM, Gwen Shapira <g...@confluent.io> wrote:
>
>> I hate doing this, because Ashish has really been good about following
>> up on the PR, but I'
be this behavior has fundamentals that I don't know.
>
> I'm sorry if it was discussed previously, I was researching but I didn't
> found a similar issue.
>
> Thanks,
>
> --
>
>
>
> Gabriel Alejandro Ibarra
>
> Software Engineer
>
> San Lorenzo 47, 3rd Floor, Office 5
>
> Córdoba, Argentina
>
> Phone: +54 351 4217888
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
under review. Here is the PR
>> <https://github.com/apache/kafka/pull/986>
>>
>> I have addressed all review comments and have been waiting for further
>> reviews/ this to go in for quite some time. I will really appreciate if a
>> committer can help with making
, Ashish Singh, Avi Flax,
> Damian Guy, Dustin Cote, Edoardo Comar, Eno Thereska, Ewen
> Cheslack-Postava, Flavio Junqueira, Florian Hussonnois, Geoff Anderson,
> Grant Henke, Greg Fodor, Guozhang Wang, Gwen Shapira, Henry Cai, Ismael
> Juma, Jason Gustafson, Jeff Klukas, Jendrik Poloczek,
>
>>
>> On Tue, Aug 9, 2016 at 4:49 PM, Gwen Shapira <g...@confluent.io> wrote:
>>
>>>
>>> 4. Frequent releases mean we need to do bugfix releases for older
>>> branches. Right now we only do bugfix releases to latest release.
>>>
>&
, Aug 10, 2016 at 5:44 PM, Joel Koshy <jjkosh...@gmail.com> wrote:
> On Tue, Aug 9, 2016 at 4:49 PM, Gwen Shapira <g...@confluent.io> wrote:
>
>>
>> 4. Frequent releases mean we need to do bugfix releases for older
>> branches. Right now we only do bugfix releases
e could say that we support direct upgrades for 2 years (6
> releases).
>
> Ismael
>
> On Wed, Aug 10, 2016 at 12:49 AM, Gwen Shapira <g...@confluent.io> wrote:
>
>> Dear Kafka Developers and Users,
>>
>> In the past, our releases have been quite unp
artifact.
>>
>> Do you think this is useful in Apache Kafka? Any thoughts on the approach?
>>
>> Thanks,
>> Grant
>> --
>> Grant Henke
>> Software Engineer | Cloudera
>> gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
>>
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
501 - 600 of 2807 matches
Mail list logo