[
https://issues.apache.org/jira/browse/KAFKA-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-3486:
-
Resolution: Fixed
Fix Version/s: 0.10.1.0
Status: Resolved (was:
[
https://issues.apache.org/jira/browse/KAFKA-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223132#comment-15223132
]
ASF GitHub Bot commented on KAFKA-3486:
---
Github user asfgit closed the pull request
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/1169
---
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
?
On Fri, Apr 1, 2016 at 11:29 PM, William Grim wrote:
> Hi,
>
> I read the reasoning about using offsets.retention.minutes at
> https://mail-archives.apache.org/mod_mbox/kafka-users/201602.mbox/%3ccaaofhrah8p_a1yebfnh4wzsjwgiqpob_pr6hn4nymtluqqb...@mail.gmail.com%3E,
> but can we agree that the
[
https://issues.apache.org/jira/browse/KAFKA-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223099#comment-15223099
]
Bill Bejeck commented on KAFKA-3338:
Guozhang,
Thanks for the response, that all make
Hello Jun,
On Fri, Apr 1, 2016 at 9:57 PM, Jun Rao wrote:
> Ashish,
>
> Thanks for the KIP.
>
> It seems that a specific implementation of Authorizer can reject invalid
> user type in addAcl/removeAcl without needing the new
> getSupportedPrincipalTypes()
> method, right? It's probably useful t
[
https://issues.apache.org/jira/browse/KAFKA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222995#comment-15222995
]
Stig Rohde Døssing commented on KAFKA-725:
--
Nevermind this, I misunderstood the hi
Hello Ismael,
On Fri, Apr 1, 2016 at 4:08 PM, Ismael Juma wrote:
> Hi Ashish,
>
> A few comments on the proposal:
>
> 1. In Kafka, we don't use use getter convention generally. However, the
> other methods in the `Authorizer` interface do follow the getter
> convention, which is unfortunate. So,
[
https://issues.apache.org/jira/browse/KAFKA-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222925#comment-15222925
]
ASF GitHub Bot commented on KAFKA-3496:
---
GitHub user fhussonnois opened a pull reque
GitHub user fhussonnois opened a pull request:
https://github.com/apache/kafka/pull/1179
KAFKA-3496 - add policies for client reconnect attempts
In addition, this PR fixes some log level as describe in this issue :
https://issues.apache.org/jira/browse/KAFKA-2998
This imple
[
https://issues.apache.org/jira/browse/KAFKA-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florian Hussonnois updated KAFKA-3496:
--
Summary: Add reconnect attemps policies for client (was: Add policies to
reconnection)
Florian Hussonnois created KAFKA-3496:
-
Summary: Add policies to reconnection
Key: KAFKA-3496
URL: https://issues.apache.org/jira/browse/KAFKA-3496
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222909#comment-15222909
]
ASF GitHub Bot commented on KAFKA-725:
--
GitHub user srdo opened a pull request:
h
GitHub user srdo opened a pull request:
https://github.com/apache/kafka/pull/1178
KAFKA-725: Change behavior of Log/LogSegment when attempting read on an
offset that's above high watermark.
This should make Log.read act the same when startOffset is larger than
maxOffset as it would
[
https://issues.apache.org/jira/browse/KAFKA-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222826#comment-15222826
]
ASF GitHub Bot commented on KAFKA-3495:
---
GitHub user ijuma opened a pull request:
[
https://issues.apache.org/jira/browse/KAFKA-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3495:
---
Status: Patch Available (was: Open)
> `NetworkClient.blockingSendAndReceive` should rely on requestTi
GitHub user ijuma opened a pull request:
https://github.com/apache/kafka/pull/1177
KAFKA-3495; `NetworkClient.blockingSendAndReceive` should rely on
requestTimeout
Also removed the code for handling negative timeouts in `blockingReady` as
`Selector.poll` has not supported that for
Ismael Juma created KAFKA-3495:
--
Summary: `NetworkClient.blockingSendAndReceive` should rely on
requestTimeout
Key: KAFKA-3495
URL: https://issues.apache.org/jira/browse/KAFKA-3495
Project: Kafka
Onur Karaman created KAFKA-3494:
---
Summary: mbeans overwritten with identical clients on a single jvm
Key: KAFKA-3494
URL: https://issues.apache.org/jira/browse/KAFKA-3494
Project: Kafka
Issue T
Sorry for jumping over some feedback, but not sure the best way to provide
this feedback. Somewhat indirectly targeting feedback from Jay:
> "I actually do think good is the enemy of perfect (not sure if that makes
sense but I think you get what I mean)."
Yes I get it, but I don't agree (so surpr
20 matches
Mail list logo