More release notes and information about property access

Author: kriszyp

docs/developers/rest.md

@@ -30,7 +30,7 @@ This can be used to search for records by the specified property name and value.
 
 ### `GET /my-resource/<record-id>.property`
 
-This can be used to retrieve the specified property of the specified record.
+This can be used to retrieve the specified property of the specified record. Note that this will only work for properties that are declared in the schema.
 
 ## PUT
 

docs/technical-details/reference/blob.md

@@ -75,4 +75,20 @@ export class MyEndpoint extends MyTable {
 }
 ```
 
+### Blob `size`
+
+Blobs that are created from streams may not have the standard `size` property available, because the size may not be known while data is being streamed. Consequently, the `size` property may be undefined until the size is determined. You can listen for the `size` event to be notified when the size is available:
+```javascript
+let record = await MyTable.get('my-record');
+let blob = record.data;
+blob.size // will be available if it was saved with a known size
+let stream blob.stream(); // start streaming the data
+if (blob.size === undefined) {
+	blob.on('size', (size) => {
+		// will be called once the size is available
+	})
+}
+
+```
+
 See the [configuration](../../deployments/configuration.md) documentation for more information on configuring where blob are stored. 

docs/technical-details/reference/resource.md

@@ -387,6 +387,18 @@ This defines the source for a table. This allows a table to function as a cache
 
 If the source resource implements subscription support, real-time invalidation can be performed to ensure the cache is guaranteed to be fresh (and this can eliminate or reduce the need for time-based expiration of data).
 
+### `directURLMapping`
+This property can be set to force the direct URL request target to be mapped to the resource primary key. Normally, URL resource targets are parsed, where the path is mapped to the primary key of the resource (and decoded using standard URL decoding), and any query string parameters are used to query that resource. But if this is turned on, the full URL is used as the primary key. For example:
+```javascript
+export class MyTable extends tables.MyTable {
+    static directURLMapping = true;
+}
+```
+```http request
+GET /MyTable/test?foo=bar
+```
+This will be mapped to the resource with a primary key of `test?foo=bar`, and no querying will be performed on that resource.
+
 ### `parsePath(path, context, query) {`
 
 This is called by static methods when they are responding to a URL (from HTTP request, for example), and translates the path to an id. By default, this will parse `.property` suffixes for accessing properties and specifying preferred content type in the URL (and for older tables it will convert a multi-segment path to multipart an array id). However, in some situations you may wish to preserve the path directly as a string. You can override `parsePath` for simpler path to id preservation:

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

@@ -22,4 +22,10 @@ The default port for replication has been changed from 9925 to 9933.
 Accessing record properties from resource instances should be accessible through standard property access syntax, regardless of whether the property was declared in a schema. Previously only properties declared in a schema were accessible through standard property access syntax. This change allows for more consistent and intuitive access to record properties, regardless of how they were defined. It is still recommended to declare properties in a schema for better performance and documentation. 
 
 ### Cluster Status Information
-The [`cluster_status` operation](../../../developers/operations-api/clustering.md) now includes new statistics for replication, including the timestamps of last received transactions, sent transactions, and committed transactions.
+The [`cluster_status` operation](../../../developers/operations-api/clustering.md) now includes new statistics for replication, including the timestamps of last received transactions, sent transactions, and committed transactions.
+
+### URL id.property handling
+The `id.property` syntax for accessing properties in URLs will only be applied to properties that are declared in a schema. This allows for URLs to generally include dots in paths without being interpreted as property access.
+
+### HTTP/2
+HarperDB now supports HTTP/2 for all API endpoints.