Merge branch 'release_4.6'

Author: kriszyp

docs/SUMMARY.md

@@ -134,9 +134,12 @@
   * [Transactions](technical-details/reference/transactions.md)
 * [Release Notes](technical-details/release-notes/README.md)
   * [Harper Tucker (Version 4)](technical-details/release-notes/4.tucker/README.md)
+    * [4.6.3](technical-details/release-notes/4.tucker/4.6.3.md)
     * [4.6.2](technical-details/release-notes/4.tucker/4.6.2.md)
     * [4.6.1](technical-details/release-notes/4.tucker/4.6.1.md)
     * [4.6.0](technical-details/release-notes/4.tucker/4.6.0.md)
+    * [4.5.16](technical-details/release-notes/4.tucker/4.5.16.md)
+    * [4.5.15](technical-details/release-notes/4.tucker/4.5.15.md)
     * [4.5.14](technical-details/release-notes/4.tucker/4.5.14.md)
     * [4.5.13](technical-details/release-notes/4.tucker/4.5.13.md)
     * [4.5.12](technical-details/release-notes/4.tucker/4.5.12.md)

docs/deployments/configuration.md

@@ -295,7 +295,7 @@ The port to use for secure replication connections.
 
 When true, Harper will verify certificates against the Node.js bundled CA store. The bundled CA store is a snapshot of the Mozilla CA store that is fixed at release time.
 
-`copyTablesToCatchUp` - _Type_: boolean; _Default_: true
+`copyTablesToCatchUp` - _Type_: boolean; _Default_: false
 
 Replication will first attempt to catch up using the audit log. If unsuccessful, it will perform a full table copy. When set to `false`, replication will only use the audit log.
 

docs/technical-details/release-notes/4.tucker/4.2.0.md

@@ -4,27 +4,27 @@
 
 HarperDB 4.2 introduces a new interface to accessing our core database engine with faster access, well-typed idiomatic JavaScript interfaces, ergonomic object mapping, and real-time data subscriptions. 4.2 also had adopted a new component architecture for building extensions to deliver customized external data sources, authentication, file handlers, content types, and more. These architectural upgrades lead to several key new HarperDB capabilities including a new REST interface, advanced caching, real-time messaging and publish/subscribe functionality through MQTT, WebSockets, and Server-Sent Events.
 
-4.2 also introduces configurable database schemas, using GraphQL Schema syntax. The new component structure is also configuration-driven, providing easy, low-code paths to building applications. [Check out our new getting starting guide](../../../getting-started.md) to see how easy it is to get started with HarperDB apps.
+4.2 also introduces configurable database schemas, using GraphQL Schema syntax. The new component structure is also configuration-driven, providing easy, low-code paths to building applications. [Check out our new getting starting guide](/docs/4.2/getting-started) to see how easy it is to get started with HarperDB apps.
 
 ### Resource API
 
-The [Resource API](../../reference/resource.md) is the new interface for accessing data in HarperDB. It utilizes a uniform interface for accessing data in HarperDB database/tables and is designed to easily be implemented or extended for defining customized application logic for table access or defining custom external data sources. This API has support for connecting resources together for caching and delivering data change and message notifications in real-time. The [Resource API documentation details this interface](../../reference/resource.md).
+The [Resource API](/docs/4.2/technical-details/reference/resource) is the new interface for accessing data in HarperDB. It utilizes a uniform interface for accessing data in HarperDB database/tables and is designed to easily be implemented or extended for defining customized application logic for table access or defining custom external data sources. This API has support for connecting resources together for caching and delivering data change and message notifications in real-time. The [Resource API documentation details this interface](/docs/4.2/technical-details/reference/resource).
 
 ### Component Architecture
 
-HarperDB's custom functions have evolved towards a [full component architecture](../../../developers/components/); our internal functionality is defined as components, and this can be used in a modular way in conjunction with user components. These can all easily be configured and loaded through configuration files, and there is now a [well-defined interface for creating your own components](broken-reference). Components can easily be deployed/installed into HarperDB using [NPM and Github references as well](broken-reference).
+HarperDB's custom functions have evolved towards a [full component architecture](/docs/4.2/technical-details/reference/components/); our internal functionality is defined as components, and this can be used in a modular way in conjunction with user components. These can all easily be configured and loaded through configuration files, and there is now a [well-defined interface for creating your own components](/docs/4.2/technical-details/reference/components/extensions). Components can easily be deployed/installed into HarperDB using [NPM and Github references as well](/docs/4.2/technical-details/reference/components/configuration).
 
 ### Configurable Database Schemas
 
-HarperDB applications or components support [schema definitions using GraphQL schema syntax](../../../developers/applications/defining-schemas.md). This makes it easy to define your table and attribute structure and gives you control over which attributes should be indexed and what types they should be. With schemas in configuration, these schemas can be bundled with an application and deployed together with application code.
+HarperDB applications or components support [schema definitions using GraphQL schema syntax](/docs/4.2/developers/applications/defining-schemas). This makes it easy to define your table and attribute structure and gives you control over which attributes should be indexed and what types they should be. With schemas in configuration, these schemas can be bundled with an application and deployed together with application code.
 
 ### REST Interface
 
 HarperDB 4.2 introduces a new REST interface for accessing data through best-practice HTTP APIs using intuitive paths and standards-based methods and headers that directly map to our Resource API. This new interface provides fast and easy access to data via queries through GET requests, modifications of data through PUTs, customized actions through POSTs and more. With standards-based header support built-in, this works seamlessly with external caches (including browser caches) for accelerated performance and reduced network transfers.
 
 ### Real-Time
 
-HarperDB 4.2 now provides standard interfaces for subscribing to data changes and receiving notifications of changes and messages in real-time. Using these new real-time messaging capabilities with structured data provides a powerful integrated platform for both database style data updates and querying along with message delivery. [Real-time messaging](../../../developers/real-time.md) of data is available through several protocols:
+HarperDB 4.2 now provides standard interfaces for subscribing to data changes and receiving notifications of changes and messages in real-time. Using these new real-time messaging capabilities with structured data provides a powerful integrated platform for both database style data updates and querying along with message delivery. [Real-time messaging](/docs/4.2/developers/real-time) of data is available through several protocols:
 
 #### MQTT
 
@@ -46,7 +46,7 @@ Databases are now entirely encapsulated in a file, which means they can be moved
 
 ### Clone Node
 
-HarperDB includes new functionality for adding new HarperDB nodes in a cluster. New instances can be configured to clone from a leader node, performing and copying a database snapshot from a leader node, and self-configuring from the leader node as well, to facilitate accelerated deployment of new nodes for fast horizontal scaling to meet demand needs. [See the documentation on Clone Node for more information.](../../../administration/cloning.md)
+HarperDB includes new functionality for adding new HarperDB nodes in a cluster. New instances can be configured to clone from a leader node, performing and copying a database snapshot from a leader node, and self-configuring from the leader node as well, to facilitate accelerated deployment of new nodes for fast horizontal scaling to meet demand needs. [See the documentation on Clone Node for more information.](/docs/4.2/administration/cloning)
 
 ### Operations API terminology updates
 

docs/technical-details/release-notes/4.tucker/4.3.0.md

