Apache Ossie May Standardize Semantic Layers, Shifting Competition to Query-Time Features

·52 views

Apache Ossie is an emerging open-source standard aimed at creating a common interchange format for semantic layer models, backed by major industry players. By making it easier to migrate semantic model definitions between tools, it could significantly reduce vendor lock-in that has historically tied organizations to specific platforms. With portability of configurations becoming less of a differentiator, experts argue that competition will shift toward query-time expressiveness and data discoverability. Traditional semantic layers like Looker, Cube, and Metricflow were built for repetitive, filter-driven queries by human analysts, making them less suited for AI agents that require dynamic, flexible querying. An agent-ready semantic layer, in this new landscape, would need to support on-the-fly metric composition and help agents efficiently discover relevant tables, columns, and business rules across large datasets.

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)

Health check failed on a metadata endpoint while the model inference path worked

A paid red-team service showed every job failing with a model-unreachable error, even though the model itself was responsive. The worker ran a liveness check against a model metadata route, and that route returned a 500 error because an expired third-party token broke the provider roster. The check treated any non-200 response as an outage and stopped before running any probes. The actual inference route, which a separate provider router served, returned valid completions the entire time. The author fixed the issue by probing the same inference call the product uses and added an end-to-end job monitor running every two hours.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Scan of 512 Lovable app migrations finds widespread open Supabase write policies

A review of 512 public Lovable projects found that 16.2% include a migration policy letting signed-out visitors update or delete every row of a table. Another 1.4% expose the same write access to any signed-in user, and 10.4% create tables without enabling row level security. The authors examined the migration files the app builder shipped rather than querying live databases, and say they checked a sample of findings by hand and independently. Their tool, VibeRaven, is an open-source checker for Vercel and Supabase apps, and the analysis points to policies using a permissive true condition as a common cause.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Health check passed on a cached GET while every buyer POST to a dead origin failed

A buyer page returned 200 to a health check every five minutes for an evening, while every submission from that page failed. The CDN edge served the GET from cache, but the POST went to an origin tunnel that had died hours earlier, producing a 1033 error. An earlier fix had probed the buyer page, but used a GET, which cached responses can satisfy without proving the origin is up. The proposed remedy is to probe with a POST that requires the origin to return specific content, matching what customers actually send. The author argues health checks should mirror the customer's request, since a status code only reflects the single request it measured.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Cloudflare and Google DNS JSON Answers Can Differ, Due to Subnet and DNSSEC Settings

A DNS lookup can return different addresses depending on the resolver used, and the JSON responses from Cloudflare and Google's DNS-over-HTTPS services reveal why. Google applies EDNS Client Subnet by default, so CDN answers may vary with the subnet specified, while Cloudflare does not send that information. The authenticated-data flag only behaves consistently when the DO bit is set, and SERVFAIL responses need Extended DNS Error codes to determine the cause. The article's measurements were taken on specific dates and inputs, so the examples describe those runs rather than general rules.

0 comments Read more at DEV Community