Tagged articles
Predicate Pushdown
15 articles · Page 1 of 1
This article details production practices for accelerating StarRocks queries on Paimon external tables, covering architecture, table design (partitioning, bucketing, compaction), dirty data handling, catalog configuration, predicate pushdown verification, SQL optimization with partition/bucket pruning, query method selection (direct, async materialized views, hot/cold tiering), and BE-level tuning.
Bucket PruningMaterialized ViewPaimon
0 likes · 22 min read

This article details the design and implementation of a cloud‑native, real‑time monitoring system for Alibaba Cloud OpenAPI, covering background challenges, a Flink‑SLS architecture, multi‑region data processing, checkpoint and state‑backend tuning, source‑side predicate pushdown, visualization with Grafana, and production results.
FlinkPredicate PushdownSLS
0 likes · 21 min read

A StarRocks case study shows how early null filtering and Bloom indexes reduced a 200M-row query from 12s to under 1s while eliminating CN node OOM restarts through predicate pushdown and partition pruning.
Bloom IndexCN NodeNull Filtering
0 likes · 15 min read

This article presents a series of MySQL performance‑tuning techniques—including smarter LIMIT usage, avoiding implicit type conversion, rewriting joins, handling mixed ordering, replacing EXISTS with joins, pushing predicates into subqueries, early row limiting, and using WITH clauses—to dramatically reduce query execution time across common scenarios.
MySQLPredicate PushdownQuery Performance
0 likes · 13 min read

This article explains common MySQL performance pitfalls such as large‑offset LIMIT queries, implicit type conversion, sub‑query updates, mixed sorting, inefficient EXISTS clauses, predicate push‑down limitations, and demonstrates how rewriting with proper indexes, JOINs, early range reduction, and WITH (CTE) statements can reduce execution time from seconds to milliseconds.
CTEMySQLPredicate Pushdown
0 likes · 12 min read

This article presents practical MySQL performance tuning methods, covering LIMIT pagination, implicit type conversion pitfalls, rewriting joins for updates/deletes, mixed-order sorting, replacing EXISTS with joins, predicate pushdown, early result limiting, and intermediate result pushdown, each illustrated with SQL examples and execution plan analyses.
MySQLPredicate PushdownQuery Performance
0 likes · 13 min read

This article explains nine practical MySQL optimization methods—including smarter LIMIT usage, implicit conversion pitfalls, JOIN‑based updates, mixed ordering tricks, EXISTS rewrites, predicate pushdown, early range reduction, intermediate result pushdown, and a concise summary—showing how to transform slow queries into sub‑millisecond operations.
LIMIT clauseMySQLPredicate Pushdown
0 likes · 12 min read


ITPUBApr 7, 2022 · Databases
The article examines Oracle’s automatic predicate pushdown that rewrites SQL statements, illustrates its impact on execution plans with trace data and queries, and draws lessons for improving domestic database products and support in the wake of recent geopolitical shifts.
CBOOraclePredicate Pushdown
0 likes · 9 min read


ITPUBMar 7, 2022 · Databases
The article examines Oracle’s unexpected predicate‑pushdown rewrite observed in trace files, shows how it alters execution plans through a virtual column index, and draws lessons for Chinese database vendors on product depth, architecture design, and after‑sales support to close the gap with global leaders.
OraclePredicate Pushdowncost-based optimizer
0 likes · 8 min read

The article explains how applying filters, projections, and predicate pushdown in Hadoop and Hive reduces data volume, speeds up MapReduce jobs, and improves performance, while also covering join limitations and providing a Java Mapper example for practical implementation.
HadoopHiveMapReduce
0 likes · 4 min read

The article examines SparkSQL’s predicate‑pushdown behavior for left outer joins, detailing four rules that show when pushing join‑condition filters to the left or right tables yields correct, faster results and when it produces incorrect outcomes, highlighting both performance gains and subtle errors.
Outer JoinPredicate PushdownSparkSQL
0 likes · 7 min read

SparkSql optimizes inner‑join queries by pushing predicates to the scan phase, allowing filters connected with AND to be applied before the join without changing results, while OR‑connected filters can be unsafe except when they involve the join key or partitioned tables which use partition pruning.
Partition PruningPredicate PushdownSQL Optimization
0 likes · 10 min read

The article recounts a real‑world Oracle SQL case where a REGEXP_SUBSTR‑based IN subquery caused the optimizer to abandon an index range scan, explores why predicate pushdown fails with CONNECT BY recursion, documents attempted hints, rewrites, and the ultimate lessons for SQL performance tuning.
IN SubqueryOraclePerformance Tuning
0 likes · 17 min read

When a critical Oracle query suddenly slowed down on regional databases while the central server remained fast, I diagnosed the issue, discovered execution‑plan differences caused by missing predicate push‑down, attempted a plan‑binding solution, faced unexpected failures, and ultimately rewrote the SQL using a WITH clause to meet a tight deadline.
Database PerformanceOraclePredicate Pushdown
0 likes · 11 min read

A detailed Oracle case study shows how a seemingly harmless view modification triggered a cascade of performance regressions, how nested UNION ALLs, missing indexes, and optimizer choices prevented predicate pushdown, and the step‑by‑step rewrites—including hints, index creation, and scalar subqueries—that finally restored fast query execution.
IndexOraclePredicate Pushdown
0 likes · 13 min read
