Results of 1 - 10 of about 16 for events (0.003 sec.)
- Variant Type 13706
- The VARIANT type stores typed, binary data where each row is self-contained with its own type information. This differs from the JSON type , which is physically stored as text. Because type metadata is embedded per-value, VARIANT provides b
...s Storing Different Types in the Same Column A VARIANT column can hold values of different types across rows: CREATE TABLE events (id INTEGER, data VARIANT); INSERT INTO events VALUES (1, 42::VARIANT), (2, 'hello world'::VARIANT), (3, [1, 2, 3]::VARIAN...T), (4, {'name': 'Alice', 'age': 30}::VARIANT); SELECT * FROM events; ┌───────┬────────────────────────────┐ │ id │ data │ │ int32 │ variant │ ├───────┼────────────────────────────┤ │ 1 │ 42...a Value Use variant_typeof to inspect the underlying type of each row: SELECT id, data, variant_typeof(data) AS vtype FROM events; ┌───────┬────────────────────────────┬───────────────────┐ │ id │ data │ vtype │ │ int32 │ variant │ varchar │ ├───────┼─... - https://man.mtool.work/duckdb/2.0/sql/data_types/variant.html
- Writing to Iceberg 10275
- The DuckDB iceberg extension supports writing to Iceberg tables when an Iceberg catalog is attached. Writing to a table read directly from storage with iceberg_scan is not supported: the catalog is required to commit the new table metadata.
...lue1', 'property2' = 'value2' ); Tables can also be created from the result of a query: CREATE TABLE iceberg_catalog.sales.events_copy AS FROM iceberg_catalog.sales.events; Table properties can also be inspected and modified after creation, see Table P...The UPDATE and DELETE statements are supported on both partitioned and unpartitioned tables: UPDATE iceberg_catalog.sales.events SET event_name = 'view' WHERE id = 1; DELETE FROM iceberg_catalog.sales.events WHERE event_time < TIMESTAMP '2026-01-01';...o a multiple of w for numeric columns). This is useful for prefix-based partitioning. CREATE TABLE iceberg_catalog.default.events ( event_id BIGINT, user_id BIGINT, country VARCHAR, event_time TIMESTAMP ) PARTITIONED BY (day(event_time), bucket(16, use... - https://man.mtool.work/duckdb/2.0/core_extensions/iceberg/writing_to_iceberg.htm...
- Profile and Monitor 10171
- Overview The JDBC driver exposes several ways to observe a running or completed query: cancelling and timing out queries, polling query progress, retrieving profiling output, and emitting memory-usage events through Java Flight Recorder . T
...System.out.println(profile); } Memory Monitoring with JFR On a JFR-capable JVM , the driver can emit Java Flight Recorder events describing DuckDB's internal memory usage, so that any JFR-aware tool — JDK Mission Control, the jfr command line tool, co...n can be set in the URL: jdbc:duckdb:/tmp/my_database;jdbc_jfr_memory_monitor=analytics-db Property value Effect absent No events emitted for this connection. empty string No events emitted, the same as absent. non-empty string Events emitted, tagged w...event> When no recording enables the event, the driver does no work: the underlying duckdb_memory() query is never issued. Event Schema While a recording is active with the event enabled, the driver emits one duckdb.MemoryUsage event per DuckDB memory... - https://man.mtool.work/duckdb/2.0/clients/java/profiling.html
- Iceberg Extension 10067
- The iceberg extension implements support for the Apache Iceberg open table format . There are two ways to work with Iceberg in DuckDB: Individual tables are read directly from storage, by pointing at a table's metadata. This requires no cat
...alog⟩.⟨schema⟩.⟨table⟩ and query or modify them with regular SQL. SHOW ALL TABLES; SELECT count(*) FROM my_catalog.default.events; INSERT INTO my_catalog.default.events VALUES (1, 'click', now()); The metadata functions also work on catalog tables when...passed a fully qualified name, e.g., iceberg_snapshots(my_catalog.default.events) . For the full set of write operations — partitioning, UPDATE , DELETE , MERGE INTO , ALTER TABLE , and table properties...hed catalog, time travel with the AT clause directly on the table: -- Using a snapshot id SELECT * FROM my_catalog.default.events AT (VERSION => ⟨snapshot_id⟩); -- Using a timestamp SELECT * FROM my_catalog.default.events AT (TIMESTAMP => TIMESTAMP '20... - https://man.mtool.work/duckdb/2.0/core_extensions/iceberg/overview.html
- Connect 9097
- Overview Every DuckDB feature reachable from Java starts with a Connection . This page covers the JDBC URL forms the driver accepts, how DuckDB and driver options are passed and which of them win, how connections come to share (or not share
...rker comment: -- Runs once, when the database instance is created. SET memory_limit = '4GB'; CREATE OR REPLACE VIEW recent_events AS SELECT * FROM events WHERE ts > now() - INTERVAL 7 DAYS; /* DUCKDB_CONNECTION_INIT_BELOW_MARKER */ -- Runs for every co...metadata.ducklake' AS lake (DATA_PATH 'lake_files/')"); stmt.execute("USE lake"); stmt.execute("CREATE TABLE IF NOT EXISTS events (id INTEGER, payload VARCHAR)"); stmt.execute("INSERT INTO events VALUES (1, 'hello'), (2, 'world')"); try (ResultSet rs =...stmt.executeQuery("SELECT count(*) FROM events")) { rs.next(); System.out.println(rs.getLong(1)); } } The ducklake extension is autoloaded on the first ATTACH ; an expli... - https://man.mtool.work/duckdb/2.0/clients/java/connecting.html
- Variant Functions 9097
- This section describes functions that operate on the VARIANT type . New Most variant_* functions were introduced in DuckDB 2.0. The variant_extract , variant_normalize and variant_typeof functions were already available in DuckDB 1.5. Name
...variant_* functions are useful for inspecting and filtering semi-structured data stored in a VARIANT column: CREATE TABLE events (payload VARIANT); INSERT INTO events VALUES ('{"user": {"id": 42, "tags": ["a", "b"]}}'::JSON::VARIANT); SELECT variant_t...ype(payload), variant_keys(payload) FROM events; SELECT * FROM events WHERE variant_contains(payload, {'user': {'id': 42}}::VARIANT);... - https://man.mtool.work/duckdb/2.0/sql/functions/variant.html
- Delta Extension 8993
- The delta extension adds support for the Delta Lake open-source storage format . It is built using the Delta Kernel . The extension reads Delta tables, local and remote, and writes them: it can create tables and append to them. For implemen
...able, attach the location for it and create a table named after the attached database: ATTACH 's3://⟨my_bucket⟩/⟨path⟩' AS events (TYPE delta); CREATE TABLE events.events (id BIGINT, region VARCHAR) PARTITIONED BY (region); INSERT INTO events VALUES (1..., 'eu'); Only CREATE TABLE needs the full events.events name: without the database name, it creates the table in the default database. The table can be read and written wi... - https://man.mtool.work/duckdb/2.0/core_extensions/delta.html
- Parquet Tips 8023
- Below is a collection of tips to help when dealing with Parquet files. Tips for Reading Parquet Files Use union_by_name When Loading Files with Different Schemas The union_by_name option can be used to unify the schema of files that have di
...n-overlapping between row groups, so that highly selective queries on those columns scan far fewer row groups: COPY (FROM 'events.parquet' ORDER BY event_time) TO 'events-sorted.parquet' (FORMAT parquet); This pairs well with a ROW_GROUP_SIZE that keep... - https://man.mtool.work/duckdb/2.0/data/parquet/tips.html
- CLI Charting with YouPlot 8023
- DuckDB can be used with CLI graphing tools to quickly pipe input to stdout to graph your data in one line. YouPlot is a Ruby-based CLI tool for drawing visually pleasing plots on the terminal. It can accept input from other programs by pipi
...h a quick curl from GitHub to see what a certain user has been up to lately. curl -sL "https://api.github.com/users/dacort/events?per_page=100" \ | duckdb -s "COPY (SELECT type, count(*) AS event_count FROM read_json('/dev/stdin') GROUP BY 1 ORDER BY 2...DESC LIMIT 10) TO '/dev/stdout' WITH (FORMAT csv, HEADER)" \ | uplot bar -d, -H -t "GitHub Events for @dacort"... - https://man.mtool.work/duckdb/2.0/guides/data_viewers/youplot.html
- Logging 8023
- DuckDB implements a logging mechanism that provides users with detailed information about events such as query execution, performance metrics and system events. Warning Logs may contain sensitive information, including secrets and credentia
...ction with DuckDB's Filesystem Yes HTTP Logs all HTTP traffic from DuckDB's internal HTTP client Yes PhysicalOperator Logs events emitted by physical operators during query execution Yes Metrics Logs profiling metrics collected during query execution Y... - https://man.mtool.work/duckdb/2.0/operations_manual/logging/overview.html
DuckDB 2.0 Documentation / man.mtool.work