Hey! I see that the Airbyte Normalization stage ...
# connector-development
j
Hey! I see that the Airbyte Normalization stage ingests these fields into the end table to debug downstream issues in the DWH.
_airbyte_ab_id,_airbyte_emitted_at,_airbyte_normalized_at,
_airbyte_survey_questions_hashid
I will like to know if it is possible to add another field
_airbyte_connector_version
? I think it is super useful API schemas change over time, this field will help downstream modeling when API schemas changed, without a need of having two different tables or el jobs
h
Hey sounds like a plan can you create an issue around this and add the details so that team can track and comment over it
j
Sure! Sorry it take ages but here it is the issue https://github.com/airbytehq/airbyte/issues/11345