-
Notifications
You must be signed in to change notification settings - Fork 115
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
Fix how resolvers are handled during driver construction #626
Conversation
@@ -15,21 +15,24 @@ import java.util.concurrent.TimeUnit | |||
import scala.collection.JavaConverters._ | |||
import scala.language.implicitConversions | |||
import org.apache.spark.internal.Logging | |||
import org.jetbrains.annotations.TestOnly |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this addition is probably not intentional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually added it two public functions on this class, as they were already commented as being public for test access.
@Test | ||
def shouldConstructDriverWithResolver(): Unit = { | ||
val options: java.util.Map[String, String] = new java.util.HashMap[String, String]() | ||
options.put(Neo4jOptions.URL, s"neo4j://localhost.localdomain:8888, bolt://localhost.localdomain:9999, ${server.getBoltUrl}") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wait, how does this work?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, I was just mapping localhost.localdomain:8888
to a set of localhost.localdomain:9999
(which is not accessible) and localhost:XYZ
(which should be accessible) - and I expect the driver to establish a connection successfully.
Bu we need a response from drivers team for this - I believe there is a bug around this in the driver.
waiting for a driver fix for this one. |
This PR fixes how multiple URLs are handled when passed to
url
option during driver creation.