Gwen Shapira created KAFKA-5000:
---
Summary: Framework should log some progress information regularly
to assist in troubleshooting
Key: KAFKA-5000
URL: https://issues.apache.org/jira/browse/KAFKA-5000
the owners of the remaining issues get them resolved or move them to a
different release?
Once we get the "remaining" list to zero, I'll roll the first RC.
--
*Gwen Shapira*
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter <https://twitter.com/ConfluentInc&
[
https://issues.apache.org/jira/browse/KAFKA-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15943621#comment-15943621
]
Gwen Shapira commented on KAFKA-4930:
-
[~sliebau] I like your validName approach. Can you create a PR
[
https://issues.apache.org/jira/browse/KAFKA-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-4929:
Resolution: Fixed
Fix Version/s: 0.11.0.0
Status: Resolved (was: Patch Available
[
https://issues.apache.org/jira/browse/KAFKA-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira resolved KAFKA-4918.
-
Resolution: Not A Problem
> Continuous fetch requests for offset storage topic in kafka conn
[
https://issues.apache.org/jira/browse/KAFKA-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira reassigned KAFKA-4918:
---
Assignee: Gwen Shapira
> Continuous fetch requests for offset storage topic in kafka conn
[
https://issues.apache.org/jira/browse/KAFKA-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936374#comment-15936374
]
Gwen Shapira commented on KAFKA-4930:
-
Good catch! If you fix this, we'll gladly take the PR. Let me
[
https://issues.apache.org/jira/browse/KAFKA-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira resolved KAFKA-4917.
-
Resolution: Won't Fix
Hoist is fine :)
> Our built-in file connector can't work with our bu
[
https://issues.apache.org/jira/browse/KAFKA-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15934854#comment-15934854
]
Gwen Shapira commented on KAFKA-4878:
-
[~original-brownbear] - Thank you. Let me know if you need help
[
https://issues.apache.org/jira/browse/KAFKA-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15930957#comment-15930957
]
Gwen Shapira commented on KAFKA-4917:
-
I guess I could use HOIST transformation to create a struct
[
https://issues.apache.org/jira/browse/KAFKA-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-4917:
Labels: newbie (was: )
> Our built-in file connector can't work with our built-in
Gwen Shapira created KAFKA-4917:
---
Summary: Our built-in file connector can't work with our built-in
SMT
Key: KAFKA-4917
URL: https://issues.apache.org/jira/browse/KAFKA-4917
Project: Kafka
I'm torn between my desire to get this in already and the fact that parts
of the API feel a bit alien to Kafka.
I will resolve my difficulties by giving my feedback here and then going to
vote +1 on the vote thread.
Colin can choose whether to address my concerns now or use his "unstable"
option
[
https://issues.apache.org/jira/browse/KAFKA-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-4878:
Fix Version/s: 0.10.2.1
> Kafka Connect does not log connector configuration err
[
https://issues.apache.org/jira/browse/KAFKA-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-4878:
Priority: Blocker (was: Major)
> Kafka Connect does not log connector configuration err
[
https://issues.apache.org/jira/browse/KAFKA-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923586#comment-15923586
]
Gwen Shapira edited comment on KAFKA-4878 at 3/14/17 5:07 AM:
--
This is even
[
https://issues.apache.org/jira/browse/KAFKA-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923586#comment-15923586
]
Gwen Shapira commented on KAFKA-4878:
-
This is even worse in stand-alone mode because if you start
Gwen Shapira created KAFKA-4882:
---
Summary: Remove internal converter configuration from example
property files
Key: KAFKA-4882
URL: https://issues.apache.org/jira/browse/KAFKA-4882
Project: Kafka
Gwen Shapira created KAFKA-4878:
---
Summary: Kafka Connect does not log connector configuration errors
Key: KAFKA-4878
URL: https://issues.apache.org/jira/browse/KAFKA-4878
Project: Kafka
Issue
yteArrayConverter+for+Kafka+Connect
>
> There was a small amount of discussion, see the original thread here:
> https://lists.apache.org/thread.html/62fc2245285ac5d15ebb9b2ebed672
> b51e391c8dfe9a51be85f685f3@%3Cdev.kafka.apache.org%3E
>
> The vote will stay open for at least 72 hou
[
https://issues.apache.org/jira/browse/KAFKA-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15896561#comment-15896561
]
Gwen Shapira commented on KAFKA-3491:
-
Very late to the party, but it looks like the issue is still
[
https://issues.apache.org/jira/browse/KAFKA-4567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira resolved KAFKA-4567.
-
Resolution: Fixed
Fix Version/s: 0.11.0.0
Issue resolved by pull request 2511
[https
[
https://issues.apache.org/jira/browse/KAFKA-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira resolved KAFKA-4792.
-
Resolution: Duplicate
> Kafka Connect: Add ByteArray Conver
[
https://issues.apache.org/jira/browse/KAFKA-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-4280:
Labels: newbie (was: )
> Add REST resource for showing available connector plugin conf
[
https://issues.apache.org/jira/browse/KAFKA-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-4276:
Resolution: Fixed
Fix Version/s: 0.11.0.0
Status: Resolved (was: Patch Available
[
https://issues.apache.org/jira/browse/KAFKA-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-4115:
Labels: newbie (was: )
> Grow default heap settings for distributed Connect from 256M to
[
https://issues.apache.org/jira/browse/KAFKA-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-3832:
Labels: newbie (was: )
> Kafka Connect's JSON Converter never outputs a null va
so 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? ExtractField?
>
> -Ewen
>
> On Wed, Mar 1, 2017 at 1:58 PM, Gwen Shapir
la 2.10 in Kafka 0.11:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-
> 119%3A+Drop+Support+for+Scala+2.10+in+Kafka+0.11
>
> The vote will run for a minimum of 72 hours.
>
> Thanks,
> Ismael
>
--
*Gwen Shapira*
Product Manager | Confluent
650.450.2760 | @
lass name) for each connector
> that needs this functionality.
>
> I imagine this will be a rather uncontroversial addition, so if I don't see
> any comments in the next day or two I'll just start the vote thread.
>
> -Ewen
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
Gwen Shapira created KAFKA-4793:
---
Summary: Kafka Connect: POST /connectors/(string: name)/restart
doesn't start failed tasks
Key: KAFKA-4793
URL: https://issues.apache.org/jira/browse/KAFKA-4793
Gwen Shapira created KAFKA-4792:
---
Summary: Kafka Connect: Add ByteArray Converter
Key: KAFKA-4792
URL: https://issues.apache.org/jira/browse/KAFKA-4792
Project: Kafka
Issue Type: Improvement
ssing something ?
>
> On 23 February 2017 at 9:21:08 am, Gwen Shapira (g...@confluent.io) wrote:
>
> I saw them in Maven yesterday?
>
> On Wed, Feb 22, 2017 at 2:15 PM, Stephane Maarek
> <steph...@simplemachines.com.au> wrote:
> > Awesome thanks a lot! When sh
; Cosentino, Andrew Olson, Andrew Stevenson, Anton Karamanov, Antony
>> Stubbs, Apurva Mehta, Arun Mahadevan, Ashish Singh, Balint Molnar, Ben
>> Stopford, Bernard Leach, Bill Bejeck, Colin P. Mccabe, Damian Guy, Dan
>> Norwood, Dana Powers, dasl, Derrick Or, Dong Lin, Dustin Cote,
of the image approval.
>
> Thanks
>
> Gianluca Privitera
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
0102/documentation.html
>
> * Protocol:
> http://kafka.apache.org/0102/protocol.html
>
> * Successful Jenkins builds for the 0.10.2 branch:
> Unit/integration tests: https://builds.apache.org/job/kafka-0.10.2-jdk7/77/
> System tests: https://jenkins.confluent.io/job/system-test-kaf
ki.apache.org/confluence/display/KAFKA/KIP-98+-+Exactly+Once+Delivery+and+Transactional+Messaging
>
> Discussion thread can be found here:
>
> http://search-hadoop.com/m/Kafka/uyzND1jwZrr7HRHf?subj=+DISCUSS+KIP+98+Exactly+Once+Delivery+and+Transactional+Messaging
>
> Thanks,
>
&
above, and Streams can take
> care of it transparently.
>
> Thanks,
> Apurva
>
>
>
> On Fri, Feb 10, 2017 at 2:33 PM, Gwen Shapira <g...@confluent.io> wrote:
>
>> Thank you so much for the detailed explanation!
>> I got the READ COMMITTED behavior. It is v
ce`
> producer config which was added previously to the design document. By
> default, idempotence will be disabled. Down the road, it may make sense to
> change that, but we're uncomfortable turning it on in the first version
> because of the subtle changes in behavior (in particular,
t; > > > >> > > validating transactional.id (for every produce request)?
>> > > > > >> >
>> > > > > >> > 4. I understand that brokers cannot authorize the
>> transactional
>> > > id
>> > > > > for
>&
s typically don't abort
>> > > > > transactions, transactions will only be aborted by transaction
>> > > > coordinators
>> > > > > during hard failure of the producers, which should be rare.
>> > > > >
>> > > > > This way, the co
;apu...@confluent.io>
>> > > > wrote:
>> > > >
>> > > > > Hi Joel,
>> > > > >
>> > > > > The alternatives are embedded in the 'discussion' sections which
>> are
>> > > > spread
>> > > > > throughout the google doc.
>> > > > >
>> > > > > Admittedly, we have not covered high level alternatives like those
>> > > which
>> > > > > have been brought up in this thread. In particular, having a
>> separate
>> > > log
>> > > > > for transactional mesages and also having multiple producers
>> > > participate
>> > > > in
>> > > > > a single transaction.
>> > > > >
>> > > > > This is an omission which we will correct.
>> > > > >
>> > > > > Thanks,
>> > > > > Apurva
>> > > > >
>> > > > > On Wed, Dec 21, 2016 at 10:34 AM, Joel Koshy <jjkosh...@gmail.com>
>> > > > wrote:
>> > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > @Joel,
>> > > > > > >
>> > > > > > > I read over your wiki, and apart from the introduction of the
>> > > notion
>> > > > of
>> > > > > > > journal partitions --whose pros and cons are already being
>> > > > discussed--
>> > > > > > you
>> > > > > > > also introduce the notion of a 'producer group' which enables
>> > > > multiple
>> > > > > > > producers to participate in a single transaction. This is
>> > > completely
>> > > > > > > opposite of the model in the KIP where a transaction is defined
>> > by
>> > > a
>> > > > > > > producer id, and hence there is a 1-1 mapping between producers
>> > and
>> > > > > > > transactions. Further, each producer can have exactly one
>> > in-flight
>> > > > > > > transaction at a time in the KIP.
>> > > > > > >
>> > > > > >
>> > > > > > Hi Apurva - yes I did notice those differences among other things
>> > :)
>> > > > > BTW, I
>> > > > > > haven't yet gone through the google-doc carefully but on a skim
>> it
>> > > does
>> > > > > not
>> > > > > > seem to contain any rejected alternatives as the wiki states.
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
ll pass easily :)
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-121%3A+Add+KStream+peek+method
>
> I believe the PR attached is already in good shape to consider merging:
>
> https://github.com/apache/kafka/pull/2493
>
> Thanks!
> Steven
>
--
Gwen Shapira
Produ
gt; running, such that consumer will seek to the newly committed offset and
> start consuming from there?
>
> Not sure about this. I will recommend to keep it simple and ask user to
> stop consumers first. But I would considered it if the trade-offs are
> clear.
>
> @Matthias
>
> Ad
gt; On Tue, Feb 7, 2017 at 10:24 PM, Gwen Shapira <g...@confluent.io> wrote:
>
>> Thanks for the KIP. I'm super happy about adding the capability.
>>
>> I hate the interface, though. It looks exactly like the replica
>> assignment tool. A tool everyone loves s
:
> Hi all,
>
> I would like to propose a KIP to Add a tool to Reset Consumer Group Offsets.
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-122%3A+Add+a+tool+to+Reset+Consumer+Group+Offsets
>
> Please, take a look at the proposal and share your feedback.
>
> Tha
ince users can stay on
the older APIs as long as they want.
IMO, we can leave the packages separate forever and avoid pains of
merging them. Does anyone see downsides to separate packages?
On Tue, Feb 7, 2017 at 4:17 PM, Gwen Shapira <g...@confluent.io> wrote:
>>>- Personall
>
>> >
>> >
>> > >
>> > > Thanks.
>> > > Manikumar
>> > >
>> > >
>> > > >
>> > > > On Fri, Dec 23, 2016 at 9:26 AM, Manikumar <
>> manikumar.re...@gmail.com>
>> > > > wrote:
>> > > >
>> > > > > Hi,
>> > > > >
>> > > > > I would like to initiate the vote on KIP-48:
>> > > > >
>> > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-48+
>> > > > > Delegation+token+support+for+Kafka
>> > > > >
>> > > > >
>> > > > > Thanks,
>> > > > > Manikumar
>> > > > >
>> > > >
>> > >
>> >
>>
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
an't find "aggregate" method. So we need to make sure this thing
makes sense to new users (we can find a few to test on?).
Since moving stuff around a hierarchy is fairly easy, why not try one
way, leave things as "unstable" for one release and gather feedback?
We usually get u
[
https://issues.apache.org/jira/browse/KAFKA-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856964#comment-15856964
]
Gwen Shapira commented on KAFKA-4564:
-
OMG, this is great. I got this:
[2017-02-07 14:48:10,250
[
https://issues.apache.org/jira/browse/KAFKA-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856964#comment-15856964
]
Gwen Shapira edited comment on KAFKA-4564 at 2/7/17 10:51 PM:
--
OMG
ple things, like how many records have been
>>>> currently processed. The peek method would allow those kinds of
>>> diagnostics
>>>> and debugging.
>>>>
>>>> Gwen, it is possible to do this with the existing functionality like map,
>>&g
;>> > > like to do so in 0.10.2.0.
>>> > >
>>> > > Perhaps we should consider a slightly customized policy instead?
> Major
>>> > > deprecations like this might require something slightly different.
> For
>>> > > exam
ifferent. For
>> > > example, I think a KIP + release notes that explain we're marking the
>> > > consumer as deprecated now but it will continue to exist for at least 1
>> > > year (regardless of release versions) and will be removed in the next
>> > major
>&g
t;
>> Please consider my contribution and hopefully you all like it and agree that
>> it should be merged into 0.10.3 :)
>> If not, be gentle, this is my first KIP!
>>
>> Happy Monday,
>> Steven
>>
>
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
s KIP focus on one thing.
>
> As mentioned in a previous reply, we plan to have at least one more KIP
> to clean up DSL -- this future KIP should include exact this change.
>
>
> -Matthias
>
>
> On 2/6/17 4:26 PM, Gwen Shapira wrote:
>> I like the cleanup a lot :)
>
ri, Feb 3, 2017 at 3:33 PM, Matthias J. Sax <matth...@confluent.io> wrote:
> Hi All,
>
> I did prepare a KIP to do some cleanup some of Kafka's Streaming API.
>
> Please have a look here:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-120%3A+Cleanup+Kafka+Streams+builder+API
&
[
https://issues.apache.org/jira/browse/KAFKA-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira resolved KAFKA-4737.
-
Resolution: Duplicate
> Streams apps hang if started when brokers are not availa
[
https://issues.apache.org/jira/browse/KAFKA-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853423#comment-15853423
]
Gwen Shapira commented on KAFKA-4737:
-
It is! Sorry for the duplicate. I'll close this.
> Stre
Gwen Shapira created KAFKA-4737:
---
Summary: Streams apps hang if started when brokers are not
available
Key: KAFKA-4737
URL: https://issues.apache.org/jira/browse/KAFKA-4737
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira reassigned KAFKA-4733:
---
Assignee: Gwen Shapira
> Improve Streams Reset Tool console out
gt;> * Javadoc:
>> http://home.apache.org/~ewencp/kafka-0.10.2.0-rc0/javadoc/
>>
>> * Tag to be voted upon (off 0.10.2 branch) is the 0.10.2.0 tag:
>> https://git-wip-us.apache.org/repos/asf?p=kafka.git;a=tag;h=
>> 33ebac1f138f17b86002df05e55a9f5cff47f48a
>>
&g
[
https://issues.apache.org/jira/browse/KAFKA-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira resolved KAFKA-1776.
-
Resolution: Duplicate
> Re-factor out existing tools that have been implemented behind the
communicate
> with this cluster because the client version doesn't match the target
> cluster.
>
> There is no scope to upgrade the Kafka 8 cluster.
>
--
*Gwen Shapira*
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter <https://twitter.com/ConfluentInc> | blog
<http://www.confluent.io/blog>
2236) and was told it'd
> be best to doublecheck this with the mailing list first.
>
> Opinions?
>
> Also, is there any accompanying Scala/Java code that's already deprecated
> and should also be removed?
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
on the Admin protocol. Throughout this, he
displayed great technical judgment, high-quality work and willingness
to contribute where needed to make Apache Kafka awesome.
Thank you for your contributions, Grant :)
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
ed from true to false.
>
> https://cwiki.apache.org/confluence/display/KAFKA/%5BWIP%5D+KIP-106+-+Change+Default+unclean.leader.election.enabled+from+True+to+False
>
> B
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
; https://cwiki.apache.org/confluence/display/KAFKA/KIP-109%3A+Old+Consumer+Deprecation
> Discussion thread:
> https://www.mail-archive.com/dev@kafka.apache.org/msg63427.html
>
> Thanks.
> --Vahid
>
>
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
Policy:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-108
> %3A+Create+Topic+Policy
>
> The vote will run for a minimum of 72 hours.
>
> Thanks,
> Ismael
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
own. The other issue,
> as Jay pointed out, is that the current behavior of close() has an
> effectively small timeout, so this changes the behavior of existing code,
> which seems best to avoid.
>
> -Jason
>
> On Thu, Jan 5, 2017 at 3:09 PM, Gwen Shapira <g...@confluent.io> wro
quot; way out that does not involve downtime
> (specifically old and new consumers cannot correctly divide up partitions
> between themselves if both operate within the same group on the same topic).
>
> On Thu, Jan 5, 2017 at 3:10 PM, Gwen Shapira <g...@confluent.io> wrote:
>
&
t; We'd like to implement this deprecation in the upcoming 0.10.2.0 release.
>
> Thanks.
> --Vahid
>
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
jpmyaf...@mail.gmail.com%3e>,
>> > the changes are only in the close code path and hence the impact is not
>> too
>> > big. The existing close() method without a timeout will use a default
>> > timeout of 30 seconds.
>> >
>> > Thank you...
>> >
>> > Regards,
>> >
>> > Rajini
>> >
>>
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
).
>
> The discussion thread can be found here:
> https://www.mail-archive.com/dev@kafka.apache.org/msg59608.html
>
> The discussion around recent changes to the KIP starts here:
> https://www.mail-archive.com/dev@kafka.apache.org/msg62357.html
>
> Thank you for your feedback.
as part of
> Kafka?
>
> -Ewen
>
> On Wed, Jan 4, 2017 at 1:31 PM, Sriram Subramanian <r...@confluent.io> wrote:
>
>> +1
>>
>> On Wed, Jan 4, 2017 at 1:29 PM, Gwen Shapira <g...@confluent.io> wrote:
>>
>> > I would have preferred not to bundle t
KIP-66:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-66%3A+Single+Message+Transforms+for+Kafka+Connect
>
> Best,
>
> Shikhar
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
/display/KAFKA/KIP-101+-+Alter+Replication+Protocol+to+use+Leader+Epoch+rather+than+High+Watermark+for+Truncation
>
> <https://cwiki.apache.org/confluence/display/KAFKA/KIP-101+-+Alter+Replication+Protocol+to+use+Leader+Epoch+rather+than+High+Watermark+for+Truncation>
>
> Ple
>
> There is a PR for it here: https://github.com/apache/kafka/pull/2244
>
> Thanks,
> Damian
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
.apache.org/confluence/display/KAFKA/[WIP]+KIP-106+-+Change+Default+unclean.leader.election.enabled+from+True+to+False>
>
> Thanks
>
> B
>
> Ben Stopford
> Confluent, http://www.confluent.io <http://www.confluent.io/>
>
>
>
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
>> We will formally add the scala 2.12 support in future minor releases.
>>
>>
>> * Javadoc:
>> http://home.apache.org/~guozhang/kafka-0.10.1.1-rc1/javadoc/
>>
>> * Tag to be voted upon (off 0.10.0 branch) is the 0.10.0.1-rc0 tag:
>> https://git-wip-us.apache.org/repos/asf?p=kafka.git;a=tag;h=
>> c3638376708ee6c02dfe4e57747acae0126fa6e7
>>
>>
>> Thanks,
>> Guozhang
>>
>> --
>> -- Guozhang
>>
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
is waiting for your abstracts :)
--
Gwen Shapira
* Tag to be voted upon (off 0.10.0 branch) is the 0.10.0.1-rc0 tag:
> https://git-wip-us.apache.org/repos/asf?p=kafka.git;a=tag;h=c3638376708ee6c02dfe4e57747acae0126fa6e7
>
>
> Thanks,
> Guozhang
>
> --
> -- Guozhang
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
w
> All 4 brokers stopped on 1st machine
> 4 brokers are stopped on 2nd machine While we do this kafka
> controlled shutdown hangs
>
> This same issue was not seen with 25 topics.
>
> Please let us know if any solution is known to this issue
>
> Thanks
&g
let's say we were going to include some baked in; in that case, does
> anything look out of place to you in the list Shikhar has included in the
> KIP?
>
> -Ewen
>
> On Thu, Dec 15, 2016 at 2:01 PM, Gwen Shapira <g...@confluent.io> wrote:
>
> > I agree about the e
>
> In other cases, their functionality is already being implemented by
> connectors in divergent ways: RegexRouter, Insert, Replace, HoistToStruct,
> ExtractFromStruct
>
> On Wed, Dec 14, 2016 at 6:00 PM Gwen Shapira <g...@confluent.io> wrote:
>
> I'm a b
fka.log.AbstractIndex.trimToValidSize(AbstractIndex.
> scala:159)
> at kafka.log.Log.roll(Log.scala:772)
> at kafka.log.Log.maybeRoll(Log.scala:742)
> at kafka.log.Log.append(Log.scala:405)
> ... 16 more
> Caused by: java.lang.OutOfMemoryError: Map fai
e to do their data munging orthogonally to connectors,
> so
> > > that connectors can focus on the logic of how data should be copied
> > from/to
> > > datastores and Kafka.
> > >
> > >
> > > > In any case, we'd probably also have to change configs of connectors
> if
> > > we
> > > > allowed configs like that since presumably transformer configs will
> > just
> > > be
> > > > part of the connector config.
> > > >
> > >
> > > Yeah, haven't thought much about how all the configuration would tie
> > > together...
> > >
> > > I think we'd need the ability to:
> > > - spec transformer chain (fully-qualified class names? perhaps special
> > > aliases for built-in ones? perhaps third-party fqcns can be assigned
> > > aliases by users in the chain spec, for easier configuration and to
> > > uniquely identify a transformation when it occurs more than one time in
> a
> > > chain?)
> > > - configure each transformer -- all properties prefixed with that
> > > transformer's ID (fqcn / alias) get destined to it
> > >
> > > Additionally, I think we would probably want to allow for
> topic-specific
> > > overrides <https://issues.apache.org/jira/browse/KAFKA-3962> (e.g. you
> > > want
> > > certain transformations for one topic, but different ones for
> another...)
> > >
> >
> >
> >
> > --
> > Thanks,
> > Ewen
> >
>
--
*Gwen Shapira*
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter <https://twitter.com/ConfluentInc> | blog
<http://www.confluent.io/blog>
t; >
> > > authenticate using
> > >
> > >SCRAM-SHA-256, providing the delegation token HMAC as password.
> > >
> > >
> > >
> > > Updated the KIP with the following:
> > >
> > > 1. Protocol and Config changes
>
ctoring:
>
> https://cwiki.apache.org/confluence/display/KAFKA/Contributing+Website+
> Documentation+Changes
>
>
> We are trying to do the same for Connect, Ops, Configs, APIs etc in the
> near future. Any comments, improvements, and contributions are welcome and
> encouraged.
>
>
&
KAFKA/KIP-
> 90+-+Remove+zkClient+dependency+from+Streams
>
> Thanks,
> --Hojjat
>
--
*Gwen Shapira*
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter <https://twitter.com/ConfluentInc> | blog
<http://www.confluent.io/blog>
ail-archive.com/dev@kafka.apache.org/msg60955.html
>
> Thanks for your feedback.
>
> best,
> Colin McCabe
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
t the
>> right headers, and right now inserts the right audit information into the
>> message fields. If they exist, and assuming the message is Avro encoded.
>> What if someone wants to use JSON instead for a good reason? What if user X
>> wants to encrypt messages, but user
What if user X
>> wants to encrypt messages, but user Y does not? Maintaining the client
>> library is still much easier than maintaining the message formats.
>>
>>
>> -Todd
>>
>>
>>
>> On Thu, Dec 1, 2016 at 6:21 PM, Gwen Shapira <g...@co
> > require it for metrics changes.
>> > > >
>> > > > Here's the link to the KIP:
>> > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-
>> > > > 96+-+Add+per+partition+metrics+for+in-sync+and+
>> assigned+replica+count
>> > > >
>> > > > Thank you,
>> > > > Xavier
>> > > >
>> > >
>> > --
>> > Thanks,
>> > Neha
>> >
>>
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
ding to be in the weeds of dealing
> with customer data formats.
>
> Trust me, a sizable portion of my support time is spent dealing with schema
> issues. I really would like to get away from that. Maybe I'd have more time
> for other hobbies. Like writing. ;)
>
> -Todd
>
> On Thu,
ache.org/snapshots/ ,
> but I'm not seeing anything published there after 0.8.2.
>
> Thanks!
> Sean
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
nder a full +1?
>
> -Todd
>
>
> On Thu, Dec 1, 2016 at 1:59 PM, Gwen Shapira <g...@confluent.io> wrote:
>
>> I know why people who support headers support them, and I've seen what
>> the discussion is like.
>>
>> This is why I'm asking people who are against
implemented as opt-in plugins transmitting data over headers. this would
>>> keep the core wire format stable(r), core codebase smaller, and avoid the
>>> "burden of proof" thats sometimes required to prove a certain feature is
>>> useful enough for a w
gt; > >> > > > > reason that by providing unique string identifiers for
>> > each
>> > > header
>> > > >> > > > > everything will just
>> > > >> > > > > magically work for all parts of the str
t Apache Phoenix in Kafka
> Connect JDBC ?
>
> Thanks
> Alex
>
>
--
Gwen Shapira
Product Manager | Confluent
650.450.2760 | @gwenshap
Follow us: Twitter | blog
401 - 500 of 2807 matches
Mail list logo
