This website uses cookies to ensure you get the best experience.
Learn more.
A preprocessing change alters feature order but the production estimator remains unchanged. Which deployment practice best prevents this class of failure?
Published
- Deploy preprocessing independently without any compatibility checks.
- Sort feature names alphabetically at serving regardless of training order.
- Version and test the compatible preprocessing and estimator artifacts as one serving contract.
- Increase endpoint memory as the only correction.
Comments — 0
Sign in to comment