[ 
https://issues.apache.org/jira/browse/HUDI-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kudinkin updated HUDI-2669:
----------------------------------
    Description: 
We should upgrade to at least JDK11, or preferably current latest LTS JDK17

 

Plan for migration:

*Compilation*

JDK8 will still be used to *compile* source code (both source/target will stay 
`1.8`): this is required to make sure as we migrate to JDK11, we don't add 
dependencies on features not compatible w/ JDK8. Migrating off JDK8 in toolset, 
will happen at a later point, when we would stop providing any assurances about 
the code being able to be run on 1.8.

*Runtime*

JDK11 will be used to *run* the code: due to JVM b/w compatibility there should 
be no issues of running the code compiled for 1.8 on JDK11+, other than 
dependencies compatibility. For that we would make sure that all our 
test-suites do run against JDK11+.

 

 

 

  was:
We should upgrade to at least JDK11, or preferably current latest LTS JDK17

 

 

 


> Upgrade Java version to JDK11
> -----------------------------
>
>                 Key: HUDI-2669
>                 URL: https://issues.apache.org/jira/browse/HUDI-2669
>             Project: Apache Hudi
>          Issue Type: Sub-task
>          Components: Code Cleanup
>            Reporter: sivabalan narayanan
>            Assignee: Alexey Kudinkin
>            Priority: Blocker
>              Labels: performance
>             Fix For: 0.11.0
>
>
> We should upgrade to at least JDK11, or preferably current latest LTS JDK17
>  
> Plan for migration:
> *Compilation*
> JDK8 will still be used to *compile* source code (both source/target will 
> stay `1.8`): this is required to make sure as we migrate to JDK11, we don't 
> add dependencies on features not compatible w/ JDK8. Migrating off JDK8 in 
> toolset, will happen at a later point, when we would stop providing any 
> assurances about the code being able to be run on 1.8.
> *Runtime*
> JDK11 will be used to *run* the code: due to JVM b/w compatibility there 
> should be no issues of running the code compiled for 1.8 on JDK11+, other 
> than dependencies compatibility. For that we would make sure that all our 
> test-suites do run against JDK11+.
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to