The location of the policies is fine. Note that the package _does not_
include clients in the name. If we ever have enough server side only code
to merit a separate JAR, we can do that and it's mostly compatible (users
would only have to update their build dependency). Generally, all public
APIs go
Thanks!
Ismael
On Mon, Nov 6, 2017 at 3:48 AM, Ted Yu wrote:
> Logged https://issues.apache.org/jira/browse/INFRA-15448
>
> On Thu, Nov 2, 2017 at 11:39 PM, Ismael Juma wrote:
>
> > This looks to be an issue in Jenkins, not in Kafka. Apache Infra updated
> > Java 9
Congratulations Onur!
Ismael
On Mon, Nov 6, 2017 at 5:24 PM, Jun Rao wrote:
> Hi, everyone,
>
> The PMC of Apache Kafka is pleased to announce a new Kafka committer Onur
> Karaman.
>
> Onur's most significant work is the improvement of Kafka controller, which
> is the brain of a Kafka cluster.
Thanks for the KIP. It would be good to elaborate a little more on why the
binary representation is not suitable. The difference between 16 and 36
bytes is significant.
Ismael
On Mon, Nov 6, 2017 at 9:53 AM, Jakub Scholz wrote:
> Hi all,
>
> Just a friendly reminder that this is still up for vo
This looks to be an issue in Jenkins, not in Kafka. Apache Infra updated
Java 9 to 9.0.1 and it seems to have broken some of the Jenkins code.
Ismael
On 3 Nov 2017 1:53 am, "Ted Yu" wrote:
> Looking at earlier runs, e.g. :
> https://builds.apache.org/job/kafka-pr-jdk9-scala2.12/2384/console
>
>
Afzali, Hao Chen, Jiefang He, Holden
Karau, Hooman Broujerdi, Hugo Louro, Ismael Juma, Jacek Laskowski, Jakub
Scholz, James Cheng, James Chien, Jan Burkhardt, Jason Gustafson, Jeff
Chao, Jeff Klukas, Jeff Widman, Jeremy Custenborder, Jeyhun Karimov,
Jiangjie Qin, Joel Dice, Joel Hamill, Jorge Quilcat
On Wed, Nov 1, 2017 at 3:51 PM, Ted Yu wrote:
> bq. Wait for a kafka release which will not support java 7 anymore
>
> Do you want to raise a separate thread for the above ?
>
There is already a KIP for this so a separate thread is not needed.
Ismael
[
https://issues.apache.org/jira/browse/KAFKA-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-1506.
Resolution: Duplicate
Marking as a duplicate of KAFKA-1676 as the latter contains more information
+1 (binding) from me. Tested the quickstart with the source and binary
(Scala 2.12) artifacts, ran the tests on the source artifact and verified
some signatures and hashes on source and binary (Scala 2.11) artifacts.
Thanks for running the release, Guozhang!
Ismael
On Fri, Oct 27, 2017 at 6:28 P
Thanks for the KIP, +1 (binding).
On 27 Oct 2017 6:15 pm, "Onur Karaman" wrote:
> I'd like to start the vote for KIP-214: Add
> zookeeper.max.in.flight.requests config to the broker
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-
> 214%3A+Add+zookeeper.max.in.flight.requests+config+to
[
https://issues.apache.org/jira/browse/KAFKA-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reopened KAFKA-3917:
If you're running 0.10.2.0, then potentially KAFKA-5413, but I'll reopen until
we can verif
[
https://issues.apache.org/jira/browse/KAFKA-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-2616.
Resolution: Auto Closed
BlockingChannel is only used by the Scala clients. which are no longer
[
https://issues.apache.org/jira/browse/KAFKA-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-2636.
Resolution: Not A Problem
The producer should throw a TimeoutException to the callback or if
[
https://issues.apache.org/jira/browse/KAFKA-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-2662.
Resolution: Auto Closed
The Scala consumers are no longer supported. Please upgrade to the Java
[
https://issues.apache.org/jira/browse/KAFKA-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-2725.
Resolution: Auto Closed
The Scala consumers are no longer supported. If this still applies to the
[
https://issues.apache.org/jira/browse/KAFKA-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-3071.
Resolution: Auto Closed
The SimpleConsumer is no longer supported and will be removed in a future
[
https://issues.apache.org/jira/browse/KAFKA-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-3860.
Resolution: Auto Closed
The old consumer is no longer supported, please upgrade to the Java
[
https://issues.apache.org/jira/browse/KAFKA-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-3756.
Resolution: Auto Closed
Closing as 0.8.2 branch is no longer supported.
> javadoc has issues w
[
https://issues.apache.org/jira/browse/KAFKA-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-3917.
Resolution: Duplicate
This log cleaner issue has been fixed in more recent versions. I suggest
[
https://issues.apache.org/jira/browse/KAFKA-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-4096.
Resolution: Auto Closed
Thanks for the JIRA. This should work. If you are still seeing this with a
[
https://issues.apache.org/jira/browse/KAFKA-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-4832.
Resolution: Auto Closed
The Scala producers have been deprecated for a while and no further work is
[
https://issues.apache.org/jira/browse/KAFKA-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5963.
Resolution: Auto Closed
Thanks for the JIRA. Kafka 0.8.x is no longer supported and the issue has
[
https://issues.apache.org/jira/browse/KAFKA-5981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5981.
Resolution: Duplicate
Updated the fix versions. Only included the ones that are still supported
[
https://issues.apache.org/jira/browse/KAFKA-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-6043.
Resolution: Auto Closed
The old consumer is deprecated and no further changes are planned. Please
[
https://issues.apache.org/jira/browse/KAFKA-6117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-6117.
Resolution: Auto Closed
Thanks for the JIRA. 0.8.2.x is unsupported at this point. Newer releases
[
https://issues.apache.org/jira/browse/KAFKA-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5934.
Resolution: Won't Fix
Thanks for the JIRA and PR. 0.8.x is unsupported at this point and we
[
https://issues.apache.org/jira/browse/KAFKA-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-2156.
Resolution: Auto Closed
It's unlikely that we will do this for Yammer Metrics. Please f
[
https://issues.apache.org/jira/browse/KAFKA-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-2180.
Resolution: Auto Closed
Not enough information and very old so auto closing.
> topics never cre
[
https://issues.apache.org/jira/browse/KAFKA-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-.
Resolution: Won't Fix
The code changed dramatically since this was filed (the stacktrace do
[
https://issues.apache.org/jira/browse/KAFKA-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-6064.
Resolution: Auto Closed
0.8.2.1 is no longer supported. Many bugs related to topic deletion have
Yes, I think it would be good to eliminate these lines from the output. A
PR is welcome if you're interested.
Ismael
On Fri, Oct 27, 2017 at 5:03 PM, Pavel Drankov wrote:
> Of course it don't fail tests. I mean to fix log appearance.
>
> Best wishes,
> Pavel
>
> On 27 October 2017 at 18:48, Ted
Seems sensible to me.
Ismael
On Thu, Oct 26, 2017 at 6:37 AM, Onur Karaman
wrote:
> Hey everyone.
>
> Giving this another shot since it looks like there was a KIP number
> collision on the wiki page.
>
> I made a config kip, KIP-214: Add zookeeper.max.in.flight.requests config
> to the broker:
Ismael Juma created KAFKA-6136:
--
Summary: Transient test failure:
SaslPlainSslEndToEndAuthorizationTest.testTwoConsumersWithDifferentSaslCredentials
Key: KAFKA-6136
URL: https://issues.apache.org/jira/browse/KAFKA
[
https://issues.apache.org/jira/browse/KAFKA-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-6131.
Resolution: Fixed
Fix Version/s: 1.1.0
0.11.0.2
1.0.0
[
https://issues.apache.org/jira/browse/KAFKA-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-6128.
Resolution: Not A Problem
> Shutdown script does not do a clean shutd
[
https://issues.apache.org/jira/browse/KAFKA-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reopened KAFKA-6128:
> Shutdown script does not do a clean shutd
[
https://issues.apache.org/jira/browse/KAFKA-6116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-6116.
Resolution: Fixed
Fixed in 0.11.0, 1.0 and trunk. Commit for 0.11.0:
https://github.com/apache
Ismael Juma created KAFKA-6116:
--
Summary: Major performance issue due to excessive logging during
leader election
Key: KAFKA-6116
URL: https://issues.apache.org/jira/browse/KAFKA-6116
Project: Kafka
Ismael Juma created KAFKA-6111:
--
Summary: Tests for KafkaControllerZkUtils
Key: KAFKA-6111
URL: https://issues.apache.org/jira/browse/KAFKA-6111
Project: Kafka
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/KAFKA-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-6070.
Resolution: Fixed
Fix Version/s: 1.1.0
1.0.0
> ducker-ak: add ipaddr
[
https://issues.apache.org/jira/browse/KAFKA-5720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5720.
Resolution: Fixed
Fix Version/s: (was: 1.1.0)
1.0.0
> In Jenk
[
https://issues.apache.org/jira/browse/KAFKA-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5743.
Resolution: Fixed
Fix Version/s: 1.0.0
> All ducktape services should store their files
[
https://issues.apache.org/jira/browse/KAFKA-6101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-6101.
Resolution: Fixed
Assignee: Ted Yu
> Reconnecting to broker does not exponentially back
[
https://issues.apache.org/jira/browse/KAFKA-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-6088.
Resolution: Fixed
Since it was fixed in 0.11.0.0, marking it as fixed.
> Kafka Consumer slows d
[
https://issues.apache.org/jira/browse/KAFKA-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reopened KAFKA-6088:
> Kafka Consumer slows down when reading from highly compacted top
Also, only part 1 of KIP-113 landed. The release planning page has the
correct info for what it's worth.
Ismael
On 18 Oct 2017 5:42 pm, "Jun Rao" wrote:
> Hi, Guozhang,
>
> Thanks for running the release. Just a quick clarification. The statement
> that "* Controller improvements: async ZK acce
ed.
>
> How about we use deleteRecords(Map
> partitionsAndOffsets) for now, and add deleteRecords(Map DeleteRecordsParameter> partitionsAndOffsets) when we need to support core
> parameter in the future? By doing this we can make user's experience better
> (i.e. not having to i
Hi Dong,
I think it makes sense to use the parameters to define the specifics of the
request. However, we would probably want to replace the `Long` with a class
(similar to `createPartitions`) instead of relying on
`DeleteRecordsOptions`. The latter is typically used for defining
additional option
Thanks for the KIP, +1 (binding). A few comments:
1. I agree with Jun about LEADER_NOT_AVAILABLE for the error code for older
versions.
2. OffsetNotAvailableException seems clear enough (i.e. we don't need the
"ForPartition" part)
3. The KIP seems to be missing the compatibility section.
4. It wou
If you don't use the default Scala version, you have to set the
SCALA_VERSION environment variable for the bin scripts to work.
Ismael
On 17 Oct 2017 1:30 am, "Vahid S Hashemian"
wrote:
Hi Guozhang,
I'm not sure if this should be covered by "Java 9 support" in the RC note,
but when I try to bu
The only public classes are the ones in the javadoc. SecurityProtocol was
not public, but it now is.
Ismael
On 13 Oct 2017 12:16 am, "Ted Yu" wrote:
> Thanks for the explanation.
>
> SecurityProtocol was declared public in previous releases, hence I didn't
> notice that it is internal.
>
> On T
See inline.
On Thu, Oct 12, 2017 at 6:43 AM, Vahid S Hashemian <
vahidhashem...@us.ibm.com> wrote:
>
>
> [2017-10-11 21:45:11,642] FATAL (kafka.Kafka$)
> java.lang.IllegalArgumentException: Unknown signal: HUP
> at sun.misc.Signal.(Unknown Source)
> at kafka.Kafka$.registerHandler
[
https://issues.apache.org/jira/browse/KAFKA-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-6053.
Resolution: Fixed
Fix Version/s: 1.1.0
1.0.0
> NoSuchMethodError w
Ismael Juma created KAFKA-6027:
--
Summary: System test failure: LogDirFailureTest
Key: KAFKA-6027
URL: https://issues.apache.org/jira/browse/KAFKA-6027
Project: Kafka
Issue Type: Bug
You can update your properties file in the same way with the current
clients, right? I don't understand how mapping properties into a single
string makes things easier.
Ismael
On Thu, Oct 5, 2017 at 11:22 PM, Clebert Suconic
wrote:
> Another useful feature for this...
>
> Say that I am writing
Ismael Juma created KAFKA-6012:
--
Summary: NoSuchElementException in markErrorMeter during
TransactionsBounceTest
Key: KAFKA-6012
URL: https://issues.apache.org/jira/browse/KAFKA-6012
Project: Kafka
Ismael Juma created KAFKA-6010:
--
Summary: Transient failure:
MemoryRecordsBuilderTest.convertToV1WithMixedV0AndV2Data
Key: KAFKA-6010
URL: https://issues.apache.org/jira/browse/KAFKA-6010
Project: Kafka
eY&s=43hzTLEDKw2v5Vh0zwkMTaaKD-
> HdJD8d_F4-Bsw25-Y&e=
> > >
> > > Linkedin : paolopatierno<
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__it.
> > linkedin.com_in_paolopatierno&d=DwIBaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=
> > EzRhmSah4IHsUZVekRUIINhltZK7U0OaeRo7h
[
https://issues.apache.org/jira/browse/KAFKA-4946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-4946.
Resolution: Duplicate
Marking as duplicate of KAFKA-5843 as that had a PR. Credited Ralph as well
Hi Haseeb,
That is the point, the server should always send a response with the same
correlation id as the request it has received. If there's a bug in the
networking layer where a response is never sent back or there is reordering
somewhere in the stack, then this will be identified by the client
[
https://issues.apache.org/jira/browse/KAFKA-5968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5968.
Resolution: Fixed
Fix Version/s: (was: 1.1.0)
1.0.0
> Remove
[
https://issues.apache.org/jira/browse/KAFKA-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5992.
Resolution: Duplicate
Duplicate of KAFKA-5445.
> Better Java Documentation for AdminCli
[
https://issues.apache.org/jira/browse/KAFKA-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-3986.
Resolution: Fixed
Fix Version/s: (was: 1.1.0)
1.0.0
[
https://issues.apache.org/jira/browse/KAFKA-5976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5976.
Resolution: Fixed
Fix Version/s: 1.0.0
> RequestChannel.sendReponse records incorrect s
p; IoT
> Microsoft Azure Advisor
>
> Twitter : @ppatierno<http://twitter.com/ppatierno>
> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno>
> Blog : DevExperience<http://paolopatierno.wordpress.com/>
>
>
>
&g
Another quick comment: the KIP states that having multiple interfaces imply
that the logic must be in 2 places. That is not true because the same class
can implement multiple interfaces (this aspect was considered when we
decided to introduce policies incrementally).
The main reason why I think th
really the same as deleting a
topic. The latter will cause consumers and producers to error out while the
former will not. It would be good to motivate the need for the delete
records policy more.
Ismael
On Wed, Sep 27, 2017 at 11:12 AM, Ismael Juma wrote:
> Another quick comment: the K
If we are introducing another interface, I think it makes sense to
complement the request metadata with a context class that exposes
non-request information that may be useful. I'll hopefully review the KIP
in more detail today or tomorrow.
Ismael
On Tue, Sep 26, 2017 at 2:01 PM, Edoardo Comar w
Hi Paolo,
The delete records KIP was voted and implemented before the AdminClient
KIP. It couldn't use something that didn't exist. :)
Regarding which part to take, I would say it depends on the contributor.
Both moving the tool to `tools` and removing the ZK dependency are
valuable. If someone i
[
https://issues.apache.org/jira/browse/KAFKA-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5695.
Resolution: Fixed
Fix Version/s: (was: 1.1.0)
1.0.0
> T
Removals can only happen in major releases.
Ismael
On Tue, Sep 26, 2017 at 8:37 AM, Paolo Patierno wrote:
> Hi devs,
>
> I know that we are already voting for this (+1 bindings from Ismael Juma
> and Guozhang Wang, +1 non binding from Mickael Maison) but I'd like to ask
>
[
https://issues.apache.org/jira/browse/KAFKA-5960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5960.
Resolution: Fixed
> Producer uses unsupported ProduceRequest version against older brok
On Mon, Sep 25, 2017 at 5:32 PM, Tom Bentley wrote:
> > bq. If this KIP is accepted for Kafka 1.1.0 this removal could happen in
> > Kafka 3.0.0
> >
> > There would be no Kafka 2.0 ?
> >
>
> As I understand it, a deprecation has to exist for a complete major version
> number cycle before the feat
Thanks for the KIP, +1 (binding).
On 19 Sep 2017 12:27 am, "Richard Yu" wrote:
> Hello, I would like to start a VOTE thread on KIP-202.
>
> Thanks.
>
[
https://issues.apache.org/jira/browse/KAFKA-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5920.
Resolution: Fixed
> Handle SSL authentication failures as non-retriable exceptions in clie
Ismael Juma created KAFKA-5955:
--
Summary: Transient failure:
AuthorizerIntegrationTest.testTransactionalProducerTopicAuthorizationExceptionInCommit
Key: KAFKA-5955
URL: https://issues.apache.org/jira/browse/KAFKA
[
https://issues.apache.org/jira/browse/KAFKA-5947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5947.
Resolution: Fixed
> Handle authentication failures from transactional producer
p 21, 2017 at 7:46 AM, Ismael Juma wrote:
>
> > Yes, although it would have to be reviewed and merged by next Wednesday.
> >
> > Ismael
> >
> > On Thu, Sep 21, 2017 at 12:17 AM, James Cheng
> > wrote:
> >
> > > Thanks Ismael. Yes, you're rig
Ismael Juma created KAFKA-5950:
--
Summary: AdminClient should retry based on returned error codes
Key: KAFKA-5950
URL: https://issues.apache.org/jira/browse/KAFKA-5950
Project: Kafka
Issue Type
to help me prioritize when
> I should work on them.
>
> But to your general point, it sounds like if I make my case and the
> community agrees that its worth the cost/benefit, that it might be eligible
> to get into 1.0.0. Sounds perfect. Thanks!
>
> -James
>
> >
Hi James,
Isn't PR 3799 purely a code refactoring (i.e. no change in behaviour)? If
so, it would probably land in trunk only after today. If it's new
functionality, then it depends on size, risk and importance. If you think
it's important and should target 1.0.0, feel free to make your case in the
Hi Ted,
Thanks for following up with INFRA on the issues we've been seeing. I asked
a clarifying comment in that ticket (for some reason it only allowed me to
add an internal comment).
Ismael
On Wed, Sep 20, 2017 at 2:31 AM, Ted Yu wrote:
> Hi,
> See Gavin's comment:
>
> https://issues.apache.
reminder Ismael. I think after this Wednesday for
> KIP-related PRs we need to discuss case-by-case to estimate its impact on
> regression.
>
>
> Guozhang
>
> On Mon, Sep 18, 2017 at 5:56 PM, Ismael Juma wrote:
>
> > Hi Guozhang,
> >
> > Note that our docu
Hi Guozhang,
Note that our documentation for the time-based release plan says the
following about what happens after the feature freeze:
"We will leave another week for "minor" features to get in (see below for
definitions), but at this point we will start efforts to stabilize the
release branch
Ismael Juma created KAFKA-5915:
--
Summary: Support unmapping of mapped/direct buffers in Java 9
Key: KAFKA-5915
URL: https://issues.apache.org/jira/browse/KAFKA-5915
Project: Kafka
Issue Type
Ismael Juma created KAFKA-5907:
--
Summary: Support aggregatedJavadoc in Java 9
Key: KAFKA-5907
URL: https://issues.apache.org/jira/browse/KAFKA-5907
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5822.
Resolution: Fixed
Fix Version/s: 1.0.0
> Consistent logging of topic partiti
Thanks for the KIP. +1 (binding) from me.
Because this is a bug fix, the change is simple and the impact can be bad,
I suggest considering this for the 1.0.0 release. Guozhang's call though.
Ismael
On Thu, Sep 14, 2017 at 9:52 AM, Mickael Maison
wrote:
> Hi,
>
> I'd like to start the vote on K
Thanks for the KIP Mickael. I suggest starting a vote.
Ismael
On Mon, Aug 21, 2017 at 2:51 PM, Mickael Maison
wrote:
> Hi all,
>
> I have created a KIP to cleanup the way client-ids are handled by
> brokers and clients.
>
> Currently the Java clients have some restrictions on the client-ids
> t
Ismael Juma created KAFKA-5887:
--
Summary: Enable findBugs (or equivalent) when building with Java 9
Key: KAFKA-5887
URL: https://issues.apache.org/jira/browse/KAFKA-5887
Project: Kafka
Issue
Ismael Juma created KAFKA-5884:
--
Summary: Enable PowerMock tests when running on Java 9
Key: KAFKA-5884
URL: https://issues.apache.org/jira/browse/KAFKA-5884
Project: Kafka
Issue Type: Task
[
https://issues.apache.org/jira/browse/KAFKA-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5076.
Resolution: Fixed
Done as part of https://github.com/apache/kafka/pull/3647.
> Remove usage
Ismael Juma created KAFKA-5883:
--
Summary: Run tests on Java 9 with –illegal-access=deny
Key: KAFKA-5883
URL: https://issues.apache.org/jira/browse/KAFKA-5883
Project: Kafka
Issue Type: Task
Just a quick follow-up: we have renamed the files ending in .sha2 to end in
.sha512 instead as per Apache guidelines. This was requested by Henk P.
Penning.
Ismael
On Tue, Sep 12, 2017 at 1:54 PM, Damian Guy wrote:
> Thanks all the vote has now closed and the release has been accepted. I'll
> p
Tom,
Thanks for the KIP, +1 (binding) from me.
Ismael
On Fri, Sep 8, 2017 at 5:42 PM, Tom Bentley wrote:
> I would like to start the vote on KIP-195 which adds an AdminClient API for
> increasing the number of partitions of a topic. The details are here:
>
> https://cwiki.apache.org/confluence
Hi Tom,
OK, I suggest not calling any policy then. We can do a separate KIP for
overhauling topic policies so that they work with all operations for 1.1.0.
Regarding the loophole issue, keep in mind that the alter topics
authorization would still be required, so I don't think it's an issue.
Users
Hi Damian,
Thanks for managing the release. This may just be the first ever RC0 to be
promoted to final. :) +1 (binding) from me. I verified some
signatures/hashes, verified quickstart on binary Scala 2.12 artifact, ran
tests and broker quickstart on the source artifact.
Ismael
On Tue, Sep 5, 20
Thanks for the KIP, +1 (binding).
Ismael
On Fri, Sep 8, 2017 at 6:00 PM, Ted Yu wrote:
> Hi,
> Please take a look at:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-
> 197+Connect+REST+API+should+include+the+connector+type+
> when+describing+a+connector
>
> Thanks
>
ace that can be used by create, alter and delete with a new config.
And deprecate CreateTopicPolicy. I doubt many are using it. What do you
think?
Ismael
On Fri, Sep 8, 2017 at 5:34 PM, Ismael Juma wrote:
> Hi Tom,
>
> Maybe we should disallow the creation of partitions while a reassignme
[
https://issues.apache.org/jira/browse/KAFKA-5763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5763.
Resolution: Fixed
> Refactor NetworkClient to use LogCont
1101 - 1200 of 5488 matches
Mail list logo
