You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/10/15 06:25:00 UTC

[jira] [Commented] (KAFKA-4422) Drop support for Scala 2.10 (KIP-119)

    [ https://issues.apache.org/jira/browse/KAFKA-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951646#comment-16951646 ] 

ASF GitHub Bot commented on KAFKA-4422:
---------------------------------------

guozhangwang commented on pull request #7519: KAFKA-4422 / KAFKA-8700 / KAFKA-5566: Wait for state to transit to RUNNING upon start
URL: https://github.com/apache/kafka/pull/7519
 
 
   I looked into the logs of the above tickets, and I think for a couple fo them it is due to the fact that the threads takes time to restore, or just stabilize the rebalance since there are multi-threads. Adding the hook to wait for state to transit to RUNNING upon starting. 
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Drop support for Scala 2.10 (KIP-119)
> -------------------------------------
>
>                 Key: KAFKA-4422
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4422
>             Project: Kafka
>          Issue Type: Task
>            Reporter: Ismael Juma
>            Assignee: Ismael Juma
>            Priority: Major
>              Labels: kip
>             Fix For: 0.11.0.0
>
>
> Now that Scala 2.12 has been released, we should drop support for Scala 2.10  in the next major Kafka version so that we keep the number of supported versions at 2. Since we have to compile and run the tests on each supported version, there is a non-trivial cost from a development and testing perspective.
> The clients library is in Java and we recommend people use the Java clients instead of the Scala ones, so dropping support for Scala 2.10 should have a smaller impact than it would have had in the past. Scala 2.10 was released in January 2013 and support ended in March 2015. 
> Once we drop support for Scala 2.10, we can take advantage of APIs and compiler improvements introduced in Scala 2.11 (introduced in April 2014): http://scala-lang.org/news/2.11.0
> Link to KIP:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-119%3A+Drop+Support+for+Scala+2.10+in+Kafka+0.11



--
This message was sent by Atlassian Jira
(v8.3.4#803005)