<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/apache-polaris-1-8-0-what-s-new-and-upgrade-guide-2888bgjpt" -->

---
title: Apache Polaris 1.8.0: What's New and Upgrade Guide
description: Apache Polaris 1.8.0, released September 28, 2026, focuses on operational safety rather than new surface features. It adds dedicated authorization for semantic...
canonical: https://daily.dev/posts/apache-polaris-1-8-0-what-s-new-and-upgrade-guide-2888bgjpt
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Apache Polaris 1.8.0: What's New and Upgrade Guide | daily.dev
og:description: Apache Polaris 1.8.0, released September 28, 2026, focuses on operational safety rather than new surface features. It adds dedicated authorization for semantic...
og:url: https://daily.dev/posts/apache-polaris-1-8-0-what-s-new-and-upgrade-guide-2888bgjpt
og:image: https://api.daily.dev/og/posts/2888bGjpT.png
og:image:alt: Apache Polaris 1.8.0: What's New and Upgrade Guide
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Apache Polaris 1.8.0: What's New and Upgrade Guide

**[Dremio Blog](https://daily.dev/sources/dremio)** · 20 min read · 0 upvotes · 0 comments

## Summary

Apache Polaris 1.8.0, released September 28, 2026, focuses on operational safety rather than new surface features. It adds dedicated authorization for semantic models, changes stale-commit responses from HTTP 400 to 409, maps unknown commit states to 500, makes relational JDBC schema placement configurable, and adds pagination controls. Breaking changes affect custom authorizers (removal of synthetic ROOT target, per-intent evaluation), OPA policies, and token exchange for pre-1.8 internal JWTs. Existing PostgreSQL and CockroachDB deployments require manual index fixes since Polaris has no automated schema migrations. The bootstrap process no longer creates the database schema automatically. A detailed upgrade runbook covers inventory, backup, index fixes, authorization retesting, canary testing, and gradual rollout.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.dremio.com/blog/apache-polaris-1-8-0-whats-new-breaking-changes-and-upgrade-guide>

## Questions this post answers

### Does Apache Polaris 1.8.0 automatically apply the database index fixes for PostgreSQL and CockroachDB?

No, Polaris does not provide automated schema migrations for existing installations. Fresh schema version 6 installations get the corrected idx_locations index automatically, but existing PostgreSQL and CockroachDB databases must manually drop and recreate idx_locations, and CockroachDB deployments must also manually create three additional indexes on grant_records and entities tables that PostgreSQL and H2 have had since schema version 4.

_Teams planning database upgrades can track these operational gotchas by following Apache Polaris coverage on daily.dev._

### Why does Polaris 1.8.0 return HTTP 409 instead of 400 for stale table commits?

A 409 correctly signals that the request conflicted with current state and may succeed after the client refreshes and retries, following Iceberg commit rules, whereas 400 incorrectly implied the request itself was invalid. Polaris also checks whether base metadata is stale before writing proposed metadata, avoiding wasted object-store writes and deletes under high-concurrency commit contention.

_Developers debugging concurrent commit failures can follow catalog behavior changes like this on daily.dev._

### What breaks for custom authorizers and OPA policies when upgrading to Apache Polaris 1.8.0?

PolarisAuthorizer inputs change in two ways: resource targets and parent paths no longer include the internal synthetic ROOT container, so a catalog target has an empty parent path, and a request with multiple authorization intents is now evaluated one intent at a time instead of as a combined list. This means Rego policies expecting combined intents can produce different results and require explicit allow/deny regression tests before upgrading.

_Engineers maintaining custom OPA authorization logic can watch for breaking changes like this via daily.dev._

## Similar posts on daily.dev

- [Apache Polaris Architecture Explained](https://daily.dev/posts/apache-polaris-architecture-explained-txzywei9p) · Dremio Blog · 1 upvotes · 0 comments
- [Apache Polaris is powered by Quarkus](https://daily.dev/posts/apache-polaris-is-powered-by-quarkus-rqxuiht4v) · Quarkus · 0 upvotes · 0 comments
- [The Apache Polaris REST API Explained](https://daily.dev/posts/the-apache-polaris-rest-api-explained-jzkzrhix6) · Dremio Blog · 0 upvotes · 0 comments
- [Apache Polaris Graduates to Top-Level Project](https://daily.dev/posts/apache-polaris-graduates-to-top-level-project-ovrl52tub) · Snowflake · 0 upvotes · 0 comments

---

Tags: [#database](https://daily.dev/tags/database), [#postgresql](https://daily.dev/tags/postgresql), [#authorization](https://daily.dev/tags/authorization), [#apache-iceberg](https://daily.dev/tags/apache-iceberg)

[View this post on daily.dev](https://daily.dev/posts/apache-polaris-1-8-0-what-s-new-and-upgrade-guide-2888bgjpt)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Apache Polaris 1.8.0: What's New and Upgrade Guide","url":"https://daily.dev/posts/apache-polaris-1-8-0-what-s-new-and-upgrade-guide-2888bgjpt","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/apache-polaris-1-8-0-what-s-new-and-upgrade-guide-2888bgjpt"},"datePublished":"2026-09-30T02:55:34.142Z","dateModified":"2026-09-30T02:55:57.865Z","description":"Apache Polaris 1.8.0, released September 28, 2026, focuses on operational safety rather than new surface features. It adds dedicated authorization for semantic...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e159778c6d8e5810ec82cee9dd583dbc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e159778c6d8e5810ec82cee9dd583dbc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Dremio Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Dremio Blog","logo":"https://media.daily.dev/image/upload/s--MGKANojy--/f_auto,q_auto/v1786870389/logos/dremio?_a=BAMAMicg0","url":"https://daily.dev/sources/dremio"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/apache-polaris-1-8-0-what-s-new-and-upgrade-guide-2888bgjpt","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"database,postgresql,authorization,apache-iceberg","timeRequired":"PT20M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Dremio Blog","item":"https://daily.dev/sources/dremio"},{"@type":"ListItem","position":3,"name":"Apache Polaris 1.8.0: What's New and Upgrade Guide"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/apache-polaris-1-8-0-what-s-new-and-upgrade-guide-2888bgjpt#faq","mainEntity":[{"@type":"Question","name":"Does Apache Polaris 1.8.0 automatically apply the database index fixes for PostgreSQL and CockroachDB?","acceptedAnswer":{"@type":"Answer","text":"No, Polaris does not provide automated schema migrations for existing installations. Fresh schema version 6 installations get the corrected idx_locations index automatically, but existing PostgreSQL and CockroachDB databases must manually drop and recreate idx_locations, and CockroachDB deployments must also manually create three additional indexes on grant_records and entities tables that PostgreSQL and H2 have had since schema version 4. Teams planning database upgrades can track these operational gotchas by following Apache Polaris coverage on daily.dev."}},{"@type":"Question","name":"Why does Polaris 1.8.0 return HTTP 409 instead of 400 for stale table commits?","acceptedAnswer":{"@type":"Answer","text":"A 409 correctly signals that the request conflicted with current state and may succeed after the client refreshes and retries, following Iceberg commit rules, whereas 400 incorrectly implied the request itself was invalid. Polaris also checks whether base metadata is stale before writing proposed metadata, avoiding wasted object-store writes and deletes under high-concurrency commit contention. Developers debugging concurrent commit failures can follow catalog behavior changes like this on daily.dev."}},{"@type":"Question","name":"What breaks for custom authorizers and OPA policies when upgrading to Apache Polaris 1.8.0?","acceptedAnswer":{"@type":"Answer","text":"PolarisAuthorizer inputs change in two ways: resource targets and parent paths no longer include the internal synthetic ROOT container, so a catalog target has an empty parent path, and a request with multiple authorization intents is now evaluated one intent at a time instead of as a combined list. This means Rego policies expecting combined intents can produce different results and require explicit allow/deny regression tests before upgrading. Engineers maintaining custom OPA authorization logic can watch for breaking changes like this via daily.dev."}}]}
```