@@ -37,7 +37,7 @@ HarperDB also now supports querying with a sort order. Multiple sort orders can
 /Product?brand.name=Microsoft&sort(price)&select(name,brand{name,size})
 ```
 
-See the [schema definition documentation](../../../developers/applications/defining-schemas.md) for more information on defining relationships, and the [REST documentation for more information on queries](../../../developers/rest.md).
+See the [schema definition documentation](/docs/4.3/developers/applications/defining-schemas) for more information on defining relationships, and the [REST documentation for more information on queries](/docs/4.3/developers/rest).
 
 #### OpenAPI Specification
 
@@ -77,7 +77,7 @@ HarperDB has upgraded the local studio to match the same version that is offered
 
 #### mTLS Support
 
-HarperDB now supports mTLS based authentication for HTTP, WebSockets, and MQTT. See the [configuration documentation for more information](../../../deployments/configuration.md).
+HarperDB now supports mTLS based authentication for HTTP, WebSockets, and MQTT. See the [configuration documentation for more information](/docs/4.3/deployments/configuration).
 
 #### Single-Level Wildcards
 
@@ -91,11 +91,11 @@ HarperDB's MQTT now supports the retain handling flags for subscriptions that ar
 
 HarperDB now supports basic conflict-free data type (CRDT) updates that allow properties to be individually updated and merged when separate properties are updated on different threads or nodes. Individual property CRDT updates are automatically performed when you update individual properties through the resource API. Individual property CRDT updates are used when making `PATCH` requests through the REST API.
 
-The CRDT functionality also supports explicit incrementation to merge multiple parallel incrementation requests with proper summing. See the [Resource API for more information](../../reference/resource.md).
+The CRDT functionality also supports explicit incrementation to merge multiple parallel incrementation requests with proper summing. See the [Resource API for more information](/docs/4.3/technical-details/reference/resource).
 
 #### Configuration Improvements
 
-The configuration has improved support for detecting port conflicts, handling paths for fastify routes, and now includes support for specifying a heap limit and TLS ciphers. See the [configuration documentation for more information](../../../deployments/configuration.md).
+The configuration has improved support for detecting port conflicts, handling paths for fastify routes, and now includes support for specifying a heap limit and TLS ciphers. See the [configuration documentation for more information](/docs/4.3/deployments/configuration).
 
 #### Balanced Audit Log Cleanup
 
@@ -111,7 +111,7 @@ Significant improvements were made to handling of free-space to decrease free-sp
 
 #### Compact Database
 
-In addition to storage improvements, HarperDB now includes functionality for [compacting a database](../../../deployments/harper-cli.md) (while offline), which can be used to eliminate all free-space to reset any fragmentation.
+In addition to storage improvements, HarperDB now includes functionality for [compacting a database](/docs/4.3/deployments/harper-cli) (while offline), which can be used to eliminate all free-space to reset any fragmentation.
 
 #### Compression
 

docs/technical-details/release-notes/4.tucker/4.4.0.md

@@ -20,15 +20,15 @@ Certain operations can now be replicated across the cluster, including the deplo
 
 ### Computed Properties
 
-Computed properties allow applications to define properties that are computed from other properties, allowing for composite properties that are calculated from other data stored in records without requiring actual storage of the computed value. For example, you could have a computed property for a full name based on first and last, or age/duration based on a date. Computed properties are also foundational for custom indexes. See the [schema documentation ](../../../developers/applications/defining-schemas.md), [Resource API](../../reference/resource.md), and our blog post on [computed properties](https://www.harperdb.io/development/tutorials/how-to-create-custom-indexes-with-computed-properties) for more information.
+Computed properties allow applications to define properties that are computed from other properties, allowing for composite properties that are calculated from other data stored in records without requiring actual storage of the computed value. For example, you could have a computed property for a full name based on first and last, or age/duration based on a date. Computed properties are also foundational for custom indexes. See the [schema documentation ](/docs/4.4/developers/applications/defining-schemas), [Resource API](/docs/4.4/technical-details/reference/resource), and our blog post on [computed properties](https://www.harperdb.io/development/tutorials/how-to-create-custom-indexes-with-computed-properties) for more information.
 
 ### Custom Indexing
 
-Custom indexes can now be defined using computed properties to allow for unlimited possibilities of indexing, including composite, full-text indexing, vector indexing. Again, see the [schema documentation](../../../developers/applications/defining-schemas.md) for more information.
+Custom indexes can now be defined using computed properties to allow for unlimited possibilities of indexing, including composite, full-text indexing, vector indexing. Again, see the [schema documentation](/docs/4.4/developers/applications/defining-schemas) for more information.
 
 ### Native Graph Support
 
-HarperDB now includes provisional support for native [GraphQL querying functionality](../../reference/graphql.md). This allows for querying of graph data using GraphQL syntax. This is provisional and some APIs may be updated in the future.
+HarperDB now includes provisional support for native [GraphQL querying functionality](/docs/4.4/technical-details/reference/graphql). This allows for querying of graph data using GraphQL syntax. This is provisional and some APIs may be updated in the future.
 
 ### Dynamic Certificate Management
 

docs/technical-details/release-notes/4.tucker/4.5.0.md

@@ -6,7 +6,7 @@
 
 ### Blob Storage
 
-4.5 introduces a new [Blob storage system](../../reference/blob.md), that is designed to efficiently handle large binary objects, with built-in support for streaming large content/media in and out of storage. This provides significantly better performance and functionality for large unstructured data, such as HTML, images, video, and other large files. Components can leverage this functionality through the JavaScript `Blob` interface, and the new `createBlob` function. Blobs are fully replicated and integrated. Harper can also coerce strings to `Blob`s (when dictated by the field type), making it feasible to use blobs for large string data, including with MQTT messaging.
+4.5 introduces a new [Blob storage system](/docs/4.5/technical-details/reference/blob), that is designed to efficiently handle large binary objects, with built-in support for streaming large content/media in and out of storage. This provides significantly better performance and functionality for large unstructured data, such as HTML, images, video, and other large files. Components can leverage this functionality through the JavaScript `Blob` interface, and the new `createBlob` function. Blobs are fully replicated and integrated. Harper can also coerce strings to `Blob`s (when dictated by the field type), making it feasible to use blobs for large string data, including with MQTT messaging.
 
 ### Password Hashing Upgrade
 
@@ -45,7 +45,7 @@ Certificates can now be revoked by configuring nodes with a list of revoked cert
 
 ### Built-in `loadEnv` Component
 
-There is a [new `loadEnv` component loader](../../../developers/components/built-in.md) that can be used to load environmental variables from a .env in a component.
+There is a [new `loadEnv` component loader](/docs/4.5/developers/components/built-in) that can be used to load environmental variables from a .env in a component.
 
 ### Cluster Status Information
 

docs/technical-details/release-notes/4.tucker/4.5.15.md

@@ -0,0 +1,5 @@
+### HarperDB 4.5.15
+7/21/2025
+
+- Removed the `copyTablesToCatchUp` option and instead utilized the clone node designation of the leader node to copy tables
+- Ensure that skipping large number of audit entries does not lock up the thread and cause a connection reset

docs/technical-details/release-notes/4.tucker/4.5.16.md

@@ -0,0 +1,4 @@
+### HarperDB 4.5.16
+7/30/2025
+
+- Do not free/remove the shared user buffer that is used by all threads as an atomic counter for ids (for blobs and incremented ids), but retain it as a stable allocated buffer 

docs/technical-details/release-notes/4.tucker/4.6.3.md

@@ -0,0 +1,7 @@
+# 4.6.3
+7/30/2025
+
+- Fix for calling table.operation()
+- Do not free/remove the shared user buffer that is used by all threads as an atomic counter for ids (for blobs and incremented ids), but retain it as a stable allocated buffer
+- Removed the `copyTablesToCatchUp` option and instead utilized the clone node designation of the leader node to copy tables
+- Ensure that skipping large number of audit entries does not lock up the thread and cause a connection reset

docs/technical-details/release-notes/4.tucker/README.md

@@ -12,7 +12,7 @@ HarperDB version 4 ([Tucker release](tucker.md)) represents major step forward i
 
 ## [4.5](4.5.0.md)
 
-- Blob Storage - 4.5 introduces a new [Blob storage system](../../reference/blob.md).
+- Blob Storage - 4.5 introduces a new [Blob storage system](/docs/4.5/technical-details/reference/blob).
 - Password Hashing Upgrade - two new password hashing algorithms for better security (to replace md5).
 - New resource and storage Analytics