6.1
1. Added the BI Parameter tab page. The parameter settings previously on the General tab page have been moved to this new tab.
2. Added parameter restrictions: Number of Components in Dashboard, Number of Calculation Fields Added to Component, Number of Nested Levels in DEF Formula, Number of Complex Calculation Steps in Direct-Connected Self-Service Dataset, Number of Extraction Lineage Levels, Number of Direct-Connection Lineage Levels, Scheduled Update Frequency, Number of Cells in Extracted Self-Service Dataset, and Data Volume During Subject Edit.
FineBI provides the functions of configuring BI parameters and tuning parameters in System Management, enabling personnel responsible for system administration and project implementation to understand the system configuration conveniently and to set the parameters quickly. Log in to the FineBI system as the admin, choose System Management > System Setting > BI Parameter, and you can see the configuration page of BI parameters and extraction parameters, as shown in the following figure.
Data Type Identification
1. Regardless of whether the parameter is enabled or not, fields containing decimal places are always recognized as the value type.
2. When the parameter is not enabled, the fields with more than 15 digits will be recognized as the text type, while those with 15 or fewer digits will be recognized as the value type.
3. When the parameter is enabled, fields are always recognized as the value type (double), whose effective precision is 15 digits (2^52). Therefore, precision loss may occur on the fields with more than 15 digits. After the parameter is enabled, the data tables may need to be rebuilt.
4. Tables added without enabling the parameter:
If the table has not been edited, after enabling the parameter and restarting FineBI, you will find that the fields are recognized as the value type when you enter the table editing page. You can just resave the table.
If the table has been edited, after enabling the parameter and restarting FineBI, you will find that the fields are still recognized as the text type and will not be recognized as the value type when you enter the table editing page.
Close
Yes
SQL Parameter and Filter Function Effective for Widget
Whether the function of binding widgets to SQL parameters and the filtering function can take effect at the same time.
No
Chinese Sort
For FineBI 6.1 (with storage-computing separation) deployed through FineOps, this configuration is invalid.
Modify the configuration of engine-related components for projects in Component Management of FineOps: Modifying Component Configuration.
Whether to rank data by Chinese.
This parameter is disabled by default, indicating not to rank data by Chinese.
When the parameter is enabled, data needs to be re-extracted for distributed tables.
For details, see section "Notes" of Sorting.
Smart Data Explanation
When the parameter is enabled, the system intelligently selects dimensions for interpretation.
Spark Log Output Level
Spark log output level, standard output stream. Spark logs are outputed in the catalina.out file of Tomcat or nohup file of BI, options: INFO, WARN, ERROR, DEBUG.
INFO: print error and basic execution logs
WARN: print a warning or prompt information
ERROR: only print error logs
DEBUG: print all logs
INFO
Manual Preview Reminder
This parameter is in seconds. The default value is empty, which indicates that the parameter is not enabled.
After the parameter is configured, if the query time of components for requesting data exceeds the set value, the system will advise users to enable the manual preview function, but the function will not be forcibly enabled. The manual preview function lowers the query pressure on the engine.
This parameter takes effect immediately after being configured (without a restart).
NULL
Default Update Settings for Self-service Dataset
Whether the self-service dataset single table updates with the parent table.
For details, see Single Table Update of Self-Service Datasets.
Update with the parent table.
Update High Performance Time Interval
There is no limit to the number of update resource pool cores occupied during the configured time period.
In order not to affect users, it is recommended to configure the parameter to a time period when the system is unused and update tasks are frequent.
Active Period of Accessed Dataset
The continuous active period after the dataset is accessed.
A dataset with one of the following two situations is considered active:
● Dashboards/components consisting of the dataset have been edited or accessed within X days.
● The sub-tables of the dataset are active.
Unit: day
14
Active Period of Created Dataset
The continuous active period after the dataset is created.
The data set created within x days will be considered active, and if it exceeds x days, it will be considered inactive.
7
Global Check Time of Dataset Activity
The check time for judging the active state of the data set, at which time the access and creation of the data set will be checked uniformly, and its active state will be refreshed, so that some datasets will not be extracted.
Available options are:
Check at Fixed Time: checks every day at XXX o'clock, with the format of hh:mm:ss.
Check Before Global Update Schedule Task
Check at Fixed Time
00:00:00
Data Access Volume
This parameter limits the number of data rows that can be read into the server memory. In scenarios involving large data volume calculations, not all data necessarily needs to be read into the memory. FineBI Spider engine has intelligent memory usage strategies, such as:
If the data rows after grouping and summarizing exceed the set value, the calculation in the component/dashboard will be interrupted.
If the data rows of the associated field in the small table during Join exceed the set value, the calculation in the component/dashboard will be interrupted.
If this parameter is set to a value that is too small, the computation accuracy will be influenced.
If the set value large, there will be a risk of downtime.
Unit: row
Configurable range: 0 - 10,000,000
Recommended configurable range: 10,000 – 1,000,000. You are advised to keep the default value.
1000000
Data Volume During Subject Edit
This parameter limits the volume of data processed in real time during data edit at each subject (default volume:10,000,000). This parameter takes effect without a restart.
Configurable range: [100000 - 10000000]
If you need to adjust the upper limit, you can contact technical support to modify the configuration file in FineDB.
10000000
Direct Connection Query Timeout
When there are too many components, leading to long query times, or when a single component has a long query time that blocks subsequent BI requests, users may mistake this for a product outage.
To solve the problem, you can set a direct query timeout. All direct data queries will be suspended after a timeout to prevent abnormally slow queries from blocking other normal queries.
The component returned an error: "Component query time exceeds {} minutes, query is interrupted."
Unit: second
Recommended configurable range: 10 – 300
Effect scope: All BI direct query requests except for those querying table structures.
180
Number of Direct-Connection Lineage Levels
This parameter limits the maximum lineage levels of the direct-connected dataset to prevent the generated SQL statement from being too complex, which will affect the dashboard loading speed.
Configurable range:2 – 6.
3
Number of Complex Calculation Steps in Direct-Connected Self-Service Dataset
This parameter limits the number of complex calculation steps in the direct-connected self-service dataset to prevent the generated SQL statement from being too complex, which will consume a large amount of memory and CPU during calculation.
The complex calculation steps include Join, adding columns from other tables, adding summary columns, converting rows to columns, and converting columns to rows.
Configurable range: 0 – 2.
2
Extraction Query Timeout
To solve the problem, you can set an extraction query timeout. All extract data queries will be terminated after a timeout to prevent abnormally slow queries from blocking other normal queries.
45
Number of Extraction Lineage Levels
This parameter limits the upper quantity limit of extraction dataset lineage levels to prevent the generated SQL statements from being too complex, which will reduce the dashboard loading speed from being affected.
Configurable range: 2 – 16.
16
Number of Nested Levels in DEF Formula
This parameter limits the maximum nested levels of the DEF function in the formula to prevent the generated SQL statement from being too complex and the calculation from taking too long time (affecting the dashboard loading speed). This parameter takes effect without a restart.
Configurable range: 0 – 4.
4
Number of Calculation Fields Added to Component
This parameter limits the maximum number of calculation fields that can be added to a single component's analysis area to prevent the performance of parsing multiple formulas from being affected.
Unlimited
Number of Components in Dashboard
This parameter limits the maximum number of components in a single dashboard to prevent high database query concurrency due to excessive SQL queries delivered during single-dashboard access.
Scheduled Update Frequency
This parameter limits the scheduled update frequency set for a single dataset to prevent excessive system load caused by high update frequency of business settings.
Unit: minute
Number of Cells in Extracted Self-Service Dataset
This parameter limits the number of cells in the final result of the extracted self-service dataset to avoid excessive disk space usage and slow extraction updates.
Data Volume Limit on Excel Export
After setting this parameter, when users export Excel files, if the data volume in the Excel file exceeds the limit, an error will be reported.
Unit: cell (row x column)
Configurable range: 0 – 2,000,000,000
Recommended configurable range: 0 – 1,000,000,000
Available Disk Space Upon Excel Export
When you export an Excel file, a disk space check is performed and the export behavior will be interrupted when the disk space is less than the limit value. This can avoid downtime caused by full disk space.
If the limit is triggered, the export will fail, and the system will prompt: "The current exported data volume is too large and there is not enough disk space. The system protection mechanism has been triggered, and the export is interrupted. Please clear the disk space in time, limited by [Excel Export Disk Space Check] parameter, disk space limit:{R1}G".
Configurable range: 5 – unlimited
5
Concurrent Thread Quantity Limit Upon Detail Table Export
When multiple users export Excel files with large data volume at the same time, the number of concurrent threads may exceed the limit and affect user experience. Therefore, you can use the parameter to set the number of users who can export the detailed tables simultaneously. If this limit is exceeded, business personnel have to wait.
Configurable range: 1 – 10
Recommended configurable range: 1 – 5. You are advised to keep the default value.
For details, see BI Cache.
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy