Add test cases for dynamic_templates mappings

[rursprung]

Description

alternative version of #443 from @reta which shows the failing test. feel free to take that commit over into the original PR and close this PR here instead.

Note that one of the test cases currently fails and requires opensearch-project/opensearch-java#1513 to be resolved first, thus it has been disabled for the OSC client.

Issues Resolved

n/a

Check List

• New functionality includes testing.
  • All tests pass (the whole point is to show a failing test; though it's disabled, so technically it passes CI)
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[rursprung]

remove this to see the test failing

[reta]

@rursprung this is expected behavior, the values with dots are not accepted to object fields (but to nested or flattened fields), changes goes back to https://www.elastic.co/guide/en/elasticsearch/reference/2.4/dots-in-names.html

[rursprung]

@rursprung this is expected behavior, the values with dots are not accepted to object fields (but to nested or flattened fields), changes goes back to https://www.elastic.co/guide/en/elasticsearch/reference/2.4/dots-in-names.html

the whole goal here is to have this split up - i.e. indexing A.B should create a field B nested within A; this is also what the documentation which you linked to suggests? and with the old client this worked perfectly fine (see also that the test succeeds with the ORHLC).

[reta]

the whole goal here is to have this split up - i.e. indexing A.B should create a field B nested within A; this is also what the documentation which you linked to suggests? and with the old client this worked perfectly fine (see also that the test succeeds with the ORHLC).

OK, so it is really very tricky, I think the case I run into is:

// First doc

	"names" : {
		"a" : "c"
	}
}

// Second doc

	"names" : {
		"a.b" : "c"
	}
}

So this does not work obviously. To your point, the general exception that dots are expanded into properties for object types is correct, but the presence of "type": "object" (dynamic template) in case of OpenSearch Java client does break the expecations

[rursprung]

// First doc

this should be:

	"names" : {
		"a" : {
			"b" : "c"
		}
	}
}

So this does not work obviously. To your point, the general exception that dots are expanded into properties for object types is correct, but the presence of "type": "object" (dynamic template) in case of OpenSearch Java client does break the expecations

exactly, that's the problem and why i've reported it to opensearch-java as discussed: opensearch-project/opensearch-java#1513

but i'm not familiar at all with the code generation going on there, so i don't know how to get this fixed there (i guess either the source from which it is being generated is wrong or the generator has a bug?)

[reta]

@rursprung closing this one, #443 has a reproducer now, thank you