Skip to content

Fall back to un-optimized filter chain for unknown filters#1284

Open
hs-lsong wants to merge 1 commit intomasterfrom
local-dt-test
Open

Fall back to un-optimized filter chain for unknown filters#1284
hs-lsong wants to merge 1 commit intomasterfrom
local-dt-test

Conversation

@hs-lsong
Copy link
Collaborator

@hs-lsong hs-lsong commented Feb 5, 2026

Fall back to un-optimized filter chain for unknown filters

Summary

  • When AstFilterChain optimization is enabled and a filter chain contains an unknown filter (e.g. local_dt), fall back to the standard nested AstMethod evaluation at parse time
  • Previously, the optimized path would report an "Unknown filter" error and return null, aborting the entire chain. Now it builds the un-optimized AST instead, matching the behavior of the non-optimized path

Why

The optimized AstFilterChain handles unknown filters differently from the standard EL evaluation path. For example, module | local_dt|unixtimestamp | pprint | md5 would produce no output with the optimization enabled, but works (with a
warning) in the un-optimized path. The optimization should be transparent — falling back when it can't handle a filter ensures parity.

When AstFilterChain optimization is enabled and a filter chain contains
an unknown filter (e.g. local_dt), fall back to the standard nested
AstMethod evaluation at parse time instead of failing with an
"Unknown filter" error and returning null.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
@hs-lsong hs-lsong marked this pull request as ready for review February 5, 2026 21:45
@hs-lsong hs-lsong requested a review from jasmith-hs February 5, 2026 21:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant