Encharge vs Open Web Analytics

OWA published more releases in the last month than in the previous two years, and 1.11.0 is the first of them that adds rather than repairs. It brings two new subsystems that depend on each other: date partitioning for the fact tables, and a job scheduler driven by a single cron entry. Behind it sits the repair sequence — security hardening in 1.8.2 and 1.8.3, a PHP 8.2 floor and rebuilt JavaScript toolchain in 1.9.0, an emergency 403 fix in 1.9.1, the PSR-4 migration and a repaired updater in 1.10.0, and tightened REST responses in 1.10.1.

The project has moved from making itself installable to making itself operable at volume. The upgrade design says the maintainers know who they are dealing with: the schema update is mandatory and the scheduler refuses every job until it runs, but partitioning an existing install is deliberately left as a manual, dry-runnable step with a published cost of roughly five seconds per million rows per table, because it rewrites each fact table twice under a write lock. The new cron requirement is the first time OWA has asked operators to run something periodic, and the admin nag until it exists suggests they expect people to miss it.

With partitioning in place but opt-in, expect the follow-up work to be retention and pruning on top of the partitions — the reason to partition fact tables is to drop old ones cheaply, and the scheduler is the piece that would do it. The 2.0 deprecation list flagged in 1.10.0 remains the other open thread.