[
https://issues.apache.org/jira/browse/KAFKA-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reopened KAFKA-5336:
> ListGroup requires Describe on Cluster, but the command-line AclCommand tool
> does not allow this to
[
https://issues.apache.org/jira/browse/KAFKA-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5336.
Resolution: Fixed
Even though this was fixed by KAFKA-5292, it's a worth tracking the fix
separatel
Github user ijuma closed the pull request at:
https://github.com/apache/kafka/pull/3347
---
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 enabl
If confusion is the problem, then totally agree no point adding more
knobs. Perhaps you're right that users don't /really/ want
processing-time semantics. Just /think/ they want them until they start
considering replay/catch-up scenarios. I guess people rarely think about
those from the start (
I'm just thinking that having output into a topic every X seconds thanks to the
windowing could be a useful feature without using something interactive queries
that are really powerful (I love them) but aren't so useful in this scenario.
Using the caching parameter isn't useful in such scenario
Jeetu Bethina created KAFKA-5466:
Summary: Unable to fetch elements from WindowStore when timestamp
is before the first inserted Elem timestamp
Key: KAFKA-5466
URL: https://issues.apache.org/jira/browse/KAFKA-5466
Divya created KAFKA-5467:
Summary: setting offset retention minutes to a lower value is not
reflecting
Key: KAFKA-5467
URL: https://issues.apache.org/jira/browse/KAFKA-5467
Project: Kafka
Issue Type
Hi all,
I have raised a new KIP at
https://cwiki.apache.org/confluence/display/KAFKA/KIP-169+-+Lag-Aware+Partition+Assignment+Strategy
The corresponding JIRA is at
https://issues.apache.org/jira/browse/KAFKA-5337
I look forward to your feedback.
Regards,
Grant Neale
Hello Kafka users, developers and client-developers,
This is the second candidate for release of Apache Kafka 0.11.0.0.
This is a major version release of Apache Kafka. It includes 32 new KIPs. See
the release notes and release plan (https://cwiki.apache.org/conf
luence/display/KAFKA/Release+Plan
Github user guozhangwang commented on the issue:
https://github.com/apache/kafka-site/pull/56
cc @gwenshap
---
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,
Github user guozhangwang commented on the issue:
https://github.com/apache/kafka-site/pull/54
@sunnykrGupta Could you close this PR as 2389 on the kafka repo has been
merged? I will be reflected in the kafka-site repo in the next major release.
---
If your project is set up for it, y
Github user guozhangwang commented on the issue:
https://github.com/apache/kafka-site/pull/53
@restlessdesign thanks for the PR, could you submit the change on the kafka
repo: https://github.com/apache/kafka/tree/trunk/docs
which will be reflected here when a release is publis
Github user guozhangwang commented on the issue:
https://github.com/apache/kafka-site/pull/53
See:
https://cwiki.apache.org/confluence/display/KAFKA/Contributing+Website+Documentation+Changes
---
If your project is set up for it, you can reply to this email and have your
reply appear
GitHub user guozhangwang opened a pull request:
https://github.com/apache/kafka/pull/3366
MINOR: Remove version in the uses page
This is contributed by Hao Chen.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/guozhangwang/kafka
Github user guozhangwang commented on the issue:
https://github.com/apache/kafka-site/pull/49
Thanks the contribution @haoch , I have copied it to the kafka repo as
https://github.com/apache/kafka/pull/3366. cc @gwenshap
---
If your project is set up for it, you can reply to this em
Github user guozhangwang commented on the issue:
https://github.com/apache/kafka-site/pull/18
Copied this PR to https://github.com/apache/kafka/pull/3366.
---
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 do
Github user guozhangwang commented on the issue:
https://github.com/apache/kafka-site/pull/62
Corresponding jira list updated:
http://mail-archives.apache.org/mod_mbox/kafka-jira/.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Stephane Maarek created KAFKA-5468:
--
Summary: Change Source offset commit message to info to match Sink
behaviour
Key: KAFKA-5468
URL: https://issues.apache.org/jira/browse/KAFKA-5468
Project: Kafka
GitHub user simplesteph opened a pull request:
https://github.com/apache/kafka/pull/3367
KAFKA-5468 WorkerSourceTask offset commit loglevel changes
changed log level for source connector worker task when committing offsets
You can merge this pull request into a Git repository by run
This metric sounds simple and useful.
+1
On Fri, Jun 16, 2017 at 9:09 AM, Abhishek Mendhekar <
abhishek.mendhe...@gmail.com> wrote:
> Hi Kafka Dev,
>
> I created KIP-168 to propose adding a metric to emit total topic count
> in a cluster. The metric will be emited by the controller.
>
> The KIP
Hi devs,
a couple of weeks ago I opened the following PR related to a fix for the Kafka
Connect documentation on the web site :
https://github.com/apache/kafka/pull/3269
I modified the related files under "docs" directory. I see that same content is
on another repo (the kafka-site).
I opene
21 matches
Mail list logo