yeshvantbhavnasi opened a new issue, #28219:
URL: https://github.com/apache/beam/issues/28219
### What happened?
```
BigQueryIO.Write<Row> batchWrite =
rowWrite
.withMethod(BigQueryIO.Write.Method.FILE_LOADS)
.withTriggeringFrequency(Duration.standardMinutes(fileLoadSpecOptional.get().writeTriggerFrequency))
.withAutoSharding()
.withExtendedErrorInfo()
.withMaxRetryJobs(fileLoadSpecOptional.get().withJobRetryCount)
.withWriteTempDataset(TMP_TABLE_DATASET)
.withCustomGcsTempLocation(ValueProvider.StaticValueProvider.of(fileLoadSpecOptional.get().stagingBucket));
```
Have following code to setup file_load operation for Dataflow streaming jobs
using GCS and File_notification based ingestion into BigQuery
- It creates a JobId for new file after few minues and load data into Live
table with example jobId
`beam_bq_job_LOAD_defaultnetworkvpcflowlogslive_e78561b1b6e147e7abafe83b9314c7f1_41dd2dbb7ce5b6e717e5aadb4244b4e0_00001_00000-0`
but every new set of files are having the `1` partition and c.pane.index to
be `0` causing the same job_id and ignore file writes
See the screenshot for different timestamp we have the same job_id ignoring
inserts
<img width="1325" alt="image"
src="https://github.com/apache/beam/assets/20260478/8ae6aaf0-5870-417b-9657-e7606fd04e47";>
### Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
### Issue Components
- [ ] Component: Python SDK
- [X] Component: Java SDK
- [ ] Component: Go SDK
- [ ] Component: Typescript SDK
- [ ] Component: IO connector
- [ ] Component: Beam examples
- [ ] Component: Beam playground
- [ ] Component: Beam katas
- [ ] Component: Website
- [ ] Component: Spark Runner
- [ ] Component: Flink Runner
- [ ] Component: Samza Runner
- [ ] Component: Twister2 Runner
- [ ] Component: Hazelcast Jet Runner
- [ ] Component: Google Cloud Dataflow Runner
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
