Edouard_JH
New Contributor III

@pavansharma36 Thanks for the details.

I had a look on runtime and platform release notes and I can't find nothing that could explain a change of behavior. I can only suppose that background changes happened but guessing is not fact.

It's only an opinion but :

  • jars can be heavy files so throwing an error when trying to load a library more than once is helpful
  • default libraries is a good concept but in this specific libraries should not collide with default ones

It would be great if we could have a release note with package management changes because with the progressive removal of DBFS, changes will continue to occur.

View solution in original post