awesome-repositories.com
博客
awesome-repositories.com

通过 AI 驱动的搜索,发现最优秀的开源仓库。

探索精选搜索开源替代品自托管软件博客网站地图
项目关于排名机制媒体报道MCP 服务器
法律隐私政策服务条款
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·

6 个仓库

Awesome GitHub RepositoriesCatalog Integration

Publishing table metadata to open catalog formats for external data discovery.

Distinct from Data Export: Distinct from general data export: focuses on publishing metadata for data lake interoperability rather than raw data export.

Explore 6 awesome GitHub repositories matching data & databases · Catalog Integration. Refine with filters or upvote what's useful.

Awesome Catalog Integration GitHub Repositories

用 AI 发现最棒的仓库。我们将通过 AI 为您搜索最匹配的仓库。
  • questdb/questdbquestdb 的头像

    questdb/questdb

    17,062在 GitHub 上查看↗

    QuestDB is a high-performance, distributed time-series database designed for the ingestion, storage, and analysis of massive datasets. It functions as a real-time analytics platform that utilizes a columnar storage engine to optimize disk input and output, enabling efficient analytical scans and complex windowing operations on streaming data. The platform distinguishes itself through specialized capabilities for handling asynchronous time-series streams, including advanced join algorithms that align disparate data sets based on precise timestamp lookups. It supports high-volume ingestion thro

    Publishes table metadata to open catalog formats to enable direct data access from external analytical tools.

    Javacapital-marketscppdatabase
    在 GitHub 上查看↗17,062
  • dbt-labs/dbt-coredbt-labs 的头像

    dbt-labs/dbt-core

    13,051在 GitHub 上查看↗

    dbt-core is a command-line framework for transforming data within a warehouse using modular SQL and version control. It functions as a data transformation engine that enables users to define data structures and business logic through declarative configuration files, which the system then compiles into executable code. By managing complex data dependencies through a directed acyclic graph, it ensures that transformation tasks execute in the correct order while maintaining a manifest-driven state to track lineage and execution history. The project distinguishes itself through an adapter-based d

    Registers table metadata in external Iceberg catalogs during materialization to ensure data objects are discoverable across different compute engines.

    Rustanalyticsbusiness-intelligencedata-modeling
    在 GitHub 上查看↗13,051
  • apache/icebergapache 的头像

    apache/iceberg

    8,972在 GitHub 上查看↗

    Iceberg is an open table format and big data table manager designed for huge analytic datasets in cloud storage. It provides a specification for tracking large-scale datasets to maintain transactional consistency and structural integrity. The project utilizes a standardized REST catalog interface to manage table metadata, ensuring interoperability between different compute engines. This allows diverse query engines to connect to a single table interface and maintain consistency across different processing frameworks. Its core capabilities include managing large-scale analytic tables, coordin

    Implements a common API specification to ensure interoperability between different catalog versions and client engines.

    Java
    在 GitHub 上查看↗8,972
  • apache/hiveapache 的头像

    apache/hive

    6,012在 GitHub 上查看↗

    Apache Hive is a SQL-on-Hadoop data warehouse that enables querying and managing petabytes of data stored in distributed storage such as HDFS and cloud storage services. It provides a familiar SQL interface for batch analytics and reporting, supported by a core set of components including the HiveServer2 Thrift service for remote query execution, the Hive Metastore Service for central metadata management, the Hive ACID Transaction Engine for concurrent read-write operations, and the Hive LLAP Interactive Engine for low-latency analytical processing. The WebHCat REST API offers an HTTP interfac

    Connects to an Iceberg REST catalog secured with OAuth2 to manage tables with snapshots and branches.

    Javaapachebig-datadatabase
    在 GitHub 上查看↗6,012
  • treeverse/lakefstreeverse 的头像

    treeverse/lakeFS

    5,406在 GitHub 上查看↗

    lakeFS 是一个数据湖版本控制系统,为存储在对象存储中的大型数据集提供类似 Git 的分支和提交功能。它作为一个版本控制层,支持创建不可变快照、原子提交和零拷贝分支,从而在不复制物理文件的情况下为数据实验创建隔离环境。 该系统充当 S3 兼容的存储网关和 Iceberg REST 目录,允许标准云存储协议和兼容客户端管理版本化表。它通过使用事件驱动的钩子系统在更改合并到生产环境之前根据治理策略验证数据集,从而充当数据质量守门人。 该平台涵盖了广泛的数据治理功能,包括 Pull Request 协作、基于角色的访问控制和数据血缘追踪。它为工作流编排、机器学习管线和各种大数据计算引擎提供了集成,支持多云存储连接以及通过 SSO 和 SCIM 进行身份同步。 该软件可以使用二进制文件、容器或 Helm Chart 安装,以便在 Kubernetes 上部署。

    Synchronizes table metadata to external query engines and warehouses for SQL-based access.

    Go
    在 GitHub 上查看↗5,406
  • anomalyco/models.devanomalyco 的头像

    anomalyco/models.dev

    2,694在 GitHub 上查看↗

    models.dev is a directory and intelligence system for large language models that provides a standardized catalog of technical specifications, provider mappings, and pricing data. It serves as a central index for model metadata, including context windows, output limits, and release dates. The project functions as a capability index and pricing comparison tool, allowing for the analysis of token costs across different hosting providers. It maps generic model names to the specific API identifiers required by various third-party platforms and tracks support for functional features such as tool ca

    Provides detailed model metadata, including modalities and release dates, via a standardized data format.

    TypeScript
    在 GitHub 上查看↗2,694
  1. Home
  2. Data & Databases
  3. Data Export
  4. Catalog Integration

探索子标签

  • Catalog Specification Standards1 个子标签Common API specifications that ensure interoperability between different catalog implementations and client engines. **Distinct from Catalog Integration:** Distinct from Catalog Integration: focuses on the definition of the standard API specification itself rather than the act of publishing metadata.
  • Federated CatalogsMetadata catalogs that distribute discovery and governance across multiple cloud services in real time. **Distinct from Catalog Integration:** Specifically covers the federation aspect of metadata discovery across services, whereas Catalog Integration is broader publishing.