Splunk Search

Join 2 indexes

jwgiblin3
Engager

I have 2 indexes that I am joining and I am getting different results based on whether I start the search with one index vs the other. The join is a one to many relationship

Indexes
- filemeta (1)
- fileacl (*)

Query 1 - 1 Result
index="filemeta" Path="\\server\testshare" | join "Path" [ search index="fileacl" ]
Query 2 - 6 results
index="fileacl" Path="\\server\testshare" | join "Path" [ search index="filemeta" ]

Am I missing something on Query 1 in order to see all the results from the fileacl index?

Tags (2)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

As you've discovered, the order of a join is significant. The type of join also makes a difference. The default type is inner which means the results do not include events from the main (1st) search that have no matches in the subsearch (2nd). Events that match on both sides are always included.

---
If this reply helps you, Karma would be appreciated.

jwgiblin3
Engager

Thanks for your reply. I do understand inner joins. What I am not clear is why it only included 1 event when there are many events for that path

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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...