[BUG] Removing rewrite for derived fields

[harshavamsi]

Describe the bug

In #19296, i commented out the rewrite for derived fields. Rewriting certain queries that are wrapped in the derived field type now have issues at the lucene layer. Range queries in lucene now check pointvalues at rewrite time and since derived fields are not indexed, the rewrite returns a MatchNoDocsQuery which is incorrect.

We need to figure out a more concrete rewriting pattern for derived fields. Using this issue to track discussions.

Related component

Search

To Reproduce

Running a rewrite on a derived field causes issues while doing range queries

Expected behavior

Figure out new ways to rewrite derived field queries

Additional Details

Plugins
Please list all plugins currently enabled.

Screenshots
If applicable, add screenshots to help explain your problem.

Host/Environment (please complete the following information):

• OS: [e.g. iOS]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[harshavamsi]

@rishabhmaurya @jainankitk could use ideas here

[rishabhmaurya]

@harshavamsi I think we can just disable rewrites for range query by passing a flag here

OpenSearch/server/src/main/java/org/opensearch/index/mapper/DerivedFieldType.java

Line 230 in 987f4fa

return new DerivedFieldQuery(

I do not see much use of rewrites anyways for range queries used in derived fields.

[jainankitk]

@harshavamsi I think we can just disable rewrites for range query by passing a flag here

I do not see much use of rewrites anyways for range queries used in derived fields.

Thanks @rishabhmaurya. That seems reasonable to me, instead of disabling rewrites completely!