Get this into Bintray and Maven Central #1
Assignees
Comments
|
It's in bintray as of yesterday. |
|
What is the current situation with Maven Central? |
|
v0.9.3 is in Maven Central but unfortunately I royally screwed up the v0.9.5, hopefully including your Oracle-XE and JDK7 PRs is what I'll try to On Fri, Jun 26, 2015 at 9:18 AM, gusohal notifications@github.com wrote:
|
beargiles
pushed a commit
to beargiles/testcontainers-java
that referenced
this issue
Dec 14, 2019
Many enterprise environments require a JDBC connection to Cassandra for integration into legacy systems. This patch changes the parent of the CassandraContainer to JdbcDatabaseContainer and optionally allows enables the 'native api' (thrift-over-rcp) used by many JDBC driver implementations. A new test was added - testCassandraJdbcQuery(). == Status This code isn't ready for merge - it's being offered for review. It loosely corresponds to my work on Friday creating a local fork that integrates into our existing environment where we were already using JDBC connections to Cassandra servers. That fork works so I know this fork is very close to working. Of particular note is the log line ``` INFO [main] 2019-12-14 21:31:33,520 ThriftServer.java:116 - Binding thrift service to /0.0.0.0:9160 ``` since that indicates that the server is listening to the RPC port required by the JDBC driver. == Remaining Work testcontainers#1 The connection attempt fails with ``` Caused by: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: localhost/127.0.0.1:32862 (com.datastax.driver.core.exceptions.TransportException: [localhost/127.0.0.1:32862] Channel has been closed)) at com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:268) at com.datastax.driver.core.ControlConnection.connect(ControlConnection.java:107) at com.datastax.driver.core.Cluster$Manager.negotiateProtocolVersionAndConnect(Cluster.java:1813) at com.datastax.driver.core.Cluster$Manager.init(Cluster.java:1726) at com.datastax.driver.core.Cluster.init(Cluster.java:214) at com.datastax.driver.core.Cluster.connectAsync(Cluster.java:387) at com.datastax.driver.core.Cluster.connect(Cluster.java:338) at com.github.adejanovski.cassandra.jdbc.SessionHolder.createSession(SessionHolder.java:201) ... 36 more ``` however I know that the same JDBC driver works elsewhere. It may be something as simple as a missing datastax jar. == Remaining Work testcontainers#2 The test includes calls to `cassandraContainer.setWaitStrategy()`. Neither seems to have any effect. In the other fork I only saw a wait strategy used was when I explicitly set the waitStrategy value in the constructor.
matriv
added a commit
to matriv/testcontainers-java
that referenced
this issue
Mar 29, 2023
eddumelendez
pushed a commit
that referenced
this issue
Oct 2, 2023
* Changed wait strategy for ysql testcontainer * Updating YugabyteDB-YSQL WaitStrategy * Catch IllegalStateException * Update test query * Changes as per review * Added a test case. * Updating YSQL wait strategy * Removing redundant if. * Minor Change * YugabyteDB version updates in tests
eddumelendez
pushed a commit
that referenced
this issue
Oct 2, 2023
* Changed wait strategy for ysql testcontainer * Updating YugabyteDB-YSQL WaitStrategy * Catch IllegalStateException * Update test query * Changes as per review * Added a test case. * Updating YSQL wait strategy * Removing redundant if. * Minor Change * YugabyteDB version updates in tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: