Update enterprise-v2.7.md for v2.7.6 (#301)

* Update enterprise-v2.7.md for v2.7.6

* Update release-downloads.md

* use s3 datetime for release date; remove curl cmd for 2.7.5

* add doc for mv_preferred_exec_node; past tense for changelog

* reorder 2.7.6 changelog, feature first, then bugfix, also mention EMIT syntax are changed

---------

Co-authored-by: Jove Zhong <jove@timeplus.io>

Author: kuiliu88

docs/enterprise-v2.7.md

@@ -34,9 +34,38 @@ Key highlights of this release:
 3. For Kubernetes users, please follow [the guide](/k8s-helm#v5-to-v6) carefully since a few timeplusd built-in users are removed in the new helm chart, and you can configure ingress for Appserver and Timeplusd independently.
 
 ## Releases
+### 2.7.6 {#2_7_6}
+Released on 04-29-2025. Installation options:
+* For Linux or Mac users: `curl https://install.timeplus.com/2.7 | sh` [Downloads](/release-downloads#2_7_6)
+* For Kubernetes users: `helm install timeplus/timeplus-enterprise --version v6.0.11 ..`
+* For Docker users (not recommended for production): `docker run -p 8000:8000 docker.timeplus.com/timeplus/timeplus-enterprise:2.7.6`
+
+Component versions:
+* timeplusd 2.7.45
+* timeplus_web 2.2.12
+* timeplus_appserver 2.2.13
+* timeplus_connector 2.2.8
+* timeplus cli 1.2.12
+
+#### Changelog {#changelog_2_7_6}
+
+Compared to the [2.7.5](#2_7_5) release:
+* timeplusd 2.7.37 -> 2.7.45
+  * added new setting [mv_preferred_exec_node](/sql-create-materialized-view#mv_preferred_exec_node) while creating materialized view
+  * added new EMIT policy `EMIT ON UPDATE WITH DELAY`. The SQL syntax for EMIT has been refactored. [Learn more](/query-syntax#emit)
+  * fixed global aggregation with `EMIT ON UPDATE` in multi-shard environments
+  * fixed concurrency issues in hybrid aggregation
+  * support incremental checkpoints for hybrid hash join
+  * fixed grouping key issues in hybrid aggregation
+
+#### Known issues {#known_issue_2_7_6}
+1. Pulsar external stream functionality is limited to Linux bare metal builds and Linux-based Docker images, excluding macOS bare metal builds.
+1. The `timeplus_connector` component may experience health issues on Ubuntu Linux with x86_64 chips, affecting Redpanda Connect functionality. This issue is specific to Ubuntu and does not affect other Linux distributions.
+1. Python UDF support is limited to Linux x86_64 bare metal and Linux x86_64 Docker image, excluding macOS or ARM builds.
+
 ### 2.7.5 {#2_7_5}
 Released on 04-14-2025. Installation options:
-* For Linux or Mac users: `curl https://install.timeplus.com/2.7 | sh` [Downloads](/release-downloads#2_7_4)
+* For Linux or Mac users: [Downloads](/release-downloads#2_7_4)
 * For Kubernetes users: `helm install timeplus/timeplus-enterprise --version v6.0.9 ..`
 * For Docker users (not recommended for production): `docker run -p 8000:8000 docker.timeplus.com/timeplus/timeplus-enterprise:2.7.5`
 

docs/release-downloads.md

@@ -10,6 +10,12 @@ Released on 03-24-2025 ([Change logs](/enterprise-v2.8#2_8_0)).
 
 ## 2.7 {#2_7}
 
+### v2.7.6 {#2_7_6}
+Released on 04-29-2025 ([Change logs](/enterprise-v2.7#2_7_6)).
+
+* Bare metal installation: [Linux x86_64](https://d.timeplus.com/timeplus-enterprise-v2.7.6-linux-amd64.tar.gz) | [Linux ARM64](https://d.timeplus.com/timeplus-enterprise-v2.7.6-linux-arm64.tar.gz) | [macOS x86_64](https://d.timeplus.com/timeplus-enterprise-v2.7.6-darwin-amd64.tar.gz) | [macOS ARM64](https://d.timeplus.com/timeplus-enterprise-v2.7.6-darwin-arm64.tar.gz)
+* All-in-one Docker image (not recommended for production): `docker run -p 8000:8000 docker.timeplus.com/timeplus/timeplus-enterprise:2.7.6`
+
 ### v2.7.5 {#2_7_5}
 Released on 04-14-2025 ([Change logs](/enterprise-v2.7#2_7_5)).
 

docs/sql-create-materialized-view.md

@@ -56,3 +56,30 @@ SETTINGS <settings>
 ```
 ### pause_on_start
 By default, once the materialized view is created, the streaming query will start automatically. If you don't want to start the query immediately, you can set `pause_on_start=true`. The default value is `false`.
+
+### memory_weight
+
+Starting from [Timeplus Enterprise v2.3](/enterprise-v2.3), when you create a materialized view with DDL SQL, you can add an optional `memory_weight` setting for those memory-consuming materialized views, e.g.
+```sql
+CREATE MATERIALIZED VIEW my_mv
+SETTINGS memory_weight = 10
+AS SELECT ..
+```
+
+When `memory_weight` is not set, by default the value is 0. When Timeplus Enterprise server starts, the system will list all materialized views, ordered by the memory weight and view names, and schedule them in the proper node.
+
+For example, in a 3-node cluster, you define 10 materialized views with names: mv1, mv2, .., mv9, mv10. If you create the first 6 materialized views with `SETTINGS memory_weight = 10`, then node1 will run mv1 and mv4; node2 will run mv2 and mv5; node3 will run mv3 and mv6; Other materialized views(mv7 to mv10) will be randomly scheduled on any nodes.
+
+It's recommended that each node in the Timeplus Enterprise cluster shares the same hardware specifications. For those resource-consuming materialized views, it's recommended to set the same `memory_weight`, such as 10, to get the expected behaviors to be dispatched to the proper nodes for load-balancing.
+
+### mv_preferred_exec_node
+
+Starting from [Timeplus Enterprise v2.7.6](/enterprise-v2.7#2_7_6), when you create a materialized view with DDL SQL, you can add an optional `mv_preferred_exec_node` setting to explicitly assign a node to run the materialized view.
+
+```sql
+CREATE MATERIALIZED VIEW my_mv
+SETTINGS mv_preferred_exec_node=3
+AS SELECT ..
+```
+
+In most cases, you don't need to specify this setting. Timeplus will automatically select an available node to run the materialized view. It's also recommended to set [memory_weight](#memory_weight) to have the system to automatically choose the appropriate node for load balancing. If you need to fine-tune the load balancing or resource utilization, you can specify this setting. As a result, load balancing or failover won't be available when this is set. You cannot change the value after the materialized view is created, even the node is having issue. In this case, please drop and re-create the materialized view with new node ID.