⌘K ctrl+k
Search Shortcut cmd + k | ctrl + k
DuckDB 2.0 ドキュメント 全文検索
per page, with , order by , clip by
Results of 1 - 7 of about 7 for probe (0.004 sec.)
OpenHarmony 12777
DuckDB supports building for OpenHarmony (OHOS) AArch64 (ARM64) on a best-effort basis. On this platform, DuckDB reports the platform name openharmony_arm64 . Prebuilt binaries and extensions are not distributed for this platform. Prerequis ... cmake --build build/openharmony --parallel DUCKDB_EXPLICIT_PLATFORM is required when cross-compiling because the platform probe binary cannot run on the build host. The resulting build/openharmony/duckdb is an AArch64 musl binary. Building on an Open ... Harmony Device On a device, CMake detects the OpenHarmony toolchain and the platform probe runs natively, so DUCKDB_EXPLICIT_PLATFORM is not required: cmake -G Ninja -B build/openharmony \ -DCMAKE_TOOLCHAIN_FILE=" ...
https://man.mtool.work/duckdb/2.0/dev/building/openharmony.html
Querying Parquet Metadata 10505
Parquet Metadata The parquet_metadata function can be used to query the metadata contained within a Parquet file, which reveals various internal details of the Parquet file such as the statistics of the different columns. This can be useful ... NT , USMALLINT , INTEGER , UINTEGER , BIGINT , UBIGINT Floating point types: FLOAT , DOUBLE VARCHAR BLOB The parquet_bloom_probe(filename, column_name, value) function shows which row groups can be excluded when filtering for a given value of a given ... column using the Bloom filter. For example: FROM parquet_bloom_probe('my_file.parquet', 'my_col', 500); file_name row_group_id bloom_filter_excludes my_file.parquet 0 true ... ... ... my_file ...
https://man.mtool.work/duckdb/2.0/data/parquet/metadata.html
Join Operations 9215
How to Force a Join Order DuckDB has a cost-based query optimizer, which uses statistics in the base tables (stored in a DuckDB database or Parquet files) to estimate the cardinality of operations. Turn Off the Join Order Optimizer To turn ... off the join order optimizer, set the following PRAGMA s : SET disabled_optimizers = 'join_order,build_side_probe_side'; This disables both the join order optimizer and left/right swapping for joins. This way, DuckDB builds a left-deep ...
https://man.mtool.work/duckdb/2.0/guides/performance/join_operations.html
Indexing 8251
DuckDB has two types of indexes: zonemaps and ART indexes. Zonemaps DuckDB automatically creates zonemaps (also known as min-max indexes) for the columns of all general-purpose data types . Operations like predicate pushdown into scan opera ... n. An ART index does not affect the performance of join, aggregation, and sorting queries. ART Index Scans ART index scans probe a single-column ART index for the requested data instead of scanning a table sequentially. Probing can improve the perform ...
https://man.mtool.work/duckdb/2.0/guides/performance/indexing.html
Profiling 7924
Profiling is essential to help understand why certain queries exhibit specific performance characteristics. DuckDB contains several built-in features to enable query profiling, which this page covers. For a high-level example of using EXPLA ... /path/to/file.json Notation in Query Plans In query plans, the hash join operators adhere to the following convention: the probe side of the join is the left operand, while the build side is the right operand. Join operators in the query plan show the ...
https://man.mtool.work/duckdb/2.0/dev/profiling.html
Metrics 7597
DuckDB provides a set of metrics that can be used to monitor the performance and health of the database. Metrics are named ⟨group⟩.⟨metric⟩ , e.g., query.total_time or operator.timing . The set of collected metrics is controlled with the tr ... pagation , optimizer.common_subexpressions , optimizer.common_aggregate , optimizer.column_lifetime , optimizer.build_side_probe_side , optimizer.limit_pushdown , optimizer.top_n , optimizer.compressed_materialization , optimizer.duplicate_groups , op ...
https://man.mtool.work/duckdb/2.0/dev/metrics.html
FROM and JOIN Clauses 7288
The FROM clause specifies the source of the data on which the remainder of the query should operate. Logically, the FROM clause is where the query starts execution. The FROM clause can contain a single table, a combination of multiple table ... es.when, price (but NOT prices.when): If you combine USING with a SELECT * like this, the query will return the left side (probe) column values for the matches, not the right side (build) column values. To get the prices times in the example, you will ...
https://man.mtool.work/duckdb/2.0/sql/query_syntax/from.html
PREV 1 NEXT
DuckDB 2.0 Documentation / man.mtool.work