https://community.databricks.com/t5/data-engineering/maven-library-conflicts/m-p/18202#M12036 <P>The import statements work fine with maven libraries freshly installed on a running cluster and on restart of the same cluster, it fails to import the classes.</P> Fri, 25 Jun 2021 22:43:53 GMT brickster_2018 2021-06-25T22:43:53Z https://community.databricks.com/t5/data-engineering/maven-library-conflicts/m-p/18202#M12036 <P>The import statements work fine with maven libraries freshly installed on a running cluster and on restart of the same cluster, it fails to import the classes.</P> Fri, 25 Jun 2021 22:43:53 GMT https://community.databricks.com/t5/data-engineering/maven-library-conflicts/m-p/18202#M12036 brickster_2018 2021-06-25T22:43:53Z https://community.databricks.com/t5/data-engineering/maven-library-conflicts/m-p/18203#M12037 <P>When you install maven libraries one by one in running clusters, it is resolved and gets downloaded individually. The behavior would be different when you restart the clusters since the libraries are resolved together and can run into issues due to conflicting library dependencies. If you click on the respective library which has classes for import statement failed, you are likely to see an eviction message caused by the conflicting library.</P> Fri, 25 Jun 2021 22:44:40 GMT https://community.databricks.com/t5/data-engineering/maven-library-conflicts/m-p/18203#M12037 brickster_2018 2021-06-25T22:44:40Z