RK
06/03/2021, 4:36 PMJackie
06/03/2021, 4:55 PMRK
06/03/2021, 5:27 PMRK
06/03/2021, 5:37 PMRK
06/03/2021, 5:38 PMJackie
06/03/2021, 5:39 PMRK
06/03/2021, 5:43 PMRK
06/03/2021, 5:44 PMRK
06/03/2021, 5:48 PMJackie
06/03/2021, 5:49 PMpushType
as REFRESH
?RK
06/03/2021, 5:53 PMRK
06/03/2021, 5:54 PMRK
06/03/2021, 5:56 PMJackie
06/03/2021, 6:07 PMingestionConfig
?Jackie
06/03/2021, 6:07 PM"ingestionConfig": {
...,
"batchIngestionConfig": {
"segmentIngestionType": "APPEND",
"segmentIngestionFrequency": "DAILY"
}
}
RK
06/03/2021, 6:11 PMJackie
06/03/2021, 6:17 PMKen Krugler
06/03/2021, 6:48 PMexecutionFrameworkSpec.yaml
file? You typically need a section like:
segmentNameGeneratorSpec:
# type: Current supported types are 'simple' and 'normalizedDate'.
type: normalizedDate
configs:
segment.name.prefix: 'ads_batch'
So that segment names vary by date. If you would wind up with multiple results that have the same name (by date) you can add exclude.sequence.id: false
to the configs
section.RK
06/04/2021, 3:58 AMKen Krugler
06/04/2021, 1:51 PMRK
06/04/2021, 1:55 PMRK
06/04/2021, 1:56 PMexecutionFrameworkSpec.yaml
file? You typically need a section like:
segmentNameGeneratorSpec:
# type: Current supported types are 'simple' and 'normalizedDate'.
type: normalizedDate
configs:
segment.name.prefix: 'ads_batch'
So that segment names vary by date. If you would wind up with multiple results that have the same name (by date) you can add exclude.sequence.id: false
to the configs
section. This was already there in file.