You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem?
OpenSearch raw response output is output using the JSON format in #1317, but what is not supported are the in-memory calculations. In the legacy engine, this was supported using the painless script calls - but painless is not supported in the new engine.
What solution would you like?
Inject in-memory calls into the raw-JSON OpenSearch response in a similar format that may be used as the legacy output - where in-memory calculations are returned for each row in the fields object, and all other row objects are returned directly from OpenSearch response.
For example, we get both the raw int0 response from OpenSearch in _source, as well as the calculated int0 + 1 column output in fields for each row. null is returned for invalid results (in this example).
Do we need to include the schema object as well for each of the fields values? It is available.
What alternatives have you considered?
Returning painless script calls are not supported in V2, and adding this feature support just for JSON output is overly complex.
Do you have any additional context?
None
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
OpenSearch raw response output is output using the
JSON
format in #1317, but what is not supported are the in-memory calculations. In the legacy engine, this was supported using thepainless
script calls - butpainless
is not supported in the new engine.What solution would you like?
Inject in-memory calls into the raw-JSON OpenSearch response in a similar format that may be used as the legacy output - where in-memory calculations are returned for each row in the
fields
object, and all other row objects are returned directly from OpenSearch response.For example, we get both the raw
int0
response from OpenSearch in_source
, as well as the calculatedint0 + 1
column output infields
for each row.null
is returned for invalid results (in this example).Do we need to include the
schema
object as well for each of thefields
values? It is available.What alternatives have you considered?
Returning painless script calls are not supported in V2, and adding this feature support just for JSON output is overly complex.
Do you have any additional context?
None
The text was updated successfully, but these errors were encountered: