GitHub user ewencp opened a pull request:
https://github.com/apache/kafka/pull/3380
MINOR: Add serialized vagrant rsync until upstream fixes broken parallelism
See https://github.com/mitchellh/vagrant/issues/7531. The core of the issue
is that vagrant rsync uses a fixed set of 1000
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/3362
---
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
Jason Gustafson created KAFKA-5478:
--
Summary: TransactionsTest.testFencingOnAddPartitions Timeout
Key: KAFKA-5478
URL: https://issues.apache.org/jira/browse/KAFKA-5478
Project: Kafka
Issue T
GitHub user rhauch opened a pull request:
https://github.com/apache/kafka/pull/3379
KAFKA-5472 Eliminated duplicate group names when validating connector
results
Kafka Connect was adding duplicate group names in the response from the
REST API's validation of connector configuration
GitHub user mjsax opened a pull request:
https://github.com/apache/kafka/pull/3378
MINOR: explain producer naming within Streams
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mjsax/kafka minor-producer-naming
Alternatively you
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3377
KAFKA-5477: Lower retryBackoff for AddPartitionsRequest
This patch lowers the retry backoff when receiving a
CONCURRENT_TRANSACTIONS error from an AddPartitions request. The default of
100ms would
Apurva Mehta created KAFKA-5477:
---
Summary: TransactionalProducer sleeps unnecessarily long during
back to back transactions
Key: KAFKA-5477
URL: https://issues.apache.org/jira/browse/KAFKA-5477
Project:
No, only Apache Infra people have commit rights to the GitHub project. The
Kafka committers push to the Apache Git repo and that gets synced
automatically to GitHub. My understanding is that there is a desire to
avoid a situation where people can push directly to GitHub for provenance
reasons (I do
On Thu, Jun 8, 2017 at 5:00 PM, Ismael Juma wrote:
> One of the reasons why some PRs remain open even if they should be
> closed is that we have no way to close PRs ourselves without referencing
> them in a commit or asking Apache Infra for help. So, abandoned PRs tend to
> remain open. This is v
Colin P. McCabe created KAFKA-5476:
--
Summary: Implement a system test that creates network partitions
Key: KAFKA-5476
URL: https://issues.apache.org/jira/browse/KAFKA-5476
Project: Kafka
Iss
Ewen Cheslack-Postava created KAFKA-5475:
Summary: Connector config validation REST API endpoint not
including fields for transformations
Key: KAFKA-5475
URL: https://issues.apache.org/jira/browse/KAFKA-54
I'm going to update the KIP with new interface StateRestoreNotification
containing two methods, startRestore and endRestore.
While naming is very similar to methods already proposed on the
StateRestoreListener, the intent of these methods is not for user
notification of restore status. Instead th
GitHub user hachikuji opened a pull request:
https://github.com/apache/kafka/pull/3376
MINOR: MemoryRecordsBuilder.sizeInBytes should consider initial position
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hachikuji/kafka recor
GitHub user mjsax opened a pull request:
https://github.com/apache/kafka/pull/3375
KAFKA-5474: Streams StandbyTask should no checkpoint on commit if EOS is
enabled
- actual fix for `StandbyTask#commit()`
Additionally (for debugging):
- EOS test, does not report "expected"
Matthias J. Sax created KAFKA-5474:
--
Summary: Streams StandbyTask should no checkpoint on commit if EOS
is enabled
Key: KAFKA-5474
URL: https://issues.apache.org/jira/browse/KAFKA-5474
Project: Kafka
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3374
KAFKA-5032: Update the docs for message size configs across the board
Before 0.11, we used to have limits for maximum message size on the
producer, broker, and consumer side.
From 0.11 onwa
Jun Rao created KAFKA-5473:
--
Summary: handle ZK session expiration properly when a new session
can't be established
Key: KAFKA-5473
URL: https://issues.apache.org/jira/browse/KAFKA-5473
Project: Kafka
Randall Hauch created KAFKA-5472:
Summary: Connector validate REST endpoint returning duplicate
entries in "groups"
Key: KAFKA-5472
URL: https://issues.apache.org/jira/browse/KAFKA-5472
Project: Kafka
Github user hachikuji commented on a diff in the pull request:
https://github.com/apache/kafka-site/pull/60#discussion_r122826323
--- Diff: 0110/design.html ---
@@ -264,21 +264,22 @@
messages have a primary key and so the updates are idempotent
(receiving the same message
Github user hachikuji commented on a diff in the pull request:
https://github.com/apache/kafka-site/pull/60#discussion_r122825810
--- Diff: 0110/design.html ---
@@ -264,21 +264,22 @@
messages have a primary key and so the updates are idempotent
(receiving the same message
GitHub user hachikuji opened a pull request:
https://github.com/apache/kafka/pull/3373
MINOR: Detail message/batch size implications for conversion between old
and new formats
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hach
Thanks everyone. Great discussion.
Because these Read or Write actions are interpreted in conjunction with
particular resources (Topic, Group, ...) it would also make more sense to
me that for committing offsets the ACL should be (Group, Write).
So, a consumer would be required to have (Topic, R
Github user wlsc closed the pull request at:
https://github.com/apache/kafka/pull/2706
---
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 enable
Github user guozhangwang commented on the issue:
https://github.com/apache/kafka-site/pull/62
Thanks for the reviews @ijuma , updated the pr.
---
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 t
Github user guozhangwang commented on a diff in the pull request:
https://github.com/apache/kafka-site/pull/62#discussion_r122784013
--- Diff: contact.html ---
@@ -19,6 +19,9 @@
comm...@kafka.apache.org: A list to track Kafka
commi
[
https://issues.apache.org/jira/browse/KAFKA-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-5465.
Resolution: Won't Fix
For the reasons mentioned by Ismael above, we've decided not to fix th
Yes it is, more of an oversight on my part, I'll remove it from the KIP.
On Mon, Jun 19, 2017 at 12:48 PM, Matthias J. Sax
wrote:
> Hi,
>
> I thinks for now it's good enough to start with a single global restore
> listener. We can incrementally improve this later on if required. Of
> course, if
Hi,
I thinks for now it's good enough to start with a single global restore
listener. We can incrementally improve this later on if required. Of
course, if it's easy to do right away we can also be more fine grained.
But for KTable, we might want to add this after getting rid of all the
overloads
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/3279
---
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
GitHub user restlessdesign opened a pull request:
https://github.com/apache/kafka/pull/3372
Provide link to ZooKeeper within Quickstart
This adds a hyperlink to the ZooKeeper project within the quickstart
tutorial for users who may be unfamiliar with ZooKeeper or who simply want a
Github user restlessdesign commented on the issue:
https://github.com/apache/kafka-site/pull/53
See: https://github.com/apache/kafka/pull/3372
---
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
Github user restlessdesign closed the pull request at:
https://github.com/apache/kafka-site/pull/53
---
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 feat
Github user restlessdesign commented on the issue:
https://github.com/apache/kafka-site/pull/53
No problem!
---
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,
Jeremy Hanna created KAFKA-5471:
---
Summary: Original Kafka paper link broken
Key: KAFKA-5471
URL: https://issues.apache.org/jira/browse/KAFKA-5471
Project: Kafka
Issue Type: Bug
Compon
GitHub user ijuma opened a pull request:
https://github.com/apache/kafka/pull/3371
KAFKA-5470: Replace -XX:+DisableExplicitGC with
-XX:+ExplicitGCInvokesConcurrent in kafka-run-class
You can merge this pull request into a Git repository by running:
$ git pull https://github.c
Ismael Juma created KAFKA-5470:
--
Summary: Replace -XX:+DisableExplicitGC with
-XX:+ExplicitGCInvokesConcurrent in kafka-run-class
Key: KAFKA-5470
URL: https://issues.apache.org/jira/browse/KAFKA-5470
Pro
Thanks Tom, that sounds great. And I agree about your comment regarding RC0
to RC1 changes.
Ismael
On Mon, Jun 19, 2017 at 3:15 PM, Tom Crayford wrote:
> Hello,
>
> Heroku has been testing 0.11.0.0 RC0, mostly focussed on backwards
> compatibility and performance. So far, we note a slight perfo
Hello,
Heroku has been testing 0.11.0.0 RC0, mostly focussed on backwards
compatibility and performance. So far, we note a slight performance
increase from older versions when using not-current clients
Testing a 0.9 client against 0.10.2.1 vs 0.11.0.0 rc0: 0.11.0.0 rc0 has
slightly higher through
Sure, 13 blockers were fixed:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20priority%20%3D%20Blocker%20AND%20fixVersion%20%3D%200.11.0.0%20AND%20resolved%20%3E%3D%20-10d%20ORDER%20BY%20updated%20DESC
Ismael
On Mon, Jun 19, 2017 at 1:44 PM, Tom Crayford wrote:
> Is th
Github user ijuma commented on a diff in the pull request:
https://github.com/apache/kafka-site/pull/62#discussion_r122709472
--- Diff: contact.html ---
@@ -19,6 +19,9 @@
comm...@kafka.apache.org: A list to track Kafka
commits. To
Is there a summary of which blockers were fixed in RC0 somewhere?
On Mon, Jun 19, 2017 at 1:41 PM, Eno Thereska
wrote:
> +1 (non-binding) passes Kafka Streams tests.
>
> Thanks,
> Eno
> > On 19 Jun 2017, at 06:49, Magnus Edenhill wrote:
> >
> > +1 (non-binding)
> >
> > Passes librdkafka integra
GitHub user matzew opened a pull request:
https://github.com/apache/kafka/pull/3370
making util classes final and adding private ctor
Utils with static methods should not be instantiated, hence marking the
classes `final` and adding a `private` constructor.
this is consiste
+1 (non-binding) passes Kafka Streams tests.
Thanks,
Eno
> On 19 Jun 2017, at 06:49, Magnus Edenhill wrote:
>
> +1 (non-binding)
>
> Passes librdkafka integration tests (v0.9.5 and master)
>
>
> 2017-06-19 0:32 GMT+02:00 Ismael Juma :
>
>> Hello Kafka users, developers and client-developers,
GitHub user tombentley opened a pull request:
https://github.com/apache/kafka/pull/3369
Improve the documentation around ACLs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tombentley/kafka doc-acl
Alternatively you can review
GitHub user ppatierno opened a pull request:
https://github.com/apache/kafka/pull/3368
KAFKA-5469: Created state changelog topics not logged correctly
Fixed debug logging for the created state changelog topics
Added toString() for InternalTopicMetadata and InternalTopicConfig for
Paolo Patierno created KAFKA-5469:
-
Summary: Created state changelog topics not logged correctly
Key: KAFKA-5469
URL: https://issues.apache.org/jira/browse/KAFKA-5469
Project: Kafka
Issue Typ
Github user dguy closed the pull request at:
https://github.com/apache/kafka/pull/3255
---
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 enable
47 matches
Mail list logo
