[fix](point query) fix point query IllegalStateException on LIST partition by hulincup · Pull Request #66416 · apache/doris

hulincup · 2026-08-04T03:56:51Z

Motivation

A short-circuit point query on a table with PARTITION BY LIST and more than one tablet per partition threw IllegalStateException (msg: null):

java.lang.IllegalStateException
at com.google.common.base.Preconditions.checkState(Preconditions.java:499)
at org.apache.doris.qe.PointQueryExecutor.setScanRangeLocations(PointQueryExecutor.java:120)

Repro (from the issue):

CREATETABLEtbl_point_query (
pk varchar(64), _id bigint
) UNIQUE KEY(pk, _id)
PARTITION BY LIST (`pk`) (PARTITION p_abcd VALUESIN ('abcd'))
DISTRIBUTED BY HASH(pk, _id) BUCKETS AUTO
PROPERTIES ("store_row_column"="true","enable_unique_key_merge_on_write"="true","light_schema_change"="true");
INSERT INTO tbl_point_query VALUES ('abcd', 1);
SELECT*FROM tbl_point_query WHERE pk ='abcd'AND _id =1; -- IllegalStateException

Root cause

In OlapScanNode.computeTabletInfo, the distribution prune flag is isNereids && !isPointQuery, which forces point queries onto the legacy HashDistributionPruner path. That path prunes using columnFilters, which is populated by computeColumnsFilter from the legacy conjuncts. For a nereids-planned direct point query the conjuncts are not in the legacy form that feeds columnFilters, so the pruner returns all tablets of the matched partition. PointQueryExecutor.setScanRangeLocations then hits checkState(scanTabletIds.size() == 1) with an un-pruned list and crashes. The bug is masked when a partition has a single tablet (e.g. BUCKETS 1), so it only surfaces with BUCKETS AUTO / multiple buckets — which is why LIST-partition users hit it.

Change

