-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Geni not usable wit latest Databricks #356
Comments
This issue makes it impossible to use geni with databricks. |
I digged into it.
is the "right thing" to do "in general", as there might always be Spark environments which do not support some of them. Docu says:Gets an existing SparkSession or, if there is no existing one, creates a new one based on the options set in this builder.
|
on my fork I made a change which fixes this: |
Hi Carsten @behrica, would you like to make a PR, and then I'm happy to merge it. Let me know if we need to change the CI workflows as well. |
As mentioned here
#332
I have an issue with geni on databricks.
Apparently this call
geni/src/clojure/zero_one/geni/spark.clj
Line 37 in e6eaeb9
which is execute even when using an existing spark session / context,
fails on databricks:
IllegalArgumentException: Path must be absolute: target/checkpoint/3f38a4a8-51e9-47fc-a1d1-7c0f3e2f2520 at com.databricks.common.path.AbstractPath$.fromHadoopPath(AbstractPath.scala:114) at com.databricks.backend.daemon.data.client.DBFSV2.resolveAndGetFileSystem(DatabricksFileSystemV2.scala:148) at com.databricks.backend.daemon.data.client.DatabricksFileSystemV2.resolve(DatabricksFileSystemV2.scala:773) at com.databricks.backend.daemon.data.client.Databrick
If I understand the current code correctly, it cannot be avoided that this call is made, neither can the directory be changed.
My comments in #332 where based n the assumption that the code does wrongly "creates" an other session, but I think it's no true.
It does get the session from databrcks, but tries to set the checkpoint directory on the existing session/context, and this fails now. Maybe it did work with older databricks/spark versions.
The text was updated successfully, but these errors were encountered: