Skip to content

SPARKC-706: Add basic support for Cassandra vectors #202

SPARKC-706: Add basic support for Cassandra vectors

SPARKC-706: Add basic support for Cassandra vectors #202

Triggered via pull request May 13, 2024 10:51
Status Failure
Total duration 26m 6s
Artifacts

main.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 20 warnings
CassandraRDDSpec.(It is not a test it is a sbt.testing.SuiteSelector): connector/src/it/scala/com/datastax/spark/connector/rdd/CassandraRDDSpec.scala#L282
com.datastax.oss.driver.api.core.AllNodesFailedException: All 1 node(s) tried for the query failed (showing first 1 nodes, use getAllErrors() for more): Node(endPoint=localhost/127.0.0.1:9042, hostId=4c56499a-300d-4b00-8fb4-5adb756b977a, hashCode=1a3eccdd): [com.datastax.oss.driver.api.core.NodeUnavailableException: No connection was available to Node(endPoint=localhost/127.0.0.1:9042, hostId=4c56499a-300d-4b00-8fb4-5adb756b977a, hashCode=1a3eccdd)]
build (2.13.13, 4.1.4)
Process completed with exit code 1.
build (2.13.13, 5.0-beta1)
Process completed with exit code 1.
DoubleVectorTypeTest.SCC should read rows with DOUBLE vectors using SQL API: connector/target/scala-2.13/it-classes/com/datastax/spark/connector/rdd/typeTests/DoubleVectorTypeTest.class#L1
org.apache.spark.sql.AnalysisException: [REQUIRES_SINGLE_PART_NAMESPACE] spark_catalog requires a single-part namespace, but got `casscatalog`.`test_double_vector_type_test`.
FloatVectorTypeTest.SCC should read rows with FLOAT vectors using SQL API: connector/target/scala-2.13/it-classes/com/datastax/spark/connector/rdd/typeTests/FloatVectorTypeTest.class#L1
org.apache.spark.sql.AnalysisException: [REQUIRES_SINGLE_PART_NAMESPACE] spark_catalog requires a single-part namespace, but got `casscatalog`.`test_float_vector_type_test`.
IntVectorTypeTest.SCC should read rows with INT vectors using SQL API: connector/target/scala-2.13/it-classes/com/datastax/spark/connector/rdd/typeTests/IntVectorTypeTest.class#L1
org.apache.spark.sql.AnalysisException: [REQUIRES_SINGLE_PART_NAMESPACE] spark_catalog requires a single-part namespace, but got `casscatalog`.`test_int_vector_type_test`.
LongVectorTypeTest.SCC should read rows with BIGINT vectors using SQL API: connector/target/scala-2.13/it-classes/com/datastax/spark/connector/rdd/typeTests/LongVectorTypeTest.class#L1
org.apache.spark.sql.AnalysisException: [REQUIRES_SINGLE_PART_NAMESPACE] spark_catalog requires a single-part namespace, but got `casscatalog`.`test_long_vector_type_test`.
DoubleVectorTypeTest.SCC should read rows with DOUBLE vectors using SQL API: connector/target/scala-2.12/it-classes/com/datastax/spark/connector/rdd/typeTests/DoubleVectorTypeTest.class#L1
org.apache.spark.sql.AnalysisException: [REQUIRES_SINGLE_PART_NAMESPACE] spark_catalog requires a single-part namespace, but got `casscatalog`.`test_double_vector_type_test`.
FloatVectorTypeTest.SCC should read rows with FLOAT vectors using SQL API: connector/target/scala-2.12/it-classes/com/datastax/spark/connector/rdd/typeTests/FloatVectorTypeTest.class#L1
org.apache.spark.sql.AnalysisException: [REQUIRES_SINGLE_PART_NAMESPACE] spark_catalog requires a single-part namespace, but got `casscatalog`.`test_float_vector_type_test`.
IntVectorTypeTest.SCC should read rows with INT vectors using SQL API: connector/target/scala-2.12/it-classes/com/datastax/spark/connector/rdd/typeTests/IntVectorTypeTest.class#L1
org.apache.spark.sql.AnalysisException: [REQUIRES_SINGLE_PART_NAMESPACE] spark_catalog requires a single-part namespace, but got `casscatalog`.`test_int_vector_type_test`.
LongVectorTypeTest.SCC should read rows with BIGINT vectors using SQL API: connector/target/scala-2.12/it-classes/com/datastax/spark/connector/rdd/typeTests/LongVectorTypeTest.class#L1
org.apache.spark.sql.AnalysisException: [REQUIRES_SINGLE_PART_NAMESPACE] spark_catalog requires a single-part namespace, but got `casscatalog`.`test_long_vector_type_test`.
build (2.12.19, 5.0-beta1)
Process completed with exit code 1.
build (2.12.19, 3.11.17)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: BSFishy/pip-action@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build (2.12.19, 3.11.17)
The following actions uses node12 which is deprecated and will be forced to run on node16: BSFishy/pip-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (2.13.13, 3.11.17)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: BSFishy/pip-action@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build (2.13.13, 3.11.17)
The following actions uses node12 which is deprecated and will be forced to run on node16: BSFishy/pip-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (2.13.13, 4.1.4)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: BSFishy/pip-action@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build (2.13.13, 4.1.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: BSFishy/pip-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (2.12.19, 4.1.4)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: BSFishy/pip-action@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build (2.12.19, 4.1.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: BSFishy/pip-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (2.13.13, 4.0.12)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: BSFishy/pip-action@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build (2.13.13, 4.0.12)
The following actions uses node12 which is deprecated and will be forced to run on node16: BSFishy/pip-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (2.12.19, 4.0.12)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: BSFishy/pip-action@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build (2.12.19, 4.0.12)
The following actions uses node12 which is deprecated and will be forced to run on node16: BSFishy/pip-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (2.13.13, 5.0-beta1)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: BSFishy/pip-action@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build (2.13.13, 5.0-beta1)
The following actions uses node12 which is deprecated and will be forced to run on node16: BSFishy/pip-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (2.12.19, 5.0-beta1)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: BSFishy/pip-action@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build (2.12.19, 5.0-beta1)
The following actions uses node12 which is deprecated and will be forced to run on node16: BSFishy/pip-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (2.13.13, dse-6.8.44)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: BSFishy/pip-action@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build (2.13.13, dse-6.8.44)
The following actions uses node12 which is deprecated and will be forced to run on node16: BSFishy/pip-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (2.12.19, dse-6.8.44)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: BSFishy/pip-action@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build (2.12.19, dse-6.8.44)
The following actions uses node12 which is deprecated and will be forced to run on node16: BSFishy/pip-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/