Use the nereids-pruned tablet set for point queries when it has already been pruned to a single tablet (the direct-query case, where the key literals are known at planning time and PhysicalPlanTranslator populates nereidsPrunedTabletIds from the nereids plan's selectedTabletIds). When the pruned set still contains multiple tablets (a prepared-statement point query whose parameter values are unknown at planning time), keep the legacy runtime-prune path, so that path is not regressed.

booleanuseNereidsPrune = isNereids && (!isPointQuery || nereidsPrunedTabletIds.size() == 1);
Collection<Long> prunedTabletIds = distributionPrune(..., useNereidsPrune);

Behavior matrix:

Normal (non-point) query: unchanged (!isPointQuery is true).
Direct point query: nereidsPrunedTabletIds has 1 tablet → uses nereids path → pruned to 1 → fixed.
Prepared point query: nereidsPrunedTabletIds has multiple tablets (value unknown at planning) → falls back to legacy runtime prune → unchanged.

Files

fe/fe-core/src/main/java/org/apache/doris/planner/OlapScanNode.java — the prune-flag change.
regression-test/suites/point_query_p0/test_point_query_list_partition.groovy — new regression test reproducing the issue (LIST partition + BUCKETS 3 + short-circuit point query).

Verification

I could not build/run FE locally for this change; verification relies on CI. The new regression test reproduces the original failure (it asserts the query returns 1 row instead of throwing) and the existing point_query_p0 suites guard the non-regression side.

Test plan

CI: new point_query_p0/test_point_query_list_partition passes.
CI: existing point_query_p0/* (incl. test_point_query_partition, test_point_query, prepared-statement paths) pass unchanged.
Maintainer review: please confirm the direct-vs-prepared branching is the right cut — I could not fully verify the prepared-statement runtime-prune path without a local cluster.

Point query (short-circuit) on a table with PARTITION BY LIST and multiple tablets per partition threw IllegalStateException because the tablet list was not pruned to a single tablet. In OlapScanNode.computeTabletInfo, point queries forced the legacy HashDistributionPruner path (isNereids && !isPointQuery), which relies on columnFilters populated from legacy conjuncts. For a nereids-planned direct point query those column filters are not populated, so the pruner returned all tablets of the matched partition and PointQueryExecutor.setScanRangeLocations hit its single-tablet checkState. Use the nereids-pruned tablet set for point queries when it has already been pruned to a single tablet (direct query, literals known at planning time). When the pruned set still contains multiple tablets (prepared statement, parameter values unknown at planning time), keep the legacy runtime-prune path so that path is not regressed. Fixesapache#66030

hello-stephen · 2026-08-04T03:56:56Z

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

What problem was fixed (it's best to include specific error reporting information). How it was fixed.
Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
What features were added. Why was this function added?
Which code was refactored and why was this part of the code refactored?
Which functions were optimized and what is the difference before and after the optimization?

…ssion test Address review feedback on apache#66416: - Hoist useNereidsPrune out of the per-partition loop (loop-invariant; isNereids/isPointQuery are already hoisted above it). - Add a prepared-statement point-query case to the regression test to guard the no-regression property: a prepared point query (parameter value unknown at planning) keeps taking the legacy runtime-prune path and must still resolve to the correct tablet.

hulincup · 2026-08-04T05:46:07Z

Thanks for the checklist. Describing this PR per the points (the PR description above covers these in detail; summarizing here):

1. Problem fixed & how
Issue #66030: a short-circuit point query on a table with PARTITION BY LIST and more than one tablet per partition threw IllegalStateException (msg: null) at PointQueryExecutor.setScanRangeLocations (single-tablet checkState).
Root cause: in OlapScanNode.computeTabletInfo, point queries forced the legacy HashDistributionPruner path (isNereids && !isPointQuery), which prunes via columnFilters. For a nereids direct point query those column filters are not populated, so the pruner returned all tablets of the matched partition → the single-tablet check failed. Fixed by using the nereids-pruned tablet set when it has already been pruned to one tablet.

2. Behavior modified (previous vs. now, impact)

Previous: direct point query → legacy path with empty columnFilters → all tablets → crash. Prepared point query → legacy runtime prune (works).
Now: direct point query (nereids pruned to 1 tablet) → nereids path → 1 tablet → fixed. Prepared point query (multiple tablets, value unknown at planning) → legacy runtime prune, unchanged. Non-point / non-nereids queries unchanged.
Impact: only the crashing case changes; every other path is provably unchanged (the boolean differs from the old value only when isNereids && isPointQuery && size==1).

3. Features added — N/A.
4. Code refactored — N/A (only a one-line logic change + hoisting a loop-invariant local).
5. Functions optimized — N/A.

I could not build/run FE locally; verification relies on CI. The new regression test (test_point_query_list_partition) reproduces the original failure and adds a prepared-statement case to guard the no-regression path.

eldenmoon · 2026-08-05T02:44:30Z

run buildall

eldenmoon · 2026-08-05T02:44:37Z

/review

github-actions · 2026-08-05T02:46:26Z

Codex automated review failed and did not complete.

Error: You've hit your usage limit. Visit https://chatgpt.com/codex/settings/usage to purchase more credits or try again at Aug 8th, 2026 3:37 AM.
Workflow run: https://github.com/apache/doris/actions/runs/30970232575

The selected account is excluded until 2026-08-08T03:37:00Z. Please trigger /review again; another configured account may be available.

Copilot

Pull request overview

Fixes a Nereids-planned short-circuit point query crash on PARTITION BY LIST tables with multiple tablets per partition by allowing Nereids’ pre-pruned tablet set to be used for point queries when it is already reduced to a single tablet. Adds a regression test covering both the direct point-query path (fixed) and the server-side prepared-statement path (must not regress).

Changes:

Adjust tablet distribution pruning selection in OlapScanNode.computeTabletInfo() to use Nereids pruning for point queries only when nereidsPrunedTabletIds.size() == 1.
Add regression coverage for LIST partition + multiple buckets + short-circuit point query, plus a prepared-statement variant to guard legacy runtime pruning.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
`fe/fe-core/src/main/java/org/apache/doris/planner/OlapScanNode.java`	Switches point-query distribution pruning to use Nereids-pruned tablet IDs when already singular to avoid multi-tablet scan ranges causing `IllegalStateException`.
`regression-test/suites/point_query_p0/test_point_query_list_partition.groovy`	New regression suite reproducing the LIST-partition point-query failure and validating both direct and prepared-statement execution paths.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

hulincup · 2026-08-05T03:21:07Z

+ def explain = sql """EXPLAIN SELECT * FROM ${tableName} WHERE pk = 'abcd' AND _id = 1"""
+ assertTrue(explain.toString().contains("SHORT-CIRCUIT"))


Good point — done in 545f4ec. Switched to the regression framework's explain { sql(...); contains "SHORT-CIRCUIT" } helper, matching the idiom used across point_query_p0 (test_point_query.groovy, load_ck.groovy).

hulincup · 2026-08-05T03:21:19Z

+ assertEquals(1, rowCount)
+ }
+
+ sql """DROP TABLE IF EXISTS ${tableName}"""


I'll keep the trailing DROP TABLE IF EXISTS. The other point_query_p0 suites that partition (test_point_query_partition.groovy:117, test_point_query_timezone.groovy:70) drop at the end too, so this matches the existing convention rather than the keep-table-around one.

Address Copilot review feedback on apache#66416: replace the brittle sql("EXPLAIN ...") + toString().contains(...) with the regression framework's explain { sql(...); contains ... } helper, matching the idiom used across the point_query_p0 suite (e.g. test_point_query.groovy, load_ck.groovy).

hulincup · 2026-08-05T03:20:44Z

Thanks @eldenmoon.

On run buildall: the CI status shows "Skip review via skip buildall comment" was skipped and the buildall job has not started — let me know if a specific label or command is needed to trigger it on this PR; I will retrigger as needed.

On /review: the Codex automated review hit a usage limit (github-actions[bot] reports it is excluded until 2026-08-08). I will retrigger /review once it is available again.

Copilot's two line comments are addressed below.

eldenmoon · 2026-08-05T03:29:48Z

run buildall

eldenmoon

LGTM

github-actions · 2026-08-05T03:31:19Z

PR approved by at least one committer and no changes requested.

github-actions · 2026-08-05T03:31:22Z

PR approved by anyone and no changes requested.

hello-stephen · 2026-08-05T05:06:49Z

FE UT Coverage Report

Increment line coverage 50.00% (1/2) 🎉
Increment coverage report
Complete coverage report

hulincup · 2026-08-05T05:26:05Z

Update on buildall: thanks @eldenmoon — the run buildall you sent at 03:29 did trigger the TeamCity pipeline (BE UT / Cloud UT / Coverage all green). However, COMPILE (DORIS_COMPILE) failed at 03:56, and FE UT is still pending.

I can't reach the TeamCity log directly (auth required). The FE change in this PR is a one-line logic tweak: hoisting isNereids && !isPointQuery into a useNereidsPrune local with an added || nereidsPrunedTabletIds.size() == 1 clause — no new types, signatures, or imports, so it shouldn't break compilation on its own. Could you take a look at the COMPILE log when you have a moment, or retrigger if it looks like a master flake? Happy to fix if it turns out to be on my side.

hulincup · 2026-08-05T05:35:51Z

run buildall

hulincup · 2026-08-05T06:20:57Z

COMPILE (DORIS_COMPILE) failed again on the rerun (buildId 1015987, 05:59), so it's not a flake. But I believe it's a BE/master compile issue, not this PR:

This PR only touches FE (OlapScanNode.java — one boolean local hoisted from the existing isNereids && !isPointQuery, passed to distributionPrune(...) whose 4th param is boolean) + a groovy regression test. Zero BE/C++ changes.
FE UT (Doris FE UT) passed on the previous run (05:06 SUCCESS) and is rerunning now.
Three other PRs that ran COMPILE in the same window today also failed ([fix](be) Pin be exec version in segment test #66465, branch-4.1: [Feature](multimodal_embed) Support multimodal(file) embed #66461, [fix](regression) Fetch streaming job metrics from master FE #66460).

I can't reach the TeamCity log (auth required). Could you check the COMPILE build log for buildId 1015987 and confirm whether it's a BE/master failure? If it is on the FE side I'll fix immediately, but the change is type-safe and FE UT passing strongly suggests FE compiles fine.

hulincup · 2026-08-05T06:35:45Z

Cross-checking today COMPILE results across PRs — 4 of 5 failed in the same window, including ones that only touch FE or a single BE test file:

PR	changes	COMPILE	performance
#66416 (this)	FE only + groovy test	FAILURE	FAILURE
#66465	1 BE test cpp	FAILURE	FAILURE
#66461	BE AI functions	FAILURE	SUCCESS
#66460	BE files	FAILURE	SUCCESS
#66462	(other)	SUCCESS	SUCCESS

This points to a systemic master/CI COMPILE issue today, not this PR (which has zero BE/C++ changes and FE UT passed on the prior run). FE UT is rerunning now and will confirm FE compiles. Could a committer check whether the COMPILE environment needs a reset? Happy to fix if the FE UT rerun surfaces anything.

hello-stephen · 2026-08-05T07:10:55Z

FE UT Coverage Report

Increment line coverage 50.00% (1/2) 🎉
Increment coverage report
Complete coverage report

eldenmoon · 2026-08-05T09:37:52Z

run buildall

hello-stephen · 2026-08-05T11:59:24Z

FE UT Coverage Report

Increment line coverage 50.00% (1/2) 🎉
Increment coverage report
Complete coverage report

hello-stephen · 2026-08-05T14:51:40Z

FE Regression Coverage Report

Increment line coverage 50.00% (1/2) 🎉
Increment coverage report
Complete coverage report

hulincup · 2026-08-06T01:08:34Z

The rerun (thanks @eldenmoon) turned most checks green: COMPILE, FE UT, vault_p0, External Regression, and the coverage reports all pass. Four regression jobs still fail, and I want to narrow down whether they are mine:

P0 Regression: 4 tests failed (5667 passed)
cloud_p0: 5 new failed
NonConcurrent: 2 new failed
performance: deploy step exit 1 (looks like an environment issue, not a test failure)

I cannot reach the TeamCity logs (auth required) to get the failing test names. The FE change only tightens tablet-prune path selection for nereids point queries already pruned to a single tablet, and FE UT passes, but the "new failed" tag makes me want to confirm. Could you share the failing test names so I can tell whether my new regression test or the prune change is involved, versus a master flake? Happy to fix immediately once I know which test.

eldenmoon · 2026-08-06T07:27:33Z

The rerun (thanks @eldenmoon) turned most checks green: COMPILE, FE UT, vault_p0, External Regression, and the coverage reports all pass. Four regression jobs still fail, and I want to narrow down whether they are mine:
P0 Regression: 4 tests failed (5667 passed)
cloud_p0: 5 new failed
NonConcurrent: 2 new failed
performance: deploy step exit 1 (looks like an environment issue, not a test failure)
I cannot reach the TeamCity logs (auth required) to get the failing test names. The FE change only tightens tablet-prune path selection for nereids point queries already pruned to a single tablet, and FE UT passes, but the "new failed" tag makes me want to confirm. Could you share the failing test names so I can tell whether my new regression test or the prune change is involved, versus a master flake? Happy to fix immediately once I know which test.

you can "Log in as guest"

In addKeyTuples, columnExpr.get(column.getName()) could return null when a key column has no matching literal conjunct on the scan node (e.g. a nereids slot columnName that does not match the base schema column name). The null literalExpr then fell through to ExprToThriftVisitor.treeToThrift and threw NullPointerException on expr.getType(), masking the root cause. Throw a diagnostic TException naming the unmatched key column and the available conjunct columns instead, so the next run reveals the exact column-name mismatch.

hulincup · 2026-08-07T01:58:55Z

Thanks — logged in as guest and pulled the failing tests. Triaging:

My new test_point_query_list_partition fails in all three regression builds. The explain { contains "SHORT-CIRCUIT" } step passes, but the actual SELECT throws NullPointerException: Cannot invoke "Expr.getType()" because "expr" is null.

Root-cause trace (static): the NPE is thrown at ExprToThriftVisitor:114 (msg.type = expr.getType(), param name expr matches the NPE), called from PointQueryExecutor.addKeyTuples:237treeToThrift(literalExpr) where literalExpr is null — returned by columnExpr.get(column.getName()) at line 219 when a key column name has no matching entry in the conjunct map built at lines 207-213 from scanNode.getConjuncts() slot column names.

My useNereidsPrune change lets the direct point query pass the single-tablet checkState (where the original IllegalStateException was thrown) and reach addKeyTuples, surfacing a pre-existing null-handling gap. distributionPrune itself doesn't touch conjuncts, only tablet selection.

I've pushed a defensive check (commit 7e5ec29) that throws a diagnostic TException — naming the unmatched key column and the available conjunct columns — instead of the NPE, so the next run reveals the exact column-name mismatch. I still need to confirm why the conjunct slot columnName doesn't match the base schema column name on this LIST-partitioned table, then fix that.

Existing point_query_p0 tests fail differently — test_point_query_partition / _ck throw IllegalStateException: Check tag 'point_select' failed at the prepared-statement qe_point_select step, a path I explicitly did not change. Likely master flakes; will confirm against master.

The rest are unrelated — search_score_cache, compaction, eager_agg, eliminate_inner, temp_table, multi_leading, mow_compact, performance (deploy step). Pre-existing in their own areas.

eldenmoon · 2026-08-07T03:33:04Z

/review

github-actions · 2026-08-07T03:34:45Z

Codex automated review failed and did not complete.

Error: All Codex review accounts are usage-limited; earliest retry is 2026-08-08T03:32:00Z.
Workflow run: https://github.com/apache/doris/actions/runs/31144692360

Please trigger /review again after that time.

hulincup · 2026-08-07T05:40:12Z

run buildall

hello-stephen · 2026-08-07T06:08:57Z

TPC-H: Total hot run time: 28664 ms

machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
scripts: https://github.com/apache/doris/tree/master/tools/tpch-tools
Tpch sf100 test result on commit a7ac664989a7dc7a0509cb4335ecded8c3b99041, data reload: false
------ Round 1 ----------------------------------
============================================
q1	17747	4041	3960	3960
q2	1983	315	196	196
q3	10327	1356	792	792
q4	4680	468	330	330
q5	7504	846	552	552
q6	179	174	136	136
q7	756	810	598	598
q8	9308	1556	1487	1487
q9	5522	4092	4015	4015
q10	6725	1611	1346	1346
q11	498	372	318	318
q12	714	565	461	461
q13	18103	3160	2733	2733
q14	254	265	239	239
q15	q16	723	725	654	654
q17	986	982	1068	982
q18	6491	5579	5533	5533
q19	1168	1191	1085	1085
q20	778	694	543	543
q21	5509	2629	2406	2406
q22	428	354	298	298
Total cold run time: 100383 ms
Total hot run time: 28664 ms
----- Round 2, with runtime_filter_mode=off -----
============================================
q1	4270	4192	4184	4184
q2	271	326	208	208
q3	4506	4880	4321	4321
q4	2169	2254	1396	1396
q5	4221	4051	4121	4051
q6	227	174	127	127
q7	1683	1585	1426	1426
q8	2157	2354	2095	2095
q9	7241	7184	7288	7184
q10	4321	4293	3876	3876
q11	571	395	388	388
q12	701	718	508	508
q13	3166	3437	3046	3046
q14	295	302	278	278
q15	q16	682	734	686	686
q17	1331	1287	1321	1287
q18	12204	11110	11741	11110
q19	1155	1149	1136	1136
q20	2229	2221	1923	1923
q21	5598	4842	4769	4769
q22	536	453	399	399
Total cold run time: 59534 ms
Total hot run time: 54398 ms

hello-stephen · 2026-08-07T06:19:11Z

TPC-DS: Total hot run time: 158600 ms

machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
scripts: https://github.com/apache/doris/tree/master/tools/tpcds-tools
TPC-DS sf100 test result on commit a7ac664989a7dc7a0509cb4335ecded8c3b99041, data reload: false
query5	4311	590	454	454
query6	448	218	209	209
query7	4943	581	345	345
query8	316	156	152	152
query9	8762	4065	4008	4008
query10	509	385	332	332
query11	5823	2165	2021	2021
query12	155	97	96	96
query13	1266	582	437	437
query14	6115	4290	4020	4020
query14_1	3787	3783	3776	3776
query15	197	191	172	172
query16	969	453	435	435
query17	923	701	530	530
query18	2412	465	346	346
query19	202	191	147	147
query20	108	103	101	101
query21	230	161	134	134
query22	12953	13118	12828	12828
query23	15682	14992	14561	14561
query23_1	14701	14666	14763	14666
query24	7525	1713	1263	1263
query24_1	1257	1246	1242	1242
query25	598	418	350	350
query26	1315	379	218	218
query27	2581	625	381	381
query28	4567	2027	2026	2026
query29	1084	587	479	479
query30	347	267	222	222
query31	1176	1115	1046	1046
query32	104	66	61	61
query33	504	308	243	243
query34	1185	1163	654	654
query35	731	751	644	644
query36	782	777	684	684
query37	156	115	95	95
query38	1836	1762	1680	1680
query39	805	821	800	800
query39_1	803	778	793	778
query40	255	165	147	147
query41	65	88	64	64
query42	96	96	88	88
query43	316	321	278	278
query44	1422	782	797	782
query45	195	173	172	172
query46	1087	1183	751	751
query47	1563	1569	1438	1438
query48	406	414	282	282
query49	584	410	287	287
query50	1109	434	369	369
query51	10851	10603	10611	10603
query52	86	89	75	75
query53	263	266	204	204
query54	271	227	212	212
query55	74	71	66	66
query56	300	283	271	271
query57	1029	990	970	970
query58	270	251	259	251
query59	1601	1615	1352	1352
query60	333	274	255	255
query61	155	146	150	146
query62	406	316	271	271
query63	226	195	200	195
query64	2841	1062	945	945
query65	3854	3801	3793	3793
query66	1848	498	380	380
query67	20030	19972	19900	19900
query68	3204	1492	1055	1055
query69	416	311	271	271
query70	909	797	755	755
query71	400	355	305	305
query72	3233	2816	2339	2339
query73	822	761	436	436
query74	4622	4493	4312	4312
query75	2363	2342	1992	1992
query76	2306	1214	764	764
query77	339	364	274	274
query78	11106	11039	10726	10726
query79	1371	1173	766	766
query80	1244	547	472	472
query81	535	316	285	285
query82	656	172	145	145
query83	373	325	294	294
query84	317	165	132	132
query85	963	610	509	509
query86	403	234	229	229
query87	1983	1959	1859	1859
query88	3733	2793	2779	2779
query89	395	321	283	283
query90	1867	200	195	195
query91	202	188	168	168
query92	64	59	56	56
query93	1751	1540	950	950
query94	701	368	314	314
query95	811	583	483	483
query96	1068	757	329	329
query97	2446	2452	2314	2314
query98	201	192	182	182
query99	769	754	616	616
Total cold run time: 245489 ms
Total hot run time: 158600 ms

hello-stephen · 2026-08-07T06:23:57Z

ClickBench: Total hot run time: 23.87 s

machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
scripts: https://github.com/apache/doris/tree/master/tools/clickbench-tools
ClickBench test result on commit a7ac664989a7dc7a0509cb4335ecded8c3b99041, data reload: false
query1	0.00	0.00	0.00
query2	0.10	0.05	0.05
query3	0.25	0.13	0.13
query4	1.60	0.14	0.14
query5	0.24	0.21	0.22
query6	1.15	0.83	0.84
query7	0.04	0.00	0.00
query8	0.05	0.03	0.04
query9	0.38	0.30	0.30
query10	0.54	0.54	0.54
query11	0.20	0.14	0.14
query12	0.18	0.14	0.14
query13	0.45	0.46	0.45
query14	1.01	0.99	0.99
query15	0.63	0.58	0.61
query16	0.30	0.33	0.32
query17	1.08	1.13	1.08
query18	0.20	0.20	0.20
query19	2.01	1.90	1.92
query20	0.01	0.01	0.01
query21	15.43	0.19	0.14
query22	5.02	0.05	0.05
query23	16.12	0.30	0.12
query24	3.03	0.44	0.33
query25	0.11	0.04	0.04
query26	0.77	0.21	0.15
query27	0.03	0.03	0.03
query28	3.43	0.78	0.34
query29	12.50	4.12	3.24
query30	0.27	0.16	0.15
query31	2.77	0.56	0.31
query32	3.23	0.59	0.49
query33	3.24	3.16	3.18
query34	15.64	3.95	3.26
query35	3.24	3.22	3.22
query36	0.54	0.43	0.46
query37	0.09	0.07	0.06
query38	0.05	0.04	0.04
query39	0.04	0.03	0.03
query40	0.16	0.15	0.15
query41	0.08	0.04	0.03
query42	0.04	0.03	0.03
query43	0.04	0.04	0.03
Total cold run time: 96.29 s
Total hot run time: 23.87 s

hello-stephen · 2026-08-07T08:35:05Z

FE Regression Coverage Report

Increment line coverage 5.19% (4/77) 🎉
Increment coverage report
Complete coverage report

hulincup · 2026-08-19T01:34:10Z

run buildall

bzhang-obsec · 2026-08-19T05:57:48Z

Hi @hulincup, thank you for working on this!
On my fork I have a different fix. I'm sending it out just to get used to how this CI works. Please ignore that one.

morrySnow changed the title ~~[fix](planner) fix point query IllegalStateException on LIST partition~~[fix](point query) fix point query IllegalStateException on LIST partitionAug 5, 2026

eldenmoon requested a lite review from Copilot August 5, 2026 02:54

Copilotstarted reviewing on behalf of eldenmoon August 5, 2026 02:54 View session

CopilotAI reviewed Aug 5, 2026
View reviewed changes

eldenmoon previously approved these changes Aug 5, 2026
View reviewed changes

github-actionsBot added the approved Indicates a PR has been approved by one committer. label Aug 5, 2026

github-actionsBot added the reviewed label Aug 5, 2026

Merge branch 'master' into fix/point-query-list-partition
3c8ab6d

hulincup dismissed eldenmoon’s stale review via 7e5ec29August 7, 2026 01:26

github-actionsBot removed the approved Indicates a PR has been approved by one committer. label Aug 7, 2026

Merge branch 'master' into fix/point-query-list-partition
a7ac664

Merge branch 'master' into fix/point-query-list-partition
e3a0324

hulincup requested review from 924060929 and morrySnow as code owners August 18, 2026 10:01

hulincup added 2 commits August 20, 2026 13:39

Merge branch 'master' into fix/point-query-list-partition
3772136

Merge branch 'master' into fix/point-query-list-partition
7c2f3f5

		def explain = sql """EXPLAIN SELECT * FROM ${tableName} WHERE pk = 'abcd' AND _id = 1"""
		assertTrue(explain.toString().contains("SHORT-CIRCUIT"))

Uh oh!

Conversation

hulincup commented Aug 4, 2026

Motivation

Root cause

Change

Files

Verification

Test plan

Uh oh!

hello-stephen commented Aug 4, 2026

Uh oh!

hulincup commented Aug 4, 2026

Uh oh!

eldenmoon commented Aug 5, 2026

Uh oh!

eldenmoon commented Aug 5, 2026

Uh oh!

github-actionsBot commented Aug 5, 2026

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

hulincupAug 5, 2026

Choose a reason for hiding this comment

Uh oh!

hulincupAug 5, 2026

Choose a reason for hiding this comment

Uh oh!

hulincup commented Aug 5, 2026

Uh oh!

eldenmoon commented Aug 5, 2026

Uh oh!

eldenmoon left a comment

Choose a reason for hiding this comment

Uh oh!

github-actionsBot commented Aug 5, 2026

Uh oh!

github-actionsBot commented Aug 5, 2026

Uh oh!

hello-stephen commented Aug 5, 2026

FE UT Coverage Report

Uh oh!

hulincup commented Aug 5, 2026

Uh oh!

hulincup commented Aug 5, 2026

Uh oh!

hulincup commented Aug 5, 2026

Uh oh!

hulincup commented Aug 5, 2026

Uh oh!

hello-stephen commented Aug 5, 2026

FE UT Coverage Report

Uh oh!

eldenmoon commented Aug 5, 2026

Uh oh!

hello-stephen commented Aug 5, 2026

FE UT Coverage Report

Uh oh!

hello-stephen commented Aug 5, 2026

FE Regression Coverage Report

Uh oh!

hulincup commented Aug 6, 2026

Uh oh!

eldenmoon commented Aug 6, 2026

Uh oh!

hulincup commented Aug 7, 2026

Uh oh!

eldenmoon commented Aug 7, 2026

Uh oh!

github-actionsBot commented Aug 7, 2026

Uh oh!

hulincup commented Aug 7, 2026

Uh oh!

hello-stephen commented Aug 7, 2026

Uh oh!

hello-stephen commented Aug 7, 2026

Uh oh!

bzhang-obsec commented Aug 19, 2026•
edited
Loading