We are currently in the process of updating our project(Spring MVC application) which was based on Lucene 2.8, to ElasticSearch so basically the bottleneck of storing indexes will pass to ElasticSearch.
The application now will only call ElasticSearch Server for CRUD operations on indexes, will not carry dependencies and responsibilities for managing Lucene Documents, IndexWriter... basically just Json and will also show the results from search queries.
My question is: Will we need(or gain advantage) by using the Java API ElasticSearch offers instead of the Rest API because as far as I understand(ElasticSearch noob here) Java API will only add more code(and maven dependencies) in the application instead of just performing the REST calls since everything will be json now.