Apache Flink StateFun 3.4.0-KZM-3.5 adds policy to handle bad Kafka records gracefully

·1 views

A long-standing flaw in Apache Stateful Functions caused an entire Flink job to crash and loop indefinitely whenever a single malformed Kafka record — such as one with a null key or a tombstone value — was encountered. Because Flink runs multiple pipelines as one unit, one bad record on one topic could take down unrelated workloads like order tracking, notifications, and billing. The new release, StateFun Actors 3.4.0-KZM-3.5, introduces an invalidRecordHandling configuration option at both the ingress and per-topic level, letting operators choose between skipping bad records with a log entry or halting the job with full record coordinates. The default behavior is now skip-with-log-and-metric rather than crash, with Prometheus-compatible counters and labels to alert on the specific producer and defect type. Teams relying on job restarts as a bad-data signal are advised to migrate their alerts to the new numInvalidRecordsSkipped metric, or explicitly set type: fail to preserve the previous strict behavior.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Developer Builds Privacy-First Browser Tools That Never Send User Data to Servers

A developer has built a collection of free online utilities called Giga Useful Tools, designed to process user data entirely within the browser without uploading it to any server. The project covers tools for file conversion, text manipulation, QR code generation, calculators, and developer utilities. By leveraging modern browser APIs such as File, Blob, and Canvas, the tools can handle tasks locally, eliminating the need for backend infrastructure. This approach offers multiple benefits: stronger privacy by default, faster processing due to reduced network overhead, and lower server costs. The developer notes that browser-based processing is not suitable for all tasks, particularly heavy computations, but argues it is the right default whenever a server is not strictly necessary.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

react-hook-lab Launches useFileSystem Hook for Direct Browser File Editing

The react-hook-lab library has released a new React hook called useFileSystem, designed to simplify direct file reading and writing in web applications. The hook wraps the browser's native File System Access API, eliminating the repetitive download-and-re-upload cycle common in web-based editors. It provides built-in state tracking across five stages — idle, picking, reading, saving, and error — along with standardized file metadata management and graceful error handling for user cancellations. Developers can use it to build tools such as log writers or markdown editors that save changes directly to a file on the user's local disk without triggering repeated download prompts. The hook is type-safe and declarative, aiming to reduce boilerplate code when managing file system interactions in React projects.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Use React Profiler to Find and Fix Slow Components

React applications can suffer from performance issues that are difficult to diagnose without proper tooling, making guesswork an unreliable approach. The React Profiler, available through React DevTools, allows developers to record interactions and inspect which components rendered and why. A key concept highlighted is that a React render does not always result in a DOM update, meaning not every rendered component is necessarily causing visible slowness. Profiling helps identify the true source of lag — for example, an unrelated expensive component re-rendering whenever search state changes, rather than the search input itself. Developers are advised to measure performance iteratively before and after any code changes, rather than assuming optimizations have worked.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds Open Tool to Mine App Store Reviews for Market Gaps

A developer has released App Store Review Miner, a free-to-try Apify Actor designed to identify improvement opportunities in existing apps. The tool pulls top-grossing app charts by category and country, then collects and classifies recent low-rated reviews into 13 complaint categories. It distinguishes between complaints that are widespread across a category versus those isolated to a single app, helping entrepreneurs spot genuine market gaps. The Actor also flags apps whose recent ratings have dropped significantly compared to their all-time scores, signaling potential vulnerabilities. Built with Node.js and Apple's public RSS endpoints, the tool is publicly available on the Apify platform, with Google Play support potentially coming based on user demand.

0 comments Read more at DEV Community