fix: dont enrich if non empty keys are not same

[nityanandagohain]

Fixes #4901

Issue explaination

If there are two fields

• myattr (type=tag, datatype=string)
• myattr (type=resource, datatype=string)

We added a change recently where we forcefully try to enrich all attributes

so if user is searching for myattr (type=resource, datatype=string) then it might get replaced with * myattr (type=tag, datatype=string)

This PR fixes it.

though there is no solution right now if in the query user enters myattr with no metadata, we don't know which one to choose for enriching the tag or the resource attribute.

[github-actions]

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

[srikanthccv]

though there is no solution right now if in the query user enters myattr with no metadata, we don't know which one to choose for enriching the tag or the resource attribute.

So what happens now?

so if user is searching for myattr (type=resource, datatype=string) then it might get replaced with * myattr (type=tag, datatype=string)

Did someone in production run into this issue? What attribute were they using?

[nityanandagohain]

So what happens now?

It's random right now, since the map is based on name whatever key remains is used for enrichment.

Did someone in production run into this issue? What attribute were they using?

Yes it was faced by an user, who had an old duplicate attribute in resource and due to this bug, even when the new attribute (with correct type and data type) was sent it was being replaced as we were forcefully enriching it.