https://lakefs.io/ logo
Join SlackCommunities
Powered by
Asked by <@U01N6DK55JL> (Thanks Ori!) We have som...
# help
i
Asked by @Ori Adijes (Thanks Ori!) We have some issue which I hope you will be able to help: We have a pom.xml file which uses both 
hadoop-lakefs
 and 
io.lakefs.api-client
 version 0.44.0 Unfortunately, The internal 
hadoop-lakefs
 library is using 
io.lakefs.api-client
 version 0.40.3 which cause collision and errors like:
Copy code
16:09:36 Caused by: java.lang.NoSuchMethodError: io.lakefs.clients.api.ObjectsApi.listObjects(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/Integer;Ljava/lang/String;)Lio/lakefs/clients/api/model/ObjectStatsList;
Do you have an idea of how we can solve it? I saw that the latest haddop-lakefs lib still using 0.40.3 The reason we’ve upgraded to 0.44.0 is to use the diff prefix feature introduced after the 0.40.3 version
🙏 1
We’ll need to upgrade the 
hadoop-lakefs
 to work with the latest api client. I’m working on fixing and releasing it now. Unfortunately, the swagger generator for Java creates a new function call with every new (even optional) param added to the api. It means you may need to go over your code using the client and add or shift places for some of the params to the function calls. It doesn’t mean that the lakeFS api isn’t backward compatible, it is and it will continue to serve the same functionality as before.
o
Thanks! But keep in mind our deployed lakefs api server is in version 0.45. Will we be able to use it with the latest api-client which is > 0.45?
y
Yes, our clients are backward-compatible with respect to the server.
That is, if you keep using the same 0.45 features with a newer client, it will work
🔥 2
i
Hey again, we released the 
hadoop-lakefs
version 0.1.4 with the 
api-client
version 
0.56.0
. It’s available as a maven dependency so feel free to use it and let us know if it solved your problem (may not be visible in the maven portal since it takes some time for it to update).
🙏 1
👍🏻 1
o
Thanks @Itai Admi!!! It worked
🙂 1
Open in Slack
PreviousNext
Powered by