[#10283] web-v2(UI): remove default prop for clickhouse table (#10285)

### What changes were proposed in this pull request?
remove default prop for clickhouse table

### Why are the changes needed?
N/A

Fix: #10283

### Does this PR introduce _any_ user-facing change?
N/A

### How was this patch tested?
manually
1 file changed
tree: 2f85076476f4db7be071c78033f32c1fe6d5a28e
  1. .claude/
  2. .github/
  3. .idea/
  4. api/
  5. authorizations/
  6. bin/
  7. bundles/
  8. catalogs/
  9. catalogs-contrib/
  10. clients/
  11. common/
  12. conf/
  13. core/
  14. dev/
  15. docs/
  16. flink-connector/
  17. gradle/
  18. iceberg/
  19. integration-test-common/
  20. lance/
  21. licenses/
  22. lineage/
  23. maintenance/
  24. mcp-server/
  25. rfc/
  26. scripts/
  27. server/
  28. server-common/
  29. spark-connector/
  30. trino-connector/
  31. web/
  32. web-v2/
  33. .asf.yaml
  34. .gitattributes
  35. .gitignore
  36. AGENTS.md
  37. build.gradle.kts
  38. CODE_OF_CONDUCT.md
  39. CONTRIBUTING.md
  40. GETTING_STARTED.md
  41. GOVERNANCE.md
  42. gradle.properties
  43. gradlew
  44. LICENSE
  45. LICENSE.bin
  46. LICENSE.iceberg
  47. LICENSE.lance
  48. LICENSE.trino
  49. MAINTAINERS.md
  50. NOTICE
  51. NOTICE.bin
  52. NOTICE.iceberg
  53. NOTICE.lance
  54. NOTICE.trino
  55. README.md
  56. ROADMAP.md
  57. SECURITY.md
  58. settings.gradle.kts
README.md

Apache Gravitino™

GitHub Actions Build GitHub Actions Integration Test License Contributors Release Open Issues Last Committed OpenSSF Best Practices

Introduction

Apache Gravitino is a high-performance, geo-distributed, and federated metadata lake. It manages metadata directly in different sources, types, and regions, providing users with unified metadata access for data and AI assets.

Gravitino Architecture

🚀 Key Features

  • Unified Metadata Management: Manage diverse metadata sources through a single model and API (e.g., Hive, MySQL, HDFS, S3).
  • End-to-End Data Governance: Features like access control, auditing, and discovery across all metadata assets.
  • Direct Metadata Integration: Changes in underlying systems are immediately reflected via Gravitino’s connectors.
  • Geo-Distribution Support: Share metadata across regions and clouds to support global architectures.
  • Multi-Engine Compatibility: Seamlessly integrates with query engines without modifying SQL dialects.
  • AI Asset Management (WIP): Support for AI model and feature tracking.

🌐 Common Use Cases

  • Federated metadata discovery across data lakes and data warehouses
  • Multi-region metadata synchronization for hybrid or multi-cloud setups
  • Data and AI asset governance with unified audit and access control
  • Plug-and-play access for engines like Trino or Spark
  • Support for evolving metadata standards, including AI model lineage

📚 Documentation

The latest Gravitino documentation is available at gravitino.apache.org/docs/latest.

This README provides a basic overview; visit the site for full installation, configuration, and development documentation.

🧪 Quick Start

Use Gravitino Playground (Recommended)

Gravitino provides a Docker Compose–based playground for a full-stack experience.
Clone or download the Gravitino Playground repository and follow its README.

Run Gravitino Locally

  1. Download and extract a binary release.
  2. Edit conf/gravitino.conf to configure settings.
  3. Start the server:
./bin/gravitino.sh start
  1. To stop:
./bin/gravitino.sh stop

Press CTRL+C to stop.

  1. (Optional) Use the new UI
  • To switch to the new UI at runtime: edit conf/gravitino-env.sh (or set the environment variable before starting) and set GRAVITINO_USE_WEB_V2 to true:
export GRAVITINO_USE_WEB_V2=true
./bin/gravitino.sh start
  • Alternatively, you can remove the GRAVITINO_USE_WEB_V2=... line from conf/gravitino-env.sh (the template defaults to false); removing that line will revert the service to the legacy UI behavior.

🧊 Iceberg REST Catalog

Gravitino provides a native Iceberg REST catalog service.
See: Iceberg REST catalog service

🗄️ Lance REST Catalog

Gravitino provides a native Lance REST catalog service.
See: Lance REST catalog service

🔌 Trino Integration

Gravitino includes a Trino connector for federated metadata access.
See: Using Trino with Gravitino

🛠️ Building from Source

Gravitino uses Gradle. Windows is not currently supported.

Clean build without tests:

./gradlew clean build -x test

Build a distribution:

./gradlew compileDistribution -x test

Or compressed package:

./gradlew assembleDistribution -x test

Artifacts are output to the distribution/ directory.

More build options: How to build Gravitino

👨‍💻 Developer Resources

🤝 Contributing

We welcome all kinds of contributions—code, documentation, testing, connectors, and more!

To get started, please read our CONTRIBUTING.md guide.

🔗 ASF Resources

🪪 License

Apache Gravitino is licensed under the Apache License, Version 2.0.
See the LICENSE file for details.

Apache®, Apache Gravitino™, Apache Hadoop®, Apache Hive™, Apache Iceberg™, Apache Kafka®, Apache Spark™, Apache Submarine™, Apache Thrift™, and Apache Zeppelin™ are trademarks of the Apache Software Foundation in the United States and/or other countries.