Tanu Sharma
Tanu Sharma
.take-issue
@ruslan-yuldashev-sxp , when using --useStorageWriteApi=true , we need to manually add the ```_metadata_big_query_commit_timestamp``` column and set ```CURRENT_TIMESTAMP``` as its default value if we need the column. So, if you have...
@oulin-coder , till apache-beam version 2.57.0, we were setting metadataTable in pipeline options [here](https://github.com/apache/beam/blob/release-2.57.0/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/spanner/SpannerIO.java#L1742) but in 2.58.0 version, this setting was removed from [here](https://github.com/apache/beam/blob/release-2.58.0/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/spanner/SpannerIO.java#L1745) with [PR](https://github.com/apache/beam/pull/31412) with reason that setting...
@an2x can you please review this PR ?
Run Java_GCP_IO_Direct PreCommit
you can use timestamp_attribute: None, then it uses message publishing time as the timestamp. Is that not sufficient for your use case ?
As per my understanding, "I read this to say that there must be a field inside my incoming Pub/Sub message attributes map that will be used as the element timestamp."...