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
Current Java API doesn't contain definition of 'mapping' object within org.opensearch.client.opensearch.indices.IndexSettings and doesn't allow a non-declared json field to be added to the payload
What solution would you like?
Either add mapping.totalFields.limit properties chain to IndexSettings object or consider allowing setting an arbitrary json property on any level of any API request objects
What alternatives have you considered?
Using high-level rest client as a workaround
Do you have any additional context?
Nope
The text was updated successfully, but these errors were encountered:
Both! I think that arbitrary fields support on all the levels makes some sense because it will provide a workaround quickly, but that also means that one could theoretically add fields that don't exist. I would fix any missing field as 1 PR and then independently propose an arbitrary field solution and we can discuss that on its own merits. WDYT?
wbeckler
changed the title
[FEATURE] java api doesn't allow setting index.mapping.total_fields.limit
[FEATURE] allow setting an arbitrary json property on any level of any API request objects
Oct 3, 2023
Is your feature request related to a problem?
Current Java API doesn't contain definition of 'mapping' object within org.opensearch.client.opensearch.indices.IndexSettings and doesn't allow a non-declared json field to be added to the payload
What solution would you like?
Either add
mapping.totalFields.limit
properties chain to IndexSettings object or consider allowing setting an arbitrary json property on any level of any API request objectsWhat alternatives have you considered?
Using high-level rest client as a workaround
Do you have any additional context?
Nope
The text was updated successfully, but these errors were encountered: