update schema or FAQ to note client_region code designations
critzo opened this issue · comments
Since the re-write of the ETL pipeline and annotation service in 2017, the field connection_spec.client_geoloation.region has a variety of content from two different standards. Make a note of this in the schema page and/or the FAQ.
Gardener has since reprocessed old data so this issue is no longer needed.