DataWind supports filtering of data source data to retain only a portion of eligible data. This article will show you how to perform data filtering on datasets.
Support the dataset Model Configuration before and after the configuration of data filtering, after the configuration of data filtering, the dataset will only be synchronized to meet the filter conditions.
Data Filter Category | Filter objects | Support mode | Usage scenario |
|---|---|---|---|
Before model configuration | Filter fields of a single table before join or union | Direct connection and extraction | When there is a large amount of redundant information unrelated to business in the original single table data, the single table can be filtered before multi-table association or merging. This can reduce the amount of data for subsequent correlation operations, improve the efficiency of model configuration, and avoid the interference of irrelevant data on subsequent analysis. |
After model configuration | Filter the data model generated after join or union (supports filtering results of non-aggregated expressions across data sources) | Extraction only | After completing the model configuration of the dataset, the amount of data is very large, but the actual business does not need the full amount of data. At this time, the required data can be filtered through data filtering, reducing the amount of data, improving query performance, and saving storage space. |
The data filtering function can be configured when creating a new dataset, or when editing an existing dataset.
Direct Connection Mode:
Before model configuration | After model configuration | |
|---|---|---|
New dataset | Create a new dataset, enter the model configuration page, drag and drop the required data table to the right canvas, and click on the data table to see the "Data Filtering" function in the configuration area below. | In direct connection mode, filtering of data after model configuration is not supported. tip Direct-connected mode does not store intermediate data after model configuration, while extraction mode stores intermediate results locally, so only extraction mode supports such filtering. |
Existing dataset | Edit the dataset, enter the model configuration page, and click on any data table that needs to be filtered to see the "Data Filtering" function in the configuration area below. | In direct connection mode, filtering of data after model configuration is not supported. tip Direct-connected mode does not store intermediate data after model configuration, while extraction mode stores intermediate results locally, so only extraction mode supports such filtering. |
Extraction mode:
Before model configuration | After model configuration | |
|---|---|---|
New dataset | Create a new dataset, enter the model configuration page, drag and drop the required data table to the right canvas, and click on the data table to see the "Data Filtering" function in the configuration area below. | Create a new dataset, enter the model configuration page, and click the "Data Filter" icon in the upper right corner to configure the filter conditions in the pop-up data filter configuration pop-up window. |
Existing dataset | Edit the dataset, enter the model configuration page, and click on any data table that needs to be filtered to see the "Data Filtering" function in the configuration area below. | Edit the dataset, enter the model configuration page, and after completing the model configuration modification operation, click the "Data Filter" icon in the upper right corner to configure the filter conditions in the pop-up data filter configuration pop-up window. |
Filtering before model configuration is data filtering for a single data table.
Direct connection mode: Only "field filtering" for a single table is supported, and only "and" relationships are supported between multiple conditions. Each condition contains field, Operator, and value. For example: Primary Channel = Marketing Campaign.
Extraction mode: Only single table "field filtering" is supported, including partitioned field filtering and non-partitioned field filtering, and only "and" relationships are supported between multiple conditions.
tip
Partitioning is a mechanism for splitting a large data table into smaller, independently manageable subtables (called "partitions") according to specific rules (such as time, geography, class, etc.). These subtables are still logically part of the same table, but may be physically stored in different locations for efficient querying and data management.
Extraction Mode Field Filter Type | Introduction |
|---|---|
Partition filtering | For the extracted dataset, when the dataset model, the data source table with partition, click on the table node, you can find the "partition filter" option in the data filter.
tip When the following system date variables are introduced, dynamic date queries are implemented: |
Non-partitioned filtering | For extracted datasets, click on the table node of any data source to find the "Non-Partition Filtering" option in the data filter.
|
Hover over the condition and click "Delete" behind the condition to delete the condition.
Filtering after model configuration is to filter against the configured data model, and to support filtering of non-aggregated expression results across data sources.
warning
The directly connected dataset does not support filtering after model configuration, only the extracted dataset supports it.
Hover over the condition and click "Delete" behind the condition to delete the condition.
Field type | Operator list |
|---|---|
String | =, ≠, IN, NOT IN, LIKE, NOT LIKE, empty, not empty, empty string, not empty string, contain, not contain. |
Numerical value | =, ≠ 、>、<、>=、<=、 IN, NOT IN, empty, not empty, interval, not in interval. warning If you select "Interval" or "Not in Interval", you also need to specify whether the interval boundary is open or closed. |
Date | You can choose a fixed date within a range or a single date. |