ryankert01 opened a new issue, #765: URL: https://github.com/apache/mahout/issues/765
### **Description** There is currently an inconsistency in how our system handles `null` values depending on the execution mode. To ensure predictable behavior and data integrity, we should align these strategies. ### **Current Behavior** * **Batch Mode:** Null values are automatically coerced/set to `0`. * **Streaming Mode:** Null values trigger a runtime error. ### **Proposed Change** We need to decide on a unified strategy for handling `null` values across both modes. Potential directions include: 1. **Strict Error Handling:** Both modes return an error to prevent silent data corruption. 2. **Default Coercion:** Both modes default to `0` (or a type-appropriate default). 3. **Configurable Policy:** Allow users to define the `on_null` behavior (e.g., `ignore`, `fill_zero`, or `raise_error`). ### **Context** https://github.com/apache/mahout/pull/753#discussion_r2650061909 ### **To-Do / Discussion Points** * [ ] Research performance implications of adding null-checks in the streaming hot path. * [ ] Determine if "Default to 0" is safe for all supported data types. * [ ] Reach a consensus on the unified default behavior. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
