Skip to content
Palantir Ontology SQL Functions GA: Unify Business Rules Across Systems
Big Data 10 min read

Palantir Ontology SQL Functions GA: Unify Business Rules Across Systems

Palantir's Foundry now offers GA Ontology SQL and SQL Functions, letting developers query ontology objects and relationships directly and publish parameterized queries as reusable functions so supply chain dashboards, customer service tools, and automation systems all apply the same business logic for predicting delivery delays while supporting versioned rule updates.

DataFunSummit
DataFunSummit
DataFunSummit

The Problem: One Shipment Delay, Three Different Lists

A shipment originally due Wednesday slips to Friday. The supply chain dashboard flags all related orders red. The customer service workbench extracts a list of customers to contact proactively. The automation system sends no alert at all. Three systems look at the same shipment but produce three different conclusions because each encodes its own definition of "which orders are predicted to miss their delivery commitment."

Shipment delay ≠ order breach ≠ customer alert. Each state has a valid use case, but the systems never explicitly distinguished them. Worse, business rules change — orders get split, customers renegotiate dates — and logic duplicated across systems inevitably diverges.

Ontology SQL: Query the Ontology Directly

In Foundry, enterprises model customers, orders, and shipment batches as object types with links expressing relationships (an order can split across batches; a batch can contain multiple orders — a many-to-many link). Ontology SQL lets developers query object types, interfaces, and many-to-many links directly, referencing link tables already defined in Ontology Manager. No separate join tables need to be maintained.

The query still requires the developer to write the exact business logic: undelivered quantities, estimated delivery dates, and the customer's current valid promise date. Ontology SQL supports a subset of Spark SQL dialect; suitable queries hit object storage with in-memory compute, while more complex ones fall back to Spark execution. The engine does not guess the business semantics.

SQL Functions: Publish Once, Call Everywhere

Developers write the query in SQL Studio, parameterize it (e.g., shipment batch ID), and publish it as an Ontology SQL Function. The function returns the predicted-late orders, their customers, promise dates, and estimated delivery dates — it does not mutate data or send notifications; those actions remain in Actions, Automate, etc.

After publishing, Workshop, Actions, Automate, and the Ontology SDK can all call the same function. The supply chain dashboard evaluates re-routing options, the service workbench aggregates by customer, and the automation flow decides whether to create a task. The underlying "predicted breach" judgment comes from a single reusable function. Differences in presented results (e.g., five orders but three customers) are traceable to clear business logic (one customer has multiple orders), not to divergent SQL.

Versioned Functions: Change Rules Without Breaking Consumers

When a customer moves a promise date from Thursday to Friday, the order drops off the alert list. Yet month-end reconciliation may still need the original Thursday commitment. Therefore "original promise date" and "latest confirmed date" must not simply overwrite each other ; the function must encode which date the alert uses and what constitutes customer confirmation.

With the logic encapsulated in a function, developers update the function body while keeping inputs and outputs stable. Foundry's Ontology Manager shows function versions; Workshop, Actions, and Automate can pin a specific version or depend on a version range. Teams can validate the new rule in the service workbench before switching the automation flow, avoiding a big-bang cutover. Version ranges may auto-adopt new versions, so high-stability flows should pin explicitly.

Result

The ontology gives orders, batches, and customers a shared relationship definition. Ontology SQL makes those relationships directly queryable. SQL Functions turn the query's business judgment into a versioned, cross-application callable unit. Next time a shipment is late, the warehouse still sees all affected orders, service still contacts only at-risk customers, and automation still runs on its own schedule — but when they answer the same question, they no longer each write their own answer. Enterprises reduce not just duplicate SQL, but rounds of reconciliation, investigation, and correction caused by rule divergence.

References: Palantir — November 2026 Announcements: Ontology SQL and SQL Functions are GA (12 Nov 2026) Palantir — Ontology SQL: Querying Object Types, Interfaces, and Many-to-Many Links Palantir — Ontology SQL Functions: Parameters, Publishing, and Cross-Application Invocation Palantir — Version Range Dependencies for Functions Palantir — Core Concepts: Objects, Properties, and Links in the Ontology
Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

Supply ChainData ConsistencyBusiness LogicVersioningEnterprise SoftwareOntologySQL FunctionsPalantirFoundryOntology SQL
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.