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
Get Updates on the Splunk Community!

Unlock Database Monitoring with Splunk Observability Cloud

  In today’s fast-paced digital landscape, even minor database slowdowns can disrupt user experiences and ...

Purpose in Action: How Splunk Is Helping Power an Inclusive Future for All

At Cisco, purpose isn’t a tagline—it’s a commitment. Cisco’s FY25 Purpose Report outlines how the company is ...

[Upcoming Webinar] Demo Day: Transforming IT Operations with Splunk

Join us for a live Demo Day at the Cisco Store on January 21st 10:00am - 11:00am PST In the fast-paced world ...