Skip to content
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,7 @@ class S3DatasourceBackfillOperator<R : Any, P : Any>(
require(fileKeys.isNotEmpty()) {
"No files found for bucket:${backfill.getBucket(config)} prefix:$pathPrefix. At least one file must exist."
}
// We limit to 100 files since each file is run in parallel.
require(fileKeys.size <= 100) {
"Listing files matching the prefix contains ${fileKeys.size} which is more than 100 files. " +
"Check your prefix. First 3 file keys ${fileKeys.slice(0..2)}"
Expand Down
6 changes: 6 additions & 0 deletions client/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,3 +2,9 @@

Contains the general, public client definitions for Backfila so clients and the service can
communicate. Never use this directly, instead use the specialized clients.

Java/Kotlin
Client - public API for communicating with Backfila, Customers depend on this for general backfila features (Parameters, dry run, logging)
Client-<service framework> - provides the base interaction with backfila for your service framework(Logging setup, client service, registration on startup). You install one of these in your real implementation. backfila-embedded is your test implementation.
Client-base - base functionality that all downstream datasource clients need (implementions of common features, parameters, Operator caching). Provides and SPI for those clients to satisfy in order to get this base functionality. This is private. Customers cannot depend on this. Only datasource clients depend on this.
client-<specific datasouce> - The specific datasouce Backfila implementation. This is where the ergonomics of working with your particular datasource exist