Skip to content

import_big_file_data: lake imports answer a job map on the current backend - #10

Merged
nikolaos-paximadakis-eea merged 1 commit into
mainfrom
docs/lake-import-job-map
Nov 21, 2026
Merged

nikolaos-paximadakis-eea merged 1 commit into
mainfrom
docs/lake-import-job-map

Conversation

@nikolaos-paximadakis-eea

Copy link
Copy Markdown
Collaborator

Checked live on the sandbox with a custodian ApiKey: a two-row import into a data-lake test dataset answered {jobId, pollingUrl} in about a second and the job reached FINISHED in about 20 s; an export showed the rows. The backend's MasterOneVersion branch registers a job for lake imports too (DatasetControllerImpl#importBigFileData). The docstring said lake imports answer an empty body; that is the older MasterDataLakes behaviour, still handled (returns {}). Docstring (sync + async), CHANGELOG and the generated reference page updated.

No code change.

@nikolaos-paximadakis-eea
nikolaos-paximadakis-eea merged commit 1b045fc into main Nov 21, 2026
6 checks passed
@nikolaos-paximadakis-eea
nikolaos-paximadakis-eea deleted the docs/lake-import-job-map branch November 21, 2026 22:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant