be the case, we only have about 3
dependencies listed there but pull in close to 90 jars (though some of
those jars may be released/licensed together). These should be cleaned up.
-Ewen
On Fri, Mar 19, 2021 at 6:51 PM Justin Mclean wrote:
> Hi,
>
> I was taking a look at this release
+1 (binding)
This will be a nice improvement. From the discussion thread it's clear this
is tricky to get right, nice work!
On Tue, May 19, 2020 at 8:16 AM Andrew Schofield
wrote:
> +1 (non-binding)
>
> This is now looking very nice.
>
> Andrew Schofield
>
> On 19/05/2020, 16:11, "Randall Hauc
bly even providing a pre-shaded version
for convenience). The latter is more than we probably want to do here and
probably has to actually wait for major version, but former might be doable.
-Ewen
On Mon, Nov 18, 2019 at 9:06 AM Mickael Maison
wrote:
> +1 (binding)
> Thanks for the KIP
>
&
seems like this should probably be tied to some
corresponding group timeout, e.g. maybe the session.timeout.
-Ewen
On Tue, Sep 24, 2019 at 11:37 AM Konstantine Karantasis <
konstant...@confluent.io> wrote:
> Nicely done!
>
> +1 (non-binding)
>
> Konstantine
>
> On Tue
+1
-Ewen
On Thu, Mar 21, 2019 at 10:33 AM Harsha wrote:
> +1 (non-bidning)
> - Download artifacts, setup 3 node cluster
> - Ran producer/consumer clients
>
> Thanks,
> Harsha
>
> On Thu, Mar 21, 2019, at 5:54 AM, Andrew Schofield wrote:
> > +1 (non-binding)
>
[
https://issues.apache.org/jira/browse/KAFKA-7813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7813.
--
Resolution: Fixed
Fix Version/s: 2.3.0
Issue resolved by pull request
+1 (binding)
-Ewen
On Wed, Mar 13, 2019 at 2:04 PM Randall Hauch wrote:
> Excellent work, Konstantine!
>
> +1 (binding)
>
> On Mon, Mar 11, 2019 at 8:05 PM Konstantine Karantasis <
> konstant...@confluent.io> wrote:
>
> > Thanks Jason!
> > That makes pe
[
https://issues.apache.org/jira/browse/KAFKA-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7834.
--
Resolution: Fixed
Fix Version/s: (was: 1.1.2
won't ever get to v2 anyway...
-Ewen
On Fri, Jan 25, 2019 at 9:38 AM Jason Gustafson wrote:
> Hey Konstantine,
>
> Thanks for the reply. Just one response below:
>
> In 'compatible' mode, the worker sends both protocols to the broker
> > coordinator during th
constructor to encourage
people to update. Further, if we're worried about confusion about how to
load the two files, we could have a constructor that does that default
pattern for you.
-Ewen
On Thu, Jan 24, 2019 at 11:36 AM Colin McCabe wrote:
> On Thu, Jan 24, 2019, at 11:25, TEJA
iding the extra
config might be worth the not-quite-perfect compatibility story.
-Ewen
On Tue, Sep 11, 2018 at 7:01 AM Stephane Maarek <
steph...@simplemachines.com.au> wrote:
> +1 (non binding)
>
> On Tue., 11 Sep. 2018, 10:48 am Mickael Maison,
> wrote:
>
> > +1 (non
[
https://issues.apache.org/jira/browse/KAFKA-7461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7461.
--
Resolution: Fixed
Fix Version/s: 2.2.0
Issue resolved by pull request
[
https://issues.apache.org/jira/browse/KAFKA-7503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7503.
--
Resolution: Fixed
Fix Version/s: 2.0.2
2.1.1
rstand the compatibility
story here (which could also be that we just don't provide one -- just want
to make sure it is clear).
I may have missed something in this proposal since it's pretty long, let me
know if there was something obvious I overlooked.
Thanks,
-Ewen
On Mon, Dec 31, 201
f interpolation were supported in the
config value (as we now do with managed secrets). For example, it could
support something like client.id=connector-${taskId} and the task ID would
be substituted automatically into the string.
I don't necessarily like that solution (seems complicated and n
[
https://issues.apache.org/jira/browse/KAFKA-7551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7551.
--
Resolution: Fixed
Merged [https://github.com/apache/kafka/pull/5842,] my bad
[
https://issues.apache.org/jira/browse/KAFKA-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7620.
--
Resolution: Fixed
Fix Version/s: 2.0.2
2.1.1
lines, is there actually a need for TopicSettings class? We
already have NewTopic in the AdminClient APIs. Does that not suffice?
-Ewen
On Mon, Sep 24, 2018 at 11:56 AM Andrew Otto wrote:
> FWIW, I’d find this feature useful.
>
> On Mon, Sep 24, 2018 at 2:42 PM Randall Hauch wrote:
>
> > R
[
https://issues.apache.org/jira/browse/KAFKA-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7560.
--
Resolution: Fixed
Fix Version/s: 2.1.0
2.2.0
Issue
+1
-Ewen
On Thu, Nov 1, 2018 at 10:10 AM Manikumar wrote:
> We were waiting for the system test results. There were few failures:
> KAFKA-7579, KAFKA-7559, KAFKA-7561
> they are not blockers for 2.0.1 release. We need more votes from
> PMC/committers :)
>
> Thanks Stanisl
[
https://issues.apache.org/jira/browse/KAFKA-6490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-6490.
--
Resolution: Fixed
Fix Version/s: 2.0.0
Closing as this is effectively
[
https://issues.apache.org/jira/browse/KAFKA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-5117.
--
Resolution: Duplicate
Assignee: Ewen Cheslack-Postava
Fix
[
https://issues.apache.org/jira/browse/KAFKA-7476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7476.
--
Resolution: Fixed
Fix Version/s: 2.1.0
0.10.2.3
ka Connect already has a couple
of Connectors for. Could you clarify what format/serialization/use case
PLC4X has?
-Ewen
On Wed, Aug 15, 2018 at 7:43 AM Christofer Dutz
wrote:
> Hi all,
>
> I am one of the Apache PLC4X (incubating) committers and am looking for
> people willing to
n immediate compatibility
commitment (compatibility across versions of AK broker & Connect, as well
as upgrade & API & config compatibility for the connector itself.
-Ewen
On Sun, Sep 30, 2018 at 1:44 PM Matthias J. Sax
wrote:
> I am not aware of anything like this. And I also t
[
https://issues.apache.org/jira/browse/KAFKA-7460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7460.
--
Resolution: Fixed
Fix Version/s: 2.1.0
2.0.1
Ewen Cheslack-Postava created KAFKA-7461:
Summary: Connect Values converter should have coverage of logical
types
Key: KAFKA-7461
URL: https://issues.apache.org/jira/browse/KAFKA-7461
Project
Ewen Cheslack-Postava created KAFKA-7460:
Summary: Connect Values converter uses incorrect date format string
Key: KAFKA-7460
URL: https://issues.apache.org/jira/browse/KAFKA-7460
Project
[
https://issues.apache.org/jira/browse/KAFKA-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7434.
--
Resolution: Fixed
Fix Version/s: 2.1.0
2.0.1
Issue
[
https://issues.apache.org/jira/browse/KAFKA-4932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-4932.
--
Resolution: Fixed
Issue resolved by pull request 4438
[https://github.com
[
https://issues.apache.org/jira/browse/KAFKA-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7353.
--
Resolution: Fixed
Fix Version/s: 2.1.0
2.0.1
[
https://issues.apache.org/jira/browse/KAFKA-7242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7242.
--
Resolution: Fixed
Fix Version/s: 2.1.0
2.0.1
Issue
nnect modules are considered
internal implementation details.
-Ewen
On Fri, Jul 27, 2018 at 7:15 PM Chia-Ping Tsai wrote:
> hi Kafka
>
> There is a section[1] listing the packages which have public interfaces.
> However, it doesn't include any connect-related packages. It would
[
https://issues.apache.org/jira/browse/KAFKA-7225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7225.
--
Resolution: Fixed
> Kafka Connect ConfigProvider not invoked before validat
[
https://issues.apache.org/jira/browse/KAFKA-7228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7228.
--
Resolution: Fixed
> DeadLetterQueue throws a NullPointerExcept
x27;t the methods on Source also be
Optional types?
-Ewen
On Mon, Jul 30, 2018 at 11:13 PM Damian Guy wrote:
> Hi Nishanth,
>
> I have one nit on the KIP. I think the topicNameExtractor method should
> return Optional rather than null.
> Sorry I'm late here.
>
> Than
[
https://issues.apache.org/jira/browse/KAFKA-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7068.
--
Resolution: Fixed
Fix Version/s: 2.1.0
Issue resolved by pull request
[
https://issues.apache.org/jira/browse/KAFKA-7047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7047.
--
Resolution: Fixed
Reviewer: Ewen Cheslack-Postava
Fix Version/s
[
https://issues.apache.org/jira/browse/KAFKA-7039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7039.
--
Resolution: Fixed
Fix Version/s: 2.1.0
Issue resolved by pull request
[
https://issues.apache.org/jira/browse/KAFKA-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7056.
--
Resolution: Fixed
Fix Version/s: 2.1.0
Issue resolved by pull request
[
https://issues.apache.org/jira/browse/KAFKA-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7009.
--
Resolution: Fixed
Fix Version/s: 2.1.0
0.11.0.3
[
https://issues.apache.org/jira/browse/KAFKA-7031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7031.
--
Resolution: Fixed
Fix Version/s: 2.1.0
Issue resolved by pull request
[
https://issues.apache.org/jira/browse/KAFKA-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7043.
--
Resolution: Fixed
Fix Version/s: 2.1.0
Issue resolved by pull request
[
https://issues.apache.org/jira/browse/KAFKA-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-7003.
--
Resolution: Fixed
Fix Version/s: 2.1.0
2.0.0
Issue
[
https://issues.apache.org/jira/browse/KAFKA-6997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-6997.
--
Resolution: Fixed
Issue resolved by pull request 5139
[https://github.com
[
https://issues.apache.org/jira/browse/KAFKA-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-6981.
--
Resolution: Fixed
Issue resolved by pull request 5125
[https://github.com
+1 (binding)
Just follow up on the existing version of the KIP, so nothing new here.
Possibly a bit disruptive given how quick the 1.0 -> 2.0 jump happened, but
it's the right time to remove it.
-Ewen
On Thu, May 24, 2018 at 8:13 AM Viktor Somogyi
wrote:
> +1 (non-binding)
>
>
Sorry for the delay, didn't see this until now. I've given you edit
permissions on the wiki.
-Ewen
On Tue, May 15, 2018 at 2:21 PM McCaig, Rhys
wrote:
> Hi Team,
>
> Would someone be able to provide me with Confluence permission in order to
> write a KIP for the below
[
https://issues.apache.org/jira/browse/KAFKA-5807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-5807.
--
Resolution: Fixed
Fix Version/s: 2.0.0
Issue resolved by pull request
+1 (binding)
-Ewen
On Tue, May 22, 2018 at 9:29 AM Ted Yu wrote:
> +1
>
> On Tue, May 22, 2018 at 9:19 AM, Randall Hauch wrote:
>
> > I'd like to start a vote of a very straightforward proposal for Connect
> to
> > add converters for the basic primitive numb
Sorry, probably not ideal to just be seeing this now given KIP deadline,
but in general straightforward ones where we expect things to be
uncontroversial, I think its fine to kick off a vote thread. Worst case we
have people re-file votes if something substantial changes in the proposal.
-Ewen
ere fundamentally it
does not fit into your k8s/mesos/container + CI/CD workflow to do anything
other than pass configs in via command line flags? Or is it mostly the pain
of too many topics? Or something else?
-Ewen
On Fri, May 18, 2018 at 4:47 AM Saulius Valatka
wrote:
> Hi,
>
> thanks
On Mon, May 21, 2018 at 12:39 PM Arjun Satish
wrote:
> Thanks a lot, Ewen! I'll make sure the documentation is clear on the
> differences between retries an tolerance.
>
> Do you think percentage would have the same problem as the one you brought
> up? Also, if we say 10% t
+1 binding. I had one last comment in the DISCUSS thread, but not really a
blocker.
-Ewen
On Mon, May 21, 2018 at 9:48 AM Matthias J. Sax
wrote:
> +1 (binding)
>
>
>
> On 5/21/18 9:30 AM, Randall Hauch wrote:
> > Thanks, Arjun. +1 (non-binding)
> >
> > Regards
olute value or something like a
percentage? Given the current way of setting things, I'm not sure I'd ever
set it to anything but -1 or 0, with maybe 1 as an easy option for
restarting a connector to get it past one bad message, then reverting back
to -1 or 0.
-Ewen
On Mon, May 21, 2018 at
ebody finds them useful for something if they exist.
-Ewen
On Fri, May 18, 2018 at 11:55 AM Randall Hauch wrote:
> Thanks, Ewen.
>
> You make several good points, and I've updated the KIP to hopefully address
> your comments. I think the symmetry with the Kafka serdes is useful
[
https://issues.apache.org/jira/browse/KAFKA-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-6566.
--
Resolution: Fixed
> SourceTask#stop() not called after exception raised in p
s -- instead of delivering the raw
data, we potentially lose raw data & schema info because we're rendering it
as JSON. Not sure that's a good idea...
I think that last item might be the biggest concern to me -- DLQ formats
and control over content & reprocessing seems a bit unclea
+1 (binding)
Thanks,
Ewen
On Thu, May 17, 2018 at 12:16 PM Ted Yu wrote:
> +1
> Original message From: Gwen Shapira
> Date: 5/17/18 12:02 PM (GMT-08:00) To: dev
> Subject: Re: [VOTE] KIP-285: Connect Rest Extension Plugin
> LGTM. +1.
>
> On Wed, Ma
Yup, thanks for the changes. The 'health' package in particular feels like
a nice fit given the way we expect it to be used.
-Ewen
On Wed, May 16, 2018 at 7:02 PM Randall Hauch wrote:
> Looks good to me. Thanks for quickly making the changes! Great work!
>
> Best regards,
&
hink this is fine as
I don't think there are truly common secrets provider
formats/apis/protocols, just want to make sure it is clear.
Thanks,
Ewen
On Thu, May 17, 2018 at 6:19 PM Ted Yu wrote:
> +1
> Original message From: Magesh Nandakumar <
> mage...@co
spend time and effort building and maintaining them.
Otherwise, this seems simple and straightforward. Generally +1 on the
proposal.
-Ewen
On Thu, May 17, 2018 at 6:04 PM Magesh Nandakumar
wrote:
> Thanks Randall for the KIP. I think it will be super useful and looks
> pretty straightforw
r metrics.
* Currently we have the State classes nested inside ConnectorHealth class.
I think this makes those classes more annoying to use. Is there a reason
for them to be nested or can we just pull them out to the same level as
ConnectorHealth?
-Ewen
On Tue, May 15, 2018 at 9:30 AM Magesh Nandaku
[
https://issues.apache.org/jira/browse/KAFKA-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-5141.
--
Resolution: Fixed
Assignee: Ewen Cheslack-Postava
Not sure of the fix
On Thu, Apr 5, 2018 at 3:28 PM, Matthias J. Sax
wrote:
> Ewen,
>
> I cannot completely follow your argument. Can you elaborate a little
> bit? After reading you mail, I am not sure if you prefer config
> inheritance or not? And if, to what extend?
>
So we've had issues wi
enges in Connect don't appear here
(e.g. conflicts in producer/consumer config naming, since this is a
Consumer-only KIP), but similar problems arise.
-Ewen
On Wed, Apr 4, 2018 at 10:56 PM, Boyang Chen wrote:
> Thanks Guozhang! I already updated the pull request and KIP to deprecate
&g
[
https://issues.apache.org/jira/browse/KAFKA-6728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-6728.
--
Resolution: Fixed
Fix Version/s: 1.1.1
1.2.0
Issue
+1 (binding)
The incompatibility is unfortunate, but seems unlikely to cause a problem
in practice. Let's just make sure there's a note in the upgrade notes about
the incompatibility when we have a PR for this.
-Ewen
On Fri, Mar 30, 2018 at 10:22 AM, Jun Rao wrote:
> Hi, Allen,
&
shouldn't revisit, just that it might also be a faster way to get to a full
understanding of the options, concerns, and tradeoffs).
-Ewen
On Thu, Mar 22, 2018 at 7:19 AM, Richard Yu
wrote:
> I do have one question though: in the current KIP, throwing
> TimeoutException to mark
> that
y start running
multiple Connect clusters but forget to make some of the default settings
unique. I'd probably start by looking into that possibility to debug this
issue.
-Ewen
On Wed, Mar 21, 2018 at 10:15 PM, Ziliang Chen wrote:
> Hi,
>
> I have 2 Kafka Connect instances runs i
ST API, we'd have to address these issues
anyway.
-Ewen
On Mon, Mar 19, 2018 at 2:33 PM, Matt Farmer wrote:
> What’s the status of this? This is a pretty hard blocker for us to meet
> requirements internally to deploy connect in a distributed fashion.
>
> @Ewen - Regarding
investigate.
>
Interesting. I think you're right that we're probably just reporting
*assigned* tasks with the task-count metric rather than active tasks. I
think an active tasks metric would be reasonable, though since you really
need to look at the aggregate across workers, I'm not sure it's the best
for alerting.
Maybe an unhealthy/dead tasks count metric would be better? You can alert
on that directly without having to aggregate across workers.
-Ewen
>
> ---
>
> I would love thoughts on all of the above from anyone on this list.
>
> Thanks,
>
> Matt Farmer
Ewen Cheslack-Postava created KAFKA-6676:
Summary: System tests do not handle ZK chroot properly with SCRAM
Key: KAFKA-6676
URL: https://issues.apache.org/jira/browse/KAFKA-6676
Project: Kafka
Thanks for voting everyone, KIP is accepted with 5 binding +1 and 5
non-binding +1s.
PR is already merged and there are upgrade notes about the potential memory
impact.
-Ewen
On Wed, Mar 7, 2018 at 9:25 PM, Ted Yu wrote:
> +1
> Original message From: Guozhang Wang
>
[
https://issues.apache.org/jira/browse/KAFKA-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-5999.
--
Resolution: Invalid
Assignee: Ewen Cheslack-Postava
Closing as Invalid
erters that fail to preserve that
information.
-Ewen
On Tue, Mar 6, 2018 at 3:29 AM, Gunnar Morling wrote:
> Hi,
>
> A user of the Debezium CDC Kafka Connect connectors has asked whether we
> could provide information about the original source type of captured table
> columns.
>
Comar, Ewen Cheslack-Postava, Filipe Agapito, fredfp,
Guozhang Wang, huxihx, Ismael Juma, Jason Gustafson, Jeremy Custenborder,
Jiangjie (Becket) Qin, Joel Hamill, Konstantine Karantasis, lisa2lisa, Logan
Buckley, Manjula K, Matthias J. Sax, Nick Chiu, parafiend, Rajini Sivaram,
Randall Hauch, R
[
https://issues.apache.org/jira/browse/KAFKA-5471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-5471.
--
Resolution: Fixed
Assignee: Ewen Cheslack-Postava
Updated the link to
ow up
with those in subsequent KIPs, see the discussion thread for details. Also
note this is related, but complementary, to
https://cwiki.apache.org/confluence/display/KAFKA/KIP-211%3A+Revise+Expiration+Semantics+of+Consumer+Group+Offsets
.
And of course +1 (binding) from me.
Thanks,
Ewen
he vote thread so we can get this fixed for the next
version.
-Ewen
On Fri, Oct 6, 2017 at 11:00 AM, Manikumar
wrote:
> looks like VOTE thread is *NOT* started for this KIP.
>
> On Fri, Oct 6, 2017 at 11:23 PM, Manikumar
> wrote:
>
> > looks like VOTE thread is started
[
https://issues.apache.org/jira/browse/KAFKA-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-4854.
--
Resolution: Not A Bug
Assignee: Ewen Cheslack-Postava
This behavior is
Thanks everyone for voting. This passes with 3 binding +1, 5 non-binding
+1, and no dissenting votes.
I'll work on getting the release finalized and send out an announcement
when it is ready.
-Ewen
On Tue, Feb 27, 2018 at 11:18 PM, Jason Gustafson
wrote:
> +1. Verified artifacts and
d by folks from Elastic or
the sarama project.
-Ewen
On Fri, Feb 9, 2018 at 7:11 AM, Sandeep Sarkar
wrote:
> Hi All,
>
>
>
> I am using filebeat 6.1 and kafka 0.11.0.1 to push logs. From filebeat
> logs I could see that communication is getting established but then logs
> are
The web page is more about general project info and might be of interest to
people beyond just developers. But I agree the wiki landing page could use
some updating. Even more than just the developer section as we're missing
several releases, the oldest ones are listed at the top, etc.
-Ewe
[
https://issues.apache.org/jira/browse/KAFKA-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-6236.
--
Resolution: Cannot Reproduce
Unresponsive, so we can't track this down. P
[
https://issues.apache.org/jira/browse/KAFKA-6239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-6239.
--
Resolution: Duplicate
> Consume group hung into rebalancing state, now str
[
https://issues.apache.org/jira/browse/KAFKA-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-6439.
--
Resolution: Not A Bug
> "com.streamsets.pipeline.api.StageException:
Ewen Cheslack-Postava created KAFKA-6580:
Summary: Connect bin scripts have incorrect usage
Key: KAFKA-6580
URL: https://issues.apache.org/jira/browse/KAFKA-6580
Project: Kafka
Issue
com/apache/kafka/tree/1.0.1-rc2
* Documentation:
http://kafka.apache.org/10/documentation.html
* Protocol:
http://kafka.apache.org/10/protocol.html
/**
Thanks,
Ewen Cheslack-Postava
ter the PR is merged.
-Ewen
On Fri, Feb 16, 2018 at 3:53 AM, Mickael Maison
wrote:
> Ran tests from source and quickstart with binaries
>
> +1 (non-binding)
>
> On Fri, Feb 16, 2018 at 6:05 AM, Jason Gustafson
> wrote:
> > +1. Verified artifacts and ran quickstart. Than
[
https://issues.apache.org/jira/browse/KAFKA-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-6503.
--
Resolution: Fixed
Fix Version/s: 1.2.0
Issue resolved by pull request
And of course I'm +1 since I've already done normal release validation
before posting this.
-Ewen
On Mon, Feb 12, 2018 at 10:15 AM, Ewen Cheslack-Postava
wrote:
> Hello Kafka users, developers and client-developers,
>
> This is the second candidate for release of Apache Ka
che.org/10/documentation.html
* Protocol:
http://kafka.apache.org/10/protocol.html
Thanks,
Ewen Cheslack-Postava
Just a heads up that we had a fix for KAFKA-6529 land to fix a file
descriptor leak. So this RC is dead and I'll be generating RC1 soon.
Thanks,
Ewen
On Wed, Feb 7, 2018 at 11:06 AM, Vahid S Hashemian <
vahidhashem...@us.ibm.com> wrote:
> Hi Ewen,
>
> +1
>
> Building f
[
https://issues.apache.org/jira/browse/KAFKA-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-6513.
--
Resolution: Fixed
Fix Version/s: 1.2.0
Issue resolved by pull request
affects
everyone contributing to the project, I figured I'd send this quick note to
increase the likelihood people see it and have a chance to weigh in.
Thanks,
-Ewen
.
This requires "closing" two separate staging repos to get everything
released.
If things look good now, I can update the release script/instructions to
make this clearer.
-Ewen
On Mon, Feb 5, 2018 at 9:59 PM, Ewen Cheslack-Postava
wrote:
> Not sure, seems to be variable. I "clo
doesn't show up for
too long or we need a follow up RC, I'll just extend/restart the process.
-Ewen
On Mon, Feb 5, 2018 at 8:21 PM, Ted Yu wrote:
> Ewen:
> Do you know how long it takes for maven repo to be populated ?
>
> Looking at:
> https://repository.apache.org/con
d from everyone.
Thanks,
Ewen
Ewen Cheslack-Postava created KAFKA-6536:
Summary: Streams quickstart pom.xml is missing versions for a
bunch of plugins
Key: KAFKA-6536
URL: https://issues.apache.org/jira/browse/KAFKA-6536
1 - 100 of 2082 matches
Mail list logo
