jiangxt2 opened a new issue, #13029: URL: https://github.com/apache/gravitino/issues/13029
Title: [Bug report] Lance Spark integration guide uses the wrong Catalog class name for the 0.4.0 bundle Version main branch Describe what's wrong The Lance Spark integration guide configures `spark.sql.catalog.lance` with `com.lancedb.lance.spark.LanceNamespaceSparkCatalog`, but the supported `org.lance:lance-spark-bundle-3.5_2.12:0.4.0` bundle provides `org.lance.spark.LanceNamespaceSparkCatalog` instead. Following the documented configuration therefore fails during Spark Catalog class loading before Spark contacts the Gravitino Lance REST endpoint. Error message and/or stacktrace ```text Cannot find catalog plugin class for catalog 'lance': com.lancedb.lance.spark.LanceNamespaceSparkCatalog. Caused by: java.lang.ClassNotFoundException: com.lancedb.lance.spark.LanceNamespaceSparkCatalog ``` How to reproduce 1. Use the Lance Spark integration example from `docs/lance-rest-integration.md`. 2. Use Spark 3.5 with `org.lance:lance-spark-bundle-3.5_2.12:0.4.0`. 3. Configure `spark.sql.catalog.lance` as `com.lancedb.lance.spark.LanceNamespaceSparkCatalog`. 4. Run any operation that resolves the catalog, such as `SHOW NAMESPACES IN lance`. The failure is reproducible before any network or storage interaction. Replacing the configured class with `org.lance.spark.LanceNamespaceSparkCatalog` allows the Catalog to load and the existing Lance Spark integration tests to proceed. Additional context The current `LanceSparkRESTServiceIT` already uses `org.lance.spark.LanceNamespaceSparkCatalog`, so the repository documentation and runtime test configuration disagree. The issue is limited to the integration example and does not indicate a Lance data-path or vector-computation failure. The documentation should use the class shipped by the supported bundle, and the compatibility matrix should guard against future documentation-to-bundle class-name drift. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
