Release Notes
Customer-facing changes in ApertureDB, starting with version 0.19.13. Releases are listed newest first. Links point to the current documentation; older releases may use different parameters or response formats. See Removed APIs and replacements for removed inputs and their replacements in 1.0.0.
1.0.0
SDK compatibility
Python SDK (
aperturedb) 1.0.2 supports servers 0.20.0 and 1.0.0 over native TCP/TLS and HTTP. Applications using SDK 0.5.x must upgrade the SDK before upgrading the server to 1.0.0. Raw queries must use the command syntax of the connected server.On server 1.0.0, the SDK reads grouped connection selectors in schema and index results and supplies them when creating connection indexes. Typed connection CSVs select the endpoint objects before adding their connection. See class, GetSchema, and GetIndexes.
SDK helpers and CSV/model loaders support descriptor classes and vector indexes. See Descriptor classes and vector indexes.
Query protocol and connections
Native requests send a JSON-string session token, the JSON command array, a network-endian blob count, and sized binary blobs.
HTTP queries use
/api/. Multipart responses carry JSON metadata followed by raw binary blobs. See Query protocol for framing, completion checks, and retry guidance.Deferred media cancellation and unexpected response failures close the connection and release its accepted session. Subsequent connections remain available after either standard or non-standard exceptions.
Queued and active deferred media work no longer consumes the network send deadline. Blocked socket writes retain their 600-second timeout.
Accepted connections no longer reserve a query thread. Configure networking and execution independently with
network_threads,query_threads,query_queue_bytes_mb, andmax_read_transactions. Lenz opens backend connections on demand.
Expressions
Added scalar type checks:
is_number,is_bool,is_str, andis_date. They return false for null or missing values.Added explicit conversions:
str_to_number,number_to_str,str_to_bool,bool_to_str,bool_to_number,number_to_bool,str_to_date, anddate_to_str. They enforce the source type and return null for null or missing inputs.Added
ifto select between two values using a boolean condition. It evaluates only the selected branch and returns null for a null or missing condition. See constraints.
Descriptor indexing
Flat, IVF, HNSW, and ACORN indexes now commit or roll back with graph changes in the same transaction. Queries see their own pending descriptor changes.
A bounded memory cache accelerates descriptor search and eligible HNSW append batches in both synchronous and lazy modes. Configure its budget with
descriptor_index_cache_size_mb(default 512; zero disables caching). Searches continue while the cache rebuilds, and indexes larger than the budget remain searchable. See Configuration File.Descriptor sets are replaced by descriptor classes and vector indexes on their binary column. Each index has one kind (
flat,ivf,hnsw, oracorn) with engine settings directly inparams. Manage vector indexes withCreateIndex,UpdateIndex,GetIndexes, andRemoveIndex. See Descriptor classes and vector indexes.Class scope always applies before descriptor top-k. Classless search merges compatible indexes into one global top-k and rejects incompatible definitions.
GetIndexesreports indexed and pending descriptor counts and training state.The ACORN engine supports filtered vector search. HNSW
filtered_knnuses exact search for small eligible subsets. Configure index builds and lazy indexing through UpdateIndex.
Classes, schema, and query results
All object types require an explicit class on insertion and accept
with_classon reads and mutations. Classes are scoped by object type; connection classes are scoped by both endpoint classes and object types. AddConnection and connect take the connection name as a string inclass. The objects being connected supply the endpoint classes and types. Connection filters group class names inclass(src,connection,dst) and endpoint types intarget(src,dst). FindConnection takes the class and type of each referenced endpoint from its selected objects. Schema edges, connection index definitions, and aggregate definitions return the same selector.RenameClasspreserves object identities;RemoveClassremoves empty classes. See class.GetSchemareturns typed arrays of object and connection classes. Clients upgrading from 0.20.0 can find the response fields in GetSchema.Owner parameters in both directions support source grouping and per-group pagination. Projected rows include read-only class fields; connections also include endpoint type and class fields.
Media results remain available across commands in the same request. Failed commands discard partial output blobs while preserving successful results.
AddBlob now recognizes HTML, XML, SVG, vCard, iCalendar, and WebVTT from their content signatures. An explicit
mime_typestill takes precedence.
Connection aggregates
CreateAggregate maintains a read-only property on each parent,
such as an order total calculated from its line items. Each matching outgoing
connection contributes once. The aggregate can count, sum, average, or take the
minimum or maximum of values from the connections or their destination objects.
Supply src_property, operation, and either dst_expression or
connection_expression directly in the command body.
Creation includes existing connections. Later changes to connections or input properties update the parent and any dependent aggregates in the same transaction. Use GetAggregates to list definitions and RemoveAggregate to remove a definition and clear its stored values.
Compatibility and upgrade notes
Version 1.0.0 upgrades databases from 0.20.0 only. Before upgrading, start
each database with 0.20.0 and wait until it answers queries, for example
GetStatus; its startup conversions are then complete. 1.0.0 refuses to
open databases from older releases, or databases whose 0.20.0 startup has not
completed, and leaves them unchanged. Upgrade those through 0.20.0 first;
1.0.0 does not include its conversions.
The query and health ports now accept connections only after startup checks and migrations complete, so TCP readiness probes no longer pass while startup is still converting an existing database.
When a clustered server restarts at the same address, it waits up to two negotiated ZooKeeper session timeouts for its previous discovery registration to expire. If another session still owns the address, startup fails and the other registration stays intact. Check for another replica configured with the same role, host, and port before retrying.
Deploy matching server, checkpoint and administration binaries together.
Checkpoint publication waits until the completed snapshot uses the current logical graph format. If an upgrade cannot complete, the previous recovery point is preserved so that 0.20.0 can still open it. Upgrade preflight checks continue to reject unsupported legacy schemas.
Existing descriptor sets become descriptor classes. Supported custom properties move losslessly into vector-index metadata. Unsupported data or customer connections to set nodes prevent conversion. Keep a pre-upgrade backup for rollback.
Some descriptor IDs and split customer-connection IDs change. Conversion repairs internal graph references. Refresh references held outside the graph or stored as ordinary string properties after conversion. Interrupted upgrades resume on restart before serving requests.
Released IVF settings with nprobe greater than nlist are normalized to
the resolved list count during migration, preserving FAISS’s full-list probing
behavior. An omitted or zero list count uses the new default of 100. New API
requests instead reject excessive probe counts, unknown IVF or HNSW parameter
names, and invalid parameter types or ranges before writing graph data.
Migration removes previously ignored engine parameters. Migrated engines remain
synchronous; enable lazy indexing explicitly after upgrading.
Removed APIs and replacements
Earlier API or configuration |
Changes for 1.0.0 |
|---|---|
Descriptor-set commands, their system properties, and the |
Use descriptor classes. Specify |
Implicit node and connection classes |
All node Add commands require an application class scoped by node type. Supply a class for each customer connection. Its scope includes the classes and object types of both endpoints. See class. |
Previous schema and index response formats |
Use |
Cached-result paging with |
Use ordinary result selection and pagination. |
|
Configure query workers with |
Property-keyed constraints and object-form groups |
Use array expressions in |
|
Place these parameters at the command level. |
|
Use |
|
Use |
|
Use the documented administration interfaces or contact support for database repair procedures. |
Comments in JSON requests and configuration files |
Remove comments before sending requests or loading configuration files. |
|
Use host or container CPU monitoring. The old field always returned zero. |
|
Select storage with |
|
Remove these unused fields from configuration files. |
0.20.0
SDK compatibility
Compatible Python SDK (
aperturedbpackage) versions are 1.0.2, 0.5.4, and 0.5.3. SDK 1.0.2 supports both native TCP/TLS and HTTP on this server. See 1.0.0 for client upgrade considerations. For applications staying on the 0.5 series, use 0.5.4.This release revokes sessions on upgrade, after changes to a user or its roles, including adding or removing personal tokens, and when
max_sessions_per_useris exceeded. SDK versions before 0.5.3 run queries but do not sign in again after a revoked session: every later query on that connector fails withNot Authenticated!until a new connector is created. Versions before 0.5.0 also cannot read the schema format introduced in 0.19.15.SDK 0.5.3 has three remaining limitations, fixed in 0.5.4:
Operations.flipsends the numericcoderemoved in 0.19.13 (pass a flip operation withmodeinstead),Utils.create_entity_indexandUtils.create_connection_indexreturnFalsewhen the index already exists, andUtils.visualize_schemafails on a database without connection classes.SDK 0.5.4 descriptor helpers use the new engine syntax accepted in 0.20.0:
Utils.add_descriptorsetsends theenginesobject, andDescriptors.find_similar,Images.get_similar_imagesand SPARQL searches name the descriptor set’s engine. They add no deprecated usage on this release. Earlier server releases reject these forms; use SDK 0.5.3 with 0.19.14 to 0.19.16.
Media MIME types
Blobs, images, and videos now store a read-only
_mime_typeproperty. It describes the stored content after ingestion operations and can be returned, filtered, sorted, and indexed without reading the media contents.AddBlobaccepts an optionalmime_typestring to set_mime_typeat ingestion and skip automatic detection, including remote prefix reads. When omitted, the server detects the type from up to the first 4096 bytes; unrecognized content usesapplication/octet-stream. See AddBlob.The Web UI uses media MIME types for previews and downloads, including the output type of requested conversions.
Deprecations and API updates
Deprecation counters cover descriptor API usage, nested result selectors,
deprecated configuration fields, and GetStatus.cpu_utilization. The
Deprecations dashboard shows usage. See Removed APIs and replacements for the
replacements in 1.0.0.
API or parameter |
Behavior in 0.20.0 |
|---|---|
|
Accept the |
|
Accepts |
|
Accept |
|
Returns an |
|
Deprecated in this release. |
|
Deprecated. Descriptor-set partitioning ignores both values. |
|
Requests increment the deprecation counter even when debug commands are disabled. |
Memory use and monitoring
The server no longer cancels or rejects queries because of memory use. Earlier releases aborted queries for a few seconds whenever resident memory crossed a threshold.
Descriptor lookup failures retain their original errors instead of appearing as missing sets. Failed index cleanup no longer blocks other index refreshes or removes set metadata prematurely.
Restored client session creation and refresh counters and corrected their Grafana rate display.
Media and query fixes
Descriptor searches with the L2 and IP metrics now return zero and very small vectors, which earlier releases skipped. With L2 these are often among the nearest neighbors. CS searches still skip the zero vector.
Video transformations preserve audio by default.
AddVideo,FindVideo, andFindClipacceptwith_audio:falseto omit it. Applications that relied on silent transformed output should set this option explicitly. URL insertion does not accept audio removal or other transformations.Video operations preserve variable frame timing, accept valid inputs without container frame counts, and report metadata for the stored output. Preview size limits include audio and the finalized container.
FindClipapplies its requested output codec and container. Clips, intervals, previews, and frame extraction can read only the needed portion of seekable sources; performance depends on the format and source capabilities.HTTPS reads now support byte ranges to retrieve content prefixes and seek within remote media.
Corrected fractional frame retrieval, aspect ratios after video resizing and transposition, and duration metadata when copying video streams. Byte-limited previews retain more frames when the selected or resized output fits. Raw H.264 input can be converted to MP4.
Requests rejected for an invalid session or insufficient permissions no longer cause other users’ concurrent writes to fail.
Batch requests report a retryable batch failure when the worker computing the result loses its session. Workers with valid sessions are no longer told to sign in again because of another worker’s session failure.
Corrected error reporting and audit records: malformed sign-in requests keep their validation errors, command errors retain actionable messages, and requests that fail before authorization are no longer recorded as access denials. Fixed a potential stall when rejecting invalid remote URLs under load.
Authorization timings are available separately in
graph_authorization_seconds. Graph execution breakdowns no longer count authorization time twice. See GetMetrics for the metric labels.
Security and remote media
User, role, and remote-credential changes now succeed or roll back together with the query’s graph changes. Backups include these settings, and clustered deployments share them across replicas. Replicas may take a short time to reflect changes. See Access Control and Remote credentials.
Security changes now apply to subsequent requests after they succeed. Previously, existing sessions could retain outdated permissions, and S3, Google Cloud Storage, or HTTPS reads could continue using credentials after they were changed or removed.
Successful sign-in is limited to
max_sessions_per_usersessions per user, default 1024. At the limit, signing in revokes the oldest session and its refresh token. Refresh replaces both tokens. User and role changes revoke affected sessions; those users must sign in again.Remote credentials identify an exact S3 bucket, Google Cloud Storage bucket, or HTTPS origin. After an update succeeds, subsequent reads use the new key; removal blocks reads until a credential is registered again. These rules also apply to later batch-page requests. Create or update the credential and wait for success before submitting a query that needs it. Requests already underway may finish with the previous key.
HTTPS media reads reuse connections. Fixed requests being refused while old idle connections were closing, even when the request limit had not been reached.
Rejected sessions now return
code: "unauthenticated"even when the request also encounters invalid media or an unavailable source, so clients can sign in again and retry. Internal failures now use the standard error object used for other query failures.Failed batch queries now release waiting page requests and allow retries. Failed inserts remove newly created media files, and active transfers can finish safely when cached remote connections are replaced.
Fixed internal errors for invalid media URLs or missing remote credentials, and failures when creating and removing the same user, role, or credential within one query.
S3 errors when checking a remote object now include the HTTP status, for example
error in HeadObject: HTTP 403 - No response body., to help distinguish denied access, missing objects, expired tokens, and wrong regions.Improved authentication performance under concurrent sign-in requests and bounded session and connection reuse with
max_sessions_in_cache(default 1024) andmax_remote_connections(default 32).
HTTP services and deployment
Community Edition no longer has a time limit.
Web UI tabs share sign-in and coordinate session renewal. Temporary network failures during renewal no longer sign out every tab. Account changes confirm success before requesting a new sign-in, and newly created personal tokens remain available to copy. Open the Web UI over HTTPS, or localhost for local use.
Protected Web UI pages open correctly from bookmarks and offer a retry when account details cannot be loaded.
Bounding-box previews in the Web UI update as you change coordinates and labels. Failed saves and deletes preserve the draft and show an error; repeated Save clicks no longer create duplicate boxes.
The Web UI graph displays all class properties in a scrollable list. Property lists and the Data and Media tables preserve their scroll positions while navigating.
HTTP services now run independently of the native database gateway, with support for workflow WebSockets and streamed responses, including notebook sessions, Grafana Live, and streaming chat.
Helm and OpenTofu packages include the HTTP service without requiring an ingress controller. Workflow HTTP routes can be configured with
http.routes.Each ZooKeeper server can set CPU and memory requests and limits through
zookeeper.resources. Each workload can also configure its own pod tolerations. See the examples in Deploy with Helm and Deploy with OpenTofu.Helm and OpenTofu now publish ZooKeeper peer DNS records before pod readiness by default, so peers can discover each other during startup. Both packages and distributed Docker Compose also let a stalled ZooKeeper leader retry election when a voter is looking for a leader and a quorum has yet to respond. The default threshold is 30 seconds.
Helm and OpenTofu configure CPU and memory requests and limits independently for Grafana, Loki, Prometheus and each database pod’s Promtail. The HTTP proxy now defaults to a CPU limit of one core.
When upgrading a deployment that supplies the Grafana admin password inline, move it from
telemetry.grafana.adminPasswordtotelemetry.adminPasswordin Helm or fromtelemetry.grafana.admin_passwordtotelemetry.admin_passwordin OpenTofu. For an existing Kubernetes Secret, move its name fromtelemetry.grafana.existingSecrettotelemetry.adminPasswordSecretin Helm or fromtelemetry.grafana.existing_secrettotelemetry.admin_password_secretin OpenTofu.Move the monitoring bearer credential out of
telemetry.auth. In Helm, usetelemetry.authPasswordfor the inline value ortelemetry.authPasswordSecretfor the name of an existing Secret. The OpenTofu keys aretelemetry.auth_passwordandtelemetry.auth_password_secret.The monitoring PVC now uses the global storage class. Move
telemetry.persistence.storageClasstoglobal.storageClassin Helm ortelemetry.persistence.storage_classtoglobal.storage_classin OpenTofu. An empty value uses the cluster default. When upgrading, keep the storage class of the existing monitoring claim.Helm’s
dbEphemeralVolumeand OpenTofu’sdb_ephemeral_volumecan place database and checkpointer scratch data on per-pod generic ephemeral claims. Database pods mount the claim at/aperturedb/dband checkpointer pods at/checkpointer/db. One setting controls capacity and storage class for both pod types. The default uses each container’s filesystem.Lenz concurrency can be set independently through
lenz.adbMaxConcurrency(Helm) orlenz.adb_max_concurrency(OpenTofu). Omitted values keep the existing database-derived default.Compose has optional per-service CPU and memory overrides with unlimited defaults. The deployment guides list every override, and separate LoadBalancer, NodePort, and ClusterIP endpoint discovery instructions.
Removed the OpenTofu module’s historical
moved.tfstate migration.HTTP redirects and Grafana links use the configured public port, including direct NodePort access and deployments behind an external load balancer.
Valid certificate replacements are loaded automatically. Existing connections can finish with the previous certificate; invalid replacements leave the last valid certificate active.
The certificate that Docker Compose generates is valid for
localhost,127.0.0.1,::1, and the service nameslenzandhttp-proxy, so containers on the Compose network can verify it.TLS_CERT_HOSTNAMESadds the DNS names and IP addresses your clients use.Fixed REST requests that could disconnect before receiving a delayed database response when the client requested connection closure.
Improved gateway readiness checks to wait for its listeners and required TLS certificate before accepting routed traffic.
Compatibility and upgrade notes
This release supports direct upgrades from 0.19.14, 0.19.15, and 0.19.16. When upgrading from 0.19.14 or 0.19.15, also apply the compatibility and upgrade notes of each later 0.19 release below.
Startup fills missing MIME types for existing blobs, images, and videos before serving requests. Referenced media and any required remote credentials must remain accessible until startup completes. Interrupted upgrades resume on restart. Older binaries cannot reopen the upgraded database; retain a pre-upgrade backup for rollback.
Supported upgrades import users, roles, personal tokens, and usable remote credentials. Existing sessions and refresh tokens are not retained: sign in again after upgrading. Manage security settings through the API afterward; editing the old access-control files no longer changes access.
Submit
AuthenticateandRefreshTokenas single-command queries.Workers sharing a batched result must sign in as the same user. Refreshing a session or signing in again preserves that result until it expires. Access is checked for every page.
Update credential commands to use
originandkey. The oldname,service,resources,add_resources, andremove_resourcesselectors are no longer accepted.GetCredentialsreturns origin names without keys. Each bucket or HTTPS origin is imported separately. Entries with paths, trailing slashes or malformed keys are skipped and logged. For overlapping origins, the first structurally valid key in credential-name order is retained. Review origins withGetCredentials, replace keys withUpdateCredentialand test a media read. See Remote credentials for credential management.GetUsersnow returns accounts underusers;GetRolesreturns definitions underroles. Both responses includestatusandreturnedalongside the result object. Update clients that read names directly from the command response.Remove
session_cache_max_age_sec,sessions_file_refresh_rate_sec,prevent_telemetry_user_deletion, and the memory-guard fieldsresources_max_mem_limit,resources_check_mem_limit,resources_check_sleep, andresources_check_kill_timerfrom configuration; they are no longer accepted. See Configuration File for current settings.Startup rejects incompatible database contents. Rehearse the upgrade on a restored backup; if startup rejects the database, preserve its data and logs and contact support rather than deleting files to force it to open.
In Helm and OpenTofu configuration, replace
ingresshost and TLS settings withhttpsettings and remove bundled ingress-controller configuration. HTTP exposure is configured throughhttp.service;servicecontinues to configure native database exposure. Removeservice.enabledand use the desired Service type instead. Both Services are always created. UseClusterIPfor private access. Point web DNS at the new HTTP Service’s external address; the native database endpoint remains separate.For direct NodePort access, set fixed HTTP and HTTPS NodePorts under
http.service. Behind an external load balancer, sethttp.publicPort(Helm) orhttp.public_port(OpenTofu) to the public port, normally 443; backend NodePorts can then be allocated automatically.Docker Compose now uses the versioned
aperturedata/http-proxyimage. Registry mirrors must include it. ReplaceHTTP_MAX_BODY_SIZEwithHTTP_BODY_LIMITin bytes (256mbecomes268435456), and replaceHTTP_PROXY_READ_TIMEOUTwithHTTP_TIMEOUT_SECONDSin seconds. Remove upstreamNGINX_IMAGEoverrides; a full-image override now usesHTTP_PROXY_IMAGEand must provide the matching ApertureData proxy image. Use the upgrade command with--remove-orphansin the Compose guide to remove the previous HTTP service and release its published ports.Docker Compose deployments that use the generated certificate receive a new certificate on their first start. Clients that verify it must copy the new certificate, as described in Deploy with Docker Compose.
Public HTTP redirects to HTTPS when TLS is enabled. Configure API clients with the HTTPS URL directly; applications that follow redirects must preserve the request method and body for status 308.
See Deploy with Docker Compose, Deploy with Helm, and Deploy with OpenTofu for current configuration examples. Follow Changing a deployment when applying the new packages.
0.19.16
SDK compatibility
Compatible Python SDK (
aperturedbpackage) versions: 0.5.0 to 0.5.3. Versions 0.4.56 to 0.4.61 run queries, but their schema and index helpers, such asUtils.summary,Utils.visualize_schema, andUtils.get_indexed_props, fail or report no indexes with the schema format introduced in 0.19.15.
Features and improvements
Improved error messages for invalid constraint expressions, including operator and scalar-function arguments.
Fixed delays when the Web UI calculates the total size of returned blobs.
Fixed handling of configured memory limits larger than 32 bits and added validation to reject numeric configuration values that would overflow.
Published all ApertureData service images for both AMD64 and ARM64.
Bundled Prometheus and Loki configuration in versioned ApertureData images shared by Docker Compose, Helm, and OpenTofu deployment packages.
Published each Docker Compose layout in its own repository:
aperturedata/aperturedb-compose-single-node,aperturedata/aperturedb-compose-distributed-local, andaperturedata/aperturedb-compose-distributed-cloud. See Deploy with Docker Compose for package references.
Compatibility and upgrade notes
When upgrading Docker Compose from 0.19.15, remove upstream
PROMETHEUS_IMAGEandLOKI_IMAGEoverrides or replace them withaperturedata/prometheus:0.19.16andaperturedata/loki:0.19.16(or matching mirrored images or digests). The packages now rely on the configuration inside these images. Keeping an upstream Prometheus image silently stops ApertureDB metric collection. Update registry mirrors to include the new images.The database now correctly enforces configured memory limits larger than 32 bits. Check memory headroom before upgrading: the default memory guard starts aborting queries above 93% of the configured limit. Numeric configuration values that previously overflowed are now rejected.
Follow Changing a deployment when applying the new deployment packages.
0.19.15
SDK compatibility
Compatible Python SDK (
aperturedbpackage) versions: 0.5.0 to 0.5.3. Versions 0.4.56 to 0.4.61 run queries, but their schema and index helpers, such asUtils.summary,Utils.visualize_schema, andUtils.get_indexed_props, fail or report no indexes with the schema and index response formats introduced in this release.
Features and improvements
Added read-only access to objects at authorized HTTPS origins, with anonymous, Basic, or Bearer authentication configured through
CreateCredential. Even anonymous access requires an authorized origin. Only public HTTPS destinations are supported; redirects are not followed.Improved handling of large FindBlob responses. Requests that exceed the response-size limit return an error; use smaller result pages when retrieving large blobs.
Property names can now contain forward slashes and start with a digit, slash, or hyphen. See properties for naming rules.
Improved index use in queries that combine multiple filters.
Added Deploying ApertureDB guides for self-hosted installations using Docker Compose, Helm, and OpenTofu.
Docker Compose installations can configure services, resource limits, image overrides, and TLS certificates through one environment file.
Added the Alt+Enter shortcut for running custom queries in the Web UI.
Compatibility and upgrade notes
Databases on 0.19.13 must first upgrade to 0.19.14, then to 0.19.15. Version 0.19.15 cannot perform the 0.19.14 database conversion.
GetSchema now returns property objects with
countandtype, replacing[matched, indexed, type]arrays. Read index definitions from GetIndexes, whose response usesindexesandreturnedinstead ofentitiesandconnections. Update clients that parse these fields.Replace
commits_between_checkpointswithseconds_between_checkpoints. Scheduled checkpoints run when there are pending changes.
0.19.14
SDK compatibility
Compatible Python SDK (
aperturedbpackage) versions: 0.4.56 to 0.5.3.
Features and improvements
Added native array properties, including null elements, with membership, element-access, length, and whole-array comparisons. Array indexes can accelerate membership and selected element queries. See properties, constraints, and CreateIndex.
Added whole-string similarity matching and relevance-ranked full-text search with typo tolerance. See Text search expressions for the supported functions and index requirements.
Improved exact descriptor search performance and fixed nearest-neighbor results that could include deleted descriptors.
Fixed an issue with manually requested checkpoints.
Added deprecated-usage metrics to help identify queries that need updating.
Updated GetApiSchema to describe the current API.
Compatibility and upgrade notes
On the first startup with a 0.19.13 database, the 0.19.14 server or checkpointer converts stored JSON properties on objects and connections according to their top-level value.
Objects remain
Jsonproperties with their nested content intact.Arrays become native
Arrayproperties. Nulls, booleans, strings, and numbers keep their positions. Each immediate object or array becomes a string containing its original JSON text, including whitespace, escapes, and number spellings. For example, reading the migrated property[1,{"x":2},[3,4]]returns the following array.[1,"{\"x\":2}","[3,4]"]
A client that needs the nested object or array can decode the corresponding string with a JSON parser.
Booleans, strings, and numbers become native scalar properties. An integer converted to a native number must be exactly representable. For example,
[9007199254740993,{}]stops the upgrade, while[[9007199254740993]]becomes["[9007199254740993]"].
A top-level
null, malformed JSON, or a value that exceeds a native storage limit also stops the upgrade. Top-level strings have a limit of 65,535 bytes. The conversion rolls back properties, schema counts, and indexes together. Use the reported object or connection ID and property name to correct the value on 0.19.13, then retry.Back up the database before upgrading. In a cluster, also back up the corresponding cluster state and stop all 0.19.13 servers and checkpointers before starting 0.19.14. The server replays committed changes into a private checkpoint copy before converting and publishing it. Downgrading requires restoring the pre-upgrade backup.
Replace index type options
bool,number,date, andtext: falsewith"kind": "ordered"for scalar indexing. Ordered indexes cover all supported scalar types. See CreateIndex for other kinds.Indexes no longer return an
index_id. Identify an index by target, class, property, and kind.CreateIndexreturns a success status; inspect definitions with GetIndexes. Remove and recreate an index to change its parameters.
0.19.13
SDK compatibility
Compatible Python SDK (
aperturedbpackage) versions: 0.4.56 to 0.4.61. SDK 0.5.0 and later send list-membership and date constraints and index commands in forms this release rejects. Versions before 0.4.56 do not renew sessions and fail once a session expires.In SDK versions up to 0.5.3,
Operations.flipsends the numericcodethat this release no longer accepts; pass a flip operation withmodeinstead, for example{"type": "flip", "mode": "horizontal"}.Utils.create_entity_indexreturnsFalsewhenCreateIndexrejects an identical existing index.
Features and improvements
Added configurable ordered, substring, and property-type indexes, including case-sensitive and case-insensitive text options.
Added case-insensitive string operations to query expressions.
Added the transpose operation for images and videos. See operations.
The media
flipoperation now usesmodewithhorizontal,vertical, orbothinstead of numericcode. See operations.Added support for AWS default credentials and Google Cloud Application Default Credentials for the database’s own storage. Credentials registered for user-supplied object URLs remain separate.
Improved query performance and reporting of storage write failures.
Compatibility and upgrade notes
The following index-command status changes from 0.19.12 can break clients that distinguish successful no-ops from errors:
Creating an identical normalized index definition with
CreateIndexnow returnsstatus: -1withAn identical index definition already existsininfo, instead ofstatus: 2. In 0.19.13, different parameter configurations on the same class/property can coexist; this failure applies to an identical definition after defaults are normalized.CreateIndexrejection of an index on a computed property now returnsstatus: -1instead ofstatus: 5.RemoveIndexnow rejects removal of a protected built-in index withstatus: -1; previously its removal succeeded withstatus: 0. Removing an absent ordinary index still succeeds withstatus: 0.
A duplicate-index failure rolls back graph writes in the same transaction. Do not treat that failed transaction as a completed migration. See Failures and retrying writes and the recovery guidance in CreateIndex. Inspect definitions with GetIndexes before creating missing indexes; use the request and response formats for your server version.