Splunk Search

Join turns off predicate pushdown optimization

aasfga
New Member

Hi,
I have problem with optimizer. It doesn't make pushdown optimization when I'm using join. I have event dataset with some eval fields and regex fields that I'm searching from. My query looks like this:

| from datamodel:"My cool ED"
| search index=A host=B <- important filter
...
and this works fine because Splunk optimizer sees that it can move "important filter to the beginning. After optimize it looks like this:

search (index=A host=B) " my cool ED query"
...

However when I add join after search:
| from datamodel:"My cool ED"
| search index=A host=B <- important filter
| join key [ subsearch from other datamodel ]
...

my important filter is not optimized and stays where it is. Can I force optimizer so it moves index filter to the beginning of optimized query?

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...