Simplify & Document Batch Size Limitations
Generally, batch size should remain configurable per-kind.
However, for specific "custom" geometryLocation or spatialSource ingestion workflows, batch sizes need to be smaller to avoid cursor expiration conflicts due to extended processing times.
How should the Transformer enforce batch size limitations?
- Always enforce smaller, pre-defined batch sizes for "custom" ingestion workflows
- How can we capture these limitations in docs and make it obvious to user in Admin UI or those consuming API?
- Allow override of any and all batch size configurations, warning user of risk when overriding the default.
We could do a combination of 1 and 2. Thoughts from the team?
Edited by Levi Remington