Exclude Era date from common v1 dataset

[suhomud]

What

Era dates is not supported by all destinations. The era dates should be checked by connectors which supports it

How

Exclude Era date from common dataset. Add separate tests for era date with https://github.com/airbytehq/airbyte-internal-issues/issues/1253

Recommended reading order

1. x.java
2. y.python

🚨 User Impact 🚨

No Impact.

[github-actions]

Affected Connector Report

NOTE ⚠️ Changes in this PR affect the following connectors. Make sure to do the following as needed:

• Run integration tests
• Bump connector or module version
• Add changelog
• Publish the new version

✅ Sources (0)

Connector	Version	Changelog	Publish

• See "Actionable Items" below for how to resolve warnings and errors.

❌ Destinations (47)

Connector	Version	Changelog	Publish
destination-aws-datalake	0.1.1	✅	✅
destination-azure-blob-storage	0.1.6	✅	✅
destination-bigquery	1.2.9	✅	✅
destination-bigquery-denormalized	1.2.9	✅	✅
destination-cassandra	0.1.4	✅	✅
destination-clickhouse	0.2.1	✅	✅
destination-clickhouse-strict-encrypt	0.2.1	🔵 (ignored)	🔵 (ignored)
destination-csv	0.2.10	✅	✅
destination-databricks	0.3.1	✅	✅
destination-dev-null	0.2.7	🔵 (ignored)	🔵 (ignored)
destination-doris	0.1.0	✅	✅
destination-dynamodb	0.1.7	✅	✅
destination-e2e-test	0.2.4	✅	✅
destination-elasticsearch	0.1.6	✅	✅
destination-elasticsearch-strict-encrypt	0.1.6	🔵 (ignored)	🔵 (ignored)
destination-gcs	0.2.12	✅	✅
destination-iceberg	0.1.0	✅	✅
destination-jdbc	0.3.14	🔵 (ignored)	🔵 (ignored)
destination-kafka	0.1.10	✅	✅
destination-keen	0.2.4	✅	✅
destination-kinesis	0.1.5	✅	✅
destination-local-json	0.2.11	✅	✅
destination-mariadb-columnstore	0.1.7	✅	✅
destination-mongodb	0.1.9	✅	✅
destination-mongodb-strict-encrypt	0.1.9	🔵 (ignored)	🔵 (ignored)
destination-mqtt	0.1.3	✅	✅
destination-mssql	0.1.22	✅	✅
destination-mssql-strict-encrypt	0.1.22	🔵 (ignored)	🔵 (ignored)
destination-mysql	0.1.20	✅	✅
destination-mysql-strict-encrypt	❌ 0.1.21 (mismatch: 0.1.20)	🔵 (ignored)	🔵 (ignored)
destination-oracle	0.1.19	✅	✅
destination-oracle-strict-encrypt	0.1.19	🔵 (ignored)	🔵 (ignored)
destination-postgres	0.3.26	✅	✅
destination-postgres-strict-encrypt	0.3.26	🔵 (ignored)	🔵 (ignored)
destination-pubsub	0.2.0	✅	✅
destination-pulsar	0.1.3	✅	✅
destination-r2	0.1.0	✅	✅
destination-redis	0.1.4	✅	✅
destination-redpanda	0.1.0	✅	✅
destination-redshift	0.3.51	✅	✅
destination-rockset	0.1.4	✅	✅
destination-s3	0.3.18	✅	✅
destination-s3-glue	0.1.1	✅	✅
destination-scylla	0.1.3	✅	✅
destination-snowflake	0.4.40	✅	✅
destination-tidb	0.1.0	✅	✅
destination-yugabytedb	0.1.0	✅	✅

• See "Actionable Items" below for how to resolve warnings and errors.

✅ Other Modules (0)

Actionable Items

(click to expand)

Category	Status	Actionable Item
Version	❌ mismatch	The version of the connector is different from its normal variant. Please bump the version of the connector.
	⚠ doc not found	The connector does not seem to have a documentation file. This can be normal (e.g. basic connector like source-jdbc is not published or documented). Please double-check to make sure that it is not a bug.
Changelog	⚠ doc not found	The connector does not seem to have a documentation file. This can be normal (e.g. basic connector like source-jdbc is not published or documented). Please double-check to make sure that it is not a bug.
	❌ changelog missing	There is no chnagelog for the current version of the connector. If you are the author of the current version, please add a changelog.
Publish	⚠ not in seed	The connector is not in the seed file (e.g. source_definitions.yaml), so its publication status cannot be checked. This can be normal (e.g. some connectors are cloud-specific, and only listed in the cloud seed file). Please double-check to make sure that it is not a bug.
	❌ diff seed version	The connector exists in the seed file, but the latest version is not listed there. This usually means that the latest version is not published. Please use the /publish command to publish the latest version.

[suhomud]

/test connector=connectors/destination-s3

🕑 connectors/destination-s3 https://github.com/airbytehq/airbyte/actions/runs/3763311079
✅ connectors/destination-s3 https://github.com/airbytehq/airbyte/actions/runs/3763311079
No Python unittests run

Build Passed

Test summary info:

All Passed

[suhomud]

Checked destination-s3 tests since it used v1 datasets

[grishick]

If a connector does not support eras in dates and a source emits a data with an era - what is the expected behavior?

[suhomud]

If a connector does not support eras in dates and a source emits a data with an era - what is the expected behavior?

@grishick Currently it leads normalization failure. I expect that we need to solve the issue in a scope of handling "bad data" tickets.