MonetDB
Data warehousemonetdb
Column-store relational database for analytical queries, held in memory-mapped files.
- Provider
- default
- Kind
- Data warehouse
- Category
- Data
- Official docs
- https://www.monetdb.org/documentation/
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| concurrencyControl | enum | optimistic | no | optimistic | inherited |
| format | enum | columnar | row | no | columnar | ▸ columnar |
| managed | boolean | — | no | false | ▸ false |
| memoryMapped | boolean | — | no | true | inherited |
| realtime | boolean | — | no | false | ▸ false |
| upsert | boolean | — | no | false | ▸ true |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
No rule reads this kind yet. That is a gap, not a guarantee.
nodes:
- { id: "monetdb", component: "monetdb" }AnalyticDBalibaba-analyticdbApsaraDB for ClickHousealibaba-clickhouseHologresalibaba-hologresMaxComputealibaba-maxcomputeApsaraDB for SelectDBalibaba-selectdbAmazon Athenaaws-athenaAmazon RedshiftredshiftAzure Analysis Servicesazure-analysis-servicesMicrosoft Fabricazure-fabricAzure Synapse Analyticsazure-synapseR2 SQLcloudflare-r2-sqlClickHouseclickhouseGeneric data warehousedata-warehouseDatabricks SQLdatabricks-sqlApache DorisdorisDremiodremioApache DrilldrillApache DruiddruidDuckDBduckdbExasolexasolFireboltfireboltGreenplumgreenplumApache HivehiveApache ImpalaimpalaApache KylinkylinMotherDuckmotherduckApache PinotpinotPrestoprestoSnowflakesnowflakeStarRocksstarrocksTeradata VantageteradataTrinotrinoVerticaverticaGoogle BigQuerybigqueryDb2 Warehouse as a Serviceibm-db2-warehouseNetezza Performance Server as a Serviceibm-netezzaIBM watsonx.dataibm-watsonx-dataAutonomous AI Lakehouseoci-autonomous-data-warehouseMySQL HeatWave clusteroci-mysql-heatwave-cluster
# yaml-language-server: $schema=../../schema/component.schema.json # MonetDB: column-store relational database for analytical queries. Per the MonetDB documentation # columns are held in memory-mapped binary files and transactions run under optimistic concurrency # control, so conflicts are detected at commit rather than prevented by locks. schemaVersion: "1" type: "component" id: "monetdb" kind: "data-warehouse" provider: "default" docs: "https://www.monetdb.org/documentation/" defaults: managed: false format: "columnar" realtime: false upsert: true properties: memoryMapped: type: "boolean" default: true concurrencyControl: type: "enum" values: ["optimistic"] default: "optimistic"