Fusion Registry Wiki - Recent changes [en]

FXLData Change Log

Vmurrell — Thu, 01 Oct 2026 07:42:00 GMT

Change Log FR - V11 and subsequent releases

Vmurrell — Thu, 01 Oct 2026 07:36:01 GMT

‎Hotfix H2.0.0.01_RFS_30.09.26

Change Log Fusion Data Browser

Vmurrell — Thu, 01 Oct 2026 07:31:54 GMT

Change Log FR - V11 and subsequent releases

Vmurrell — Thu, 01 Oct 2026 07:29:59 GMT

‎Hotfix H2.0.0.01_RFS_30.09.26

What's new

Vmurrell — Thu, 01 Oct 2026 07:28:27 GMT

‎Key Features

File:Compatibility-sept2026.png

Vmurrell — Mon, 28 Sep 2026 11:45:47 GMT

Vmurrell uploaded File:Compatibility-sept2026.png

New page

What's new

Vmurrell — Mon, 28 Sep 2026 11:42:13 GMT

‎September 2026 H2.0.0.01

Aggregations- Series Threshold

Vmurrell — Thu, 24 Sep 2026 09:27:35 GMT

Created page with "Category:Fusion Registry Configuration To make a permanent change you can add this parameter to the properties file: -Daggregation.query.limit=XXXXXX The default is set..."

New page

[[Category:Fusion Registry Configuration]]

To make a permanent change you can add this parameter to the properties file:

-Daggregation.query.limit=XXXXXX

The default is set at 10,000.

This can be configured dynamically [[System_Properties#Properties_which_may_be_Dynamically_changed | as described in this article]].

System Properties

Vmurrell — Thu, 24 Sep 2026 09:22:00 GMT

‎Properties which may be Dynamically changed

Auto Aggregate items using hierarchies

Vmurrell — Thu, 24 Sep 2026 09:17:53 GMT

What's new

Vmurrell — Thu, 24 Sep 2026 09:01:04 GMT

‎September 2026 H2.0.0.01

Auto Aggregate items using hierarchies

Vmurrell — Thu, 24 Sep 2026 08:59:52 GMT

‎Parameter detail=forceAggregates

What's new

Vmurrell — Thu, 24 Sep 2026 08:20:25 GMT

‎September 2026 H2.0.0.01

Release Plans

Vmurrell — Wed, 23 Sep 2026 17:03:17 GMT

‎Next Release

What's new

Vmurrell — Wed, 23 Sep 2026 16:43:44 GMT

‎September 2026 H2.0.0.01

Auto Aggregate items using hierarchies

Vmurrell — Wed, 23 Sep 2026 16:31:33 GMT

@@ Line 2: / Line 2: @@
 '''Excel Command'''<br>
   =FXLDataVersion("changelog")
 =Release R2.0.0.00_RFS_28.08.26 Released August 28, 2026=

@@ Line 5: / Line 5: @@
 RFS-3362 - Enhancement - Performance improvements with queries which contained aggregation hierarchies that resulted in large amounts of data. A configurable series count threshold now guards aggregation. When a query matches more series than the threshold, aggregate series are no longer computed and only the underlying raw leaf series are returned. Callers that need the full aggregate response can opt in using detail=forceAggregates. The threshold is set with the system property aggregation.query.limit, default 10000. A new web service, GET /ws/public/aggregation /dataflow?urn=, reports whether a dataflow has aggregates and the effective limit, and the Data web service view now warns when the current query exceeds it. [[Auto_Aggregate_items_using_hierarchies#Parameter_detail.3DforceAggregates | Click here to read more]]. This can also be set when the Registry starts up [[Aggregations-_Series_Threshold| read more]].
-RFS-3352
+RFS-3054 - Bug Fix - Kafka startup replay now resumes from the correct most recent sent transaction, so the Registry stays responsive after a restart. Support Reference - SUP-405103
 =Release R2.0.0.00_RFS_28.08.26 Released August 28, 2026=

@@ Line 1: / Line 1: @@
 [[Category:Fusion Data Browser]]
 __NOTOC__
 ==Release R2.0.0.00_RFS_28.08.26 Released August 28, 2026==
 RFS-1813 - New Feature - New loading wheel which will appear when large datasets are being loaded. Support Reference - SUP-284855

@@ Line 2: / Line 2: @@
 [[Category:ChangeLogFR]]
 __NOTOC__
 =Release R2.0.0.00_RFS_28.08.26 Released August 28, 2026=
 RFS-2590 - New Feature from Opensource codebase - FMR-947 - New web service Database Consistency Checker. More information can be found in the Media Wiki Knowledgebase. [[Database_Consistency_Web_Service|Read More.]]

@@ Line 4: / Line 4: @@
 '''Fusion Data Browser''' - filters now follow the Dimension order as defined by the DSD.
-'''Fusion Registry''' - behavioural change with Aggregations. [[Auto_Aggregate_items_using_hierarchies#Parameter_detail.3DforceAggregates | click here to read more]]. This can also be set when the Registry starts up [[Aggregations-_Series_Threshold| read more]].
+'''Fusion Registry''' - behavioural change with Aggregations. [[Auto_Aggregate_items_using_hierarchies#Parameter_detail.3DforceAggregates | Click here to read more]]. This can also be set when the Registry starts up [[Aggregations-_Series_Threshold| read more]].
 Please refer to the change logs and Release Notes for more information.
 == Compatibility ==
-Image coming soon.
+[[File:Compatibility-sept2026.png|800px]]
 == Upgrade Instructions ==

@@ Line 78: / Line 78: @@
 |-
 | aggregation.series.threshold  || 500000 || Sets the limit for aggregated series. Keep in mind that increasing this value can have an impact on performance during data load/hierarchy association or hierarchy change.
 |-
 | HCL_OUTPUT_PERMIT_ALIAS_REF || false || Determine how Hierarchical Codelists should be output.<p>Fusion Registry version 10 only and since version 10.9.4.<p>[[Hierarchical_Codelists_Output_Format| Hierarchical Codelist Output]]
 |}

@@ Line 27: / Line 27: @@
 '''Important'''
-As from Release H2.0.0.01 (due to be released at the end of September 2026, Aggregate series are now only calculated automatically when the number of matching series is within a configurable limit (default 10,000). Queries above that limit return the underlying series without aggregates.
+As from Release H2.0.0.01 (due to be released at the end of September 2026), Aggregate series are now only calculated automatically when the number of matching series is within a configurable limit (default 10,000). Queries above that limit return the underlying series without aggregates.
 ==Parameter detail=forceAggregates==

← Older revision		Revision as of 08:59, 24 September 2026
(2 intermediate revisions by the same user not shown)
Line 27:		Line 27:

	'''Important'''		'''Important'''
−	As from Release H2.0.0.01 (due to be released at the end of September 2026, Aggregate series are now only calculated automatically when the number of matching series is within a configurable limit (default 10,000). Queries above that limit return the underlying series without aggregates. The full aggregate response can still be requested explicitly using the detail=forceAggregates parameter. The Data web service screen warns when a query exceeds the limit.	+	As from Release H2.0.0.01 (due to be released at the end of September 2026, Aggregate series are now only calculated automatically when the number of matching series is within a configurable limit (default 10,000). Queries above that limit return the underlying series without aggregates.
		+
		+	==Parameter detail=forceAggregates==
		+	The full aggregate response can still be requested explicitly using the detail=forceAggregates parameter. The Data web service screen warns when a query exceeds the limit.
		+
		+	When a data query that would normally produce hierarchy aggregates matches more series than a configured threshold, the system will not compute or return aggregate series by default. Instead it will return the underlying raw leaf series only. Callers that genuinely need the full aggregate response can opt in with detail=forceAggregates. The threshold is configurable via a JVM system property.
		+
		+	The default number of series is 10,000 but can be changed, click here [[System_Properties \|to read more.]]

@@ Line 2: / Line 2: @@
 '''Key Features'''
-Fusion Data Browser - filters now follow the Dimension order as defined by the DSD.
+'''Fusion Data Browser''' - filters now follow the Dimension order as defined by the DSD.
-Fusion Registry - behavioural change with Aggregations.
+'''Fusion Registry''' - behavioural change with Aggregations. When a data query that would normally produce hierarchy aggregates matches more series than a configured threshold, the system will not compute or return aggregate series by default. Instead it will return the underlying raw leaf series only. Callers that genuinely need the full aggregate response can opt in with detail=forceAggregates. The threshold is configurable via a JVM system property.
 Please refer to the change logs and Release Notes for more information.

@@ Line 1: / Line 1: @@
 __NOTOC__
-Please refer to the Change Log(s) and Release Notes for more detail.
+=Next Release=
-==P2.0.1.00 Estimated Release Date September 2026 - Patch ==
+Optimisations for granular and Microdata plus customer driven fixes and enhancements and security updates.

← Older revision		Revision as of 16:43, 23 September 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
		+	=September 2026 H2.0.0.01=
		+	'''Key Features'''
		+
		+	Fusion Data Browser - filters now follow the Dimension order as defined by the DSD.
		+
		+	Fusion Registry - behavioural change with Aggregations.
		+
		+	Please refer to the change logs and Release Notes for more information.
		+
	=August 2026 R2.0.0.00=		=August 2026 R2.0.0.00=

← Older revision		Revision as of 16:31, 23 September 2026
Line 25:		Line 25:

	[[File:Aggregate - WS.png \|Aggregation in Web Services\|800px]]<br>		[[File:Aggregate - WS.png \|Aggregation in Web Services\|800px]]<br>
		+
		+	'''Important'''
		+	As from Release H2.0.0.01 (due to be released at the end of September 2026, Aggregate series are now only calculated automatically when the number of matching series is within a configurable limit (default 10,000). Queries above that limit return the underlying series without aggregates. The full aggregate response can still be requested explicitly using the detail=forceAggregates parameter. The Data web service screen warns when a query exceeds the limit.