Indexer not paying attention to updated DEVELOPMENT status schema
- We installed a DEVELOPMENT status schema with an incorrect x-osdu-indexing hint. (It was at the wrong level in the schema.). We indexed some data with this incorrect schema, and the affected field was not queryable.
- We then fixed the schema (moved only the x-osdu-indexing extensions) and reinstalled it with the PUT endpoint, but with the same version number. We confirmed by retrieving the schema that the changes had been committed to the schema service.
- We deleted the records created with the prior version and created new records.
- The field in question was still not queryable.
- We installed the schema again, but bumped the SchemaVersionPatch value by 1.
- We deleted the records created with the second version of the schema and created new records with updated "kind" values.
- This time, the field in question was queryable.
In the past, we've been able to install updated DEVELOPMENT status schema with the same version number and the indexer would appear to take notice. Is the indexer not noticing changes limited to x-osdu-indexing extensions, and using a cached version of the prior schema content?