Will jboss required any changes after upgrading HDP or CDH versions?

[#1]

Greetings,

We are using HDP 2.6.5 mainly for Storm, Kafka, Zookeeper, Spark etc services. We have developed our application in Java and we are deploying our application using JBoss EAP. 

Now If I change HDP version 2.6.5 to CDH 6.3 or upgrade it to HDP 3.1.0, do I need to change anything in JBoss configuration or JBoss development perspective? Will there be any development changes from JBoss and Java side if all my code for storm and kafka is in Java. 

How JBoss application server will use HDP/CDH services?

[#2]

@girish_khole 

For example if you are currently using HDP 2.6.5 Kafka client libraries inside JBoss deployed application then you will find that the versions of kafka gets changes when you upgrade to HDP 3

For example:

1. In HDP 2.6.5 you will find the Kafka Version is "Apache Kafka 1.0.0"  (Apache Storm 1.1.0)
https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.5/bk_release-notes/content/comp_versions.html

2. But on the other hand in HDP 3.1 it is "Apache Kafka 2.0.0"  (Apache Storm 1.2.1)
https://docs.hortonworks.com/HDPDocuments/HDP3/HDP-3.1.0/release-notes/content/comp_versions.html

So based on the changes introduced in Kafka/storm versions you might need to change your application a bit to make use of the upgraded kafka version and to rebuild your JBoss deployed application to use the latest binaries/jars.

[#3]

@jsensharma  Thank you for your quick reply. It would be very helpful for me, that you can explain a bit changes means only POM dependency entry changes or actual code related changes? Do I need to rewrite any function?

[#4 · Accepted solution]

@girish_khole 

It will be highly impossible to tell exactly what all changes are needed in your application when Kafka version changes from 1.0 to 2.0 (similarly Storm version changes from 1.1.0 to 1.2.0). As we do not know which kind of APIs your application is using.

Kafka version changes are from 1.0 to 2.0 which is kind of version upgrade and with any such version upgrade it is possible that there may be few methods removed which were declared as deprecated earlier... or some methods signatures might have changes.. Similarly some new classes and methods are introduced.

So better to go step by step try upgrading the pom.xml dependencies inside your JBoss deployed application and then check if it works ... if you see any NoSuchMethodError/ ClasssNotFountError/ ..etc then accordingly you will need to fix it by referring to the new APIs available as part of the upgraded components.

If your question is answered then, Please make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.

[#5]

Thank you very much for your inputs.