Data view configuration method and device, electronic equipment and storage medium

Abstract

The invention provides a data view configuration method and device, electronic equipment and a storage medium, and the data view configuration method comprises the steps: obtaining a data source type, a first data source interface function description and a second data source interface function description; and instantiating the strategy class described by the first data source interface function and the strategy class described by the second data source interface function, obtaining a required data source based on the instantiated strategy class described by the first data source interface function, determining screening data from the data source according to a pre-configured operation authority, packaging the screening data, and storing the packaging data in a database. Obtaining a data view, previewing the data view, and performing configuration operation on data nodes in the data view to obtain configuration data; according to the method and the device, the data source can be flexibly acquired and the data view can be flexibly configured according to requirements, so that the condition that the data view is configured by adopting a customized development mode is avoided, and the defects caused by the customized development mode are overcome.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data view configuration method, device, electronic device, and storage medium. Background Art

[0002] Data view is a core concept in a database or data management system. It is used to organize and display data in a specific way to meet user query, analysis or reporting needs during the operation of the data view.

[0003] At present, systems in various fields often have the need to query business data instantly and efficiently and to perform secondary integration of business data. However, the requirements for business data integration of systems in various fields are different, and the sources of business data are diverse. Customized development is often required to meet these requirements. However, customized development has the disadvantages of high cost and long cycle, and changes in requirements affect system redeployment, which increases the cost of subsequent operation and maintenance. Therefore, it is necessary to improve the data view configuration method in related technologies. Summary of the Invention

[0004] In view of the above-mentioned shortcomings of the prior art, the present application provides a data view configuration method, device, electronic device and storage medium to solve the above-mentioned technical problems.

[0005] According to one aspect of an embodiment of the present application, a data view configuration method is provided, the method comprising: obtaining a data source type, a first data source interface functional description, and a second data source interface functional description; the data source type is determined by different databases; the first data source interface functional description comprises obtaining a structured query language structure, obtaining a table structure, obtaining a database table list, and obtaining a database list; the second data source interface functional description comprises generating a data preview; based on the data source type, instantiating a policy class of the first data source interface functional description and an instantiating a policy class of the second data source interface functional description; based on the instantiated policy class of the first data source interface functional description, obtaining a required data source and determining filtered data from the data source according to pre-configured operation permissions, encapsulating the filtered data, and obtaining a data view; previewing the data view through the instantiated policy class of the second data source interface functional description, and performing configuration operations on data nodes in the data view on a preset visualization page to obtain configuration data; the configuration operations comprise dragging and / or connecting.

[0006] In one embodiment of the present application, the process of instantiating the policy class of the first data source interface function description and the policy class of the second data source interface function description according to the data source type includes: configuring a unique identifier of the data source type; configuring a structured query language of the first data source interface function description according to the unique identifier, and constructing a policy class access interface of the first data source interface function description through a bytecode operation library to complete the instantiation of the policy class of the first data source interface function description; the structured query language of the first data source interface function description is part of the execution program of the policy class access interface of the first data source interface function description; configuring a structured query language of the second data source interface function description according to the unique identifier, and constructing a policy class access interface of the second data source interface function description through a bytecode operation library to complete the instantiation of the policy class of the second data source interface function description; the structured query language of the second data source interface function description is part of the execution program of the policy class access interface of the second data source interface function description.

[0007] In one embodiment of the present application, based on the instantiation strategy class of the first data source interface functional description, the process of obtaining the required data source includes: according to the unique identifier of the data source type, creating a data view through a preset connection pool to configure the physical connection channel between the application and the target database; the protocol adapter of the physical connection channel is loaded through a service discovery provision mechanism; the heartbeat detection message format of the physical connection channel follows the network transmission specification of the data source type; the instantiation strategy class of the first data source interface functional description obtains the data source and supplementary data source corresponding to the data source type through the physical connection channel; the supplementary data source is configured through the configuration center; the data source corresponding to the data source type and the supplementary data source are used as the required data source.

[0008] In one embodiment of the present application, a configuration operation is performed on the data node in the data view on a preset visualization page, and the process of obtaining the configuration data includes: obtaining the type of the data node; if the type of the data node is a data table node, dragging the data table node to the preset visualization page, selecting the required data field by checking the data field in the data table node, connecting the data fields in different data table nodes by dragging and dropping, and combining the data fields in the connected data table nodes to obtain the configuration data; the combination method includes left join or inner join; if the type of the data node is a structured query language execution node, running the structured query language execution statement corresponding to the structured query language execution node to obtain the required data field, connecting the data fields in different structured query language execution nodes by dragging and dropping, and combining the data fields in the connected structured query language execution nodes to obtain the configuration data.

[0009] In one embodiment of the present application, after obtaining the configuration data, the method further includes: if the type of the data node is a data table node, extracting the physical storage information in the configuration data, the data field connection relationship and combination relationship between the data table nodes, generating multiple standard identifiers based on the field name in the physical storage information and the table alias to which the field name belongs, splicing the multiple standard identifiers to obtain a query field; generating a connection clause for the connection relationship and the combination relationship through an abstract syntax tree parser, splicing the query field and the connection clause to obtain a first structured query language statement, running the first structured query language statement to obtain query data; if the type of the data node is a structured query language execution node, extracting the data field connection relationship and combination relationship between the data table nodes in the configuration data, parsing the query data through an abstract syntax tree The processor generates a join clause from the join relationship and the combination relationship to obtain a second structured query language statement. The second structured query language statement is parsed by the abstract syntax tree parser to obtain an abstract syntax tree. The nodes in the abstract syntax tree are recursively traversed to verify the execution statement type, the number of query statements, the subquery nesting depth, and the number of connection tables in the second structured query language statement. If the execution statement type, the number of query statements, the subquery nesting depth, and the number of connection tables all meet the verification requirements, the placeholder tag in the second structured query language statement is parsed by the abstract syntax tree parser, and a filtering parameter at the placeholder tag is obtained through a type-safe parameter. The second structured query language statement is executed based on the filtering parameter to obtain query data, where the filtering parameter is derived from the preset visualization page.

[0010] In one embodiment of the present application, after obtaining the second structured query language statement, the method further includes: calculating a hash key of the second structured query language statement, using the hash key as a key value of the structured query language execution node, locally storing the preview data and execution risk verification results of the structured query language execution node, and obtaining cached data of the structured query language execution node; using the unique identifier of the data view as a key value, locally storing the preview data of the data view, and obtaining cached data of the data view.

[0011] In one embodiment of the present application, if the second data source interface function description includes: full data preview and paginated data preview, then the process of previewing the data view through the instantiation strategy class of the second data source interface function description includes: running a full data preview structured query language statement in the instantiation strategy class of the second data source interface function description to obtain data fields and data in the data view, returning the data fields and data of the data view to the preset visualization page via the hypertext transfer protocol, and rendering the data fields and data of the data view through the visualization engine of the preset visualization page to achieve preview of the data view; or running a paginated data preview structured query language statement in the instantiation strategy class of the second data source interface function description to obtain data fields and data in the data view, returning the data fields and data of the data view to the preset visualization page via the hypertext transfer protocol, and rendering the data fields and data of the data view through the visualization engine of the preset visualization page to achieve preview of the data view.

[0012] According to one aspect of an embodiment of the present application, a data view configuration device is provided, comprising: an interface definition module, configured to obtain a data source type, a first data source interface functional description, and a second data source interface functional description; the data source type is determined by different databases; the first data source interface functional description includes obtaining a structured query language structure, obtaining a table structure, obtaining a database table list, and obtaining a database list; the second data source interface functional description includes generating a data preview; an interface instantiation module, configured to instantiate a policy class of the first data source interface functional description and a policy class of the second data source interface functional description based on the data source type; a data encapsulation module, configured to obtain a required data source based on the instantiated policy class of the first data source interface functional description, determine filtered data from the data source based on pre-configured operation permissions, encapsulate the filtered data, and obtain a data view; and a view configuration module, configured to preview the data view using the instantiated policy class of the second data source interface functional description, and perform configuration operations on data nodes in the data view on a preset visualization page to obtain configuration data; the configuration operations include dragging and / or connecting.

[0013] According to one aspect of an embodiment of the present application, an electronic device is provided, comprising: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the electronic device implements the data view configuration method described above.

[0014] According to one aspect of an embodiment of the present application, a computer-readable storage medium is provided, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor of a computer, the computer executes the data view configuration method as described above.

[0015] The beneficial effects of the present application are as follows: the present application obtains the data source type, the first data source interface function description and the second data source interface function description, and instantiates the policy class of the first data source interface function description according to the data source type, and instantiates the policy class of the second data source interface function description. Based on the instantiated policy class of the first data source interface function description, the required data source is obtained and, according to the pre-configured operation permissions, the filtered data is determined from the data source, the filtered data is encapsulated to obtain a data view, and the data view is previewed through the instantiated policy class of the second data source interface function description, and the data nodes in the data view are configured on the preset visualization page to obtain the configuration data. In the above process, the required data source can be obtained through the instantiated policy class of the first data source interface function description, and the data nodes in the data view can be configured on the preset visualization page. The data source can be flexibly obtained and the data view can be flexibly configured according to needs, avoiding the configuration of the data view in a customized development manner, and overcoming the defects brought by the customized development manner.

[0016] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The accompanying drawings are incorporated into and constitute a part of the specification, illustrating embodiments consistent with the present application and, together with the specification, serving to explain the principles of the present application. It is obvious that the drawings described below are merely some embodiments of the present application, and a person of ordinary skill in the art can derive other drawings based on these drawings without inventive effort. In the drawings:

[0018] Figure 1 is a schematic diagram of an exemplary system architecture shown in an exemplary embodiment of the present application;

[0019] Figure 2 is a flow chart of a data view configuration method shown in an exemplary embodiment of the present application;

[0020] Figure 3 is a flow chart of a data view configuration method shown in another exemplary embodiment of the present application;

[0021] Figure 4 A block diagram of a data view configuration device suitable for implementing an embodiment of the present application is shown;

[0022] Figure 5 is a block diagram of a data view configuration device shown in another exemplary embodiment of the present application;

[0023] Figure 6A schematic diagram of the structure of a computer system suitable for implementing an electronic device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0024] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. When the following description refers to the drawings, identical numerals in different figures represent identical or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0025] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0026] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, while others may be combined or partially combined. Therefore, the actual execution order may vary depending on the actual situation.

[0027] In this application, "plurality" refers to two or more. "And / or" describes the relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.

[0028] The technical solutions of the embodiments of this application involve related technologies such as material loading and unloading management, and are specifically described through the following embodiments:

[0029] Figure 1 It is a schematic diagram of an exemplary system architecture shown in an exemplary embodiment of the present application.

[0030] Reference Figure 1As shown, the system architecture may include a storage device 101 and a computer device 102. The computer device 102 may be at least one of a desktop graphics processing unit (GPU) computer, a GPU computing cluster, a neural network computer, and the like. Relevant technicians may use the computer device 102 to obtain a data source type, a first data source interface functional description, and a second data source interface functional description. Based on the data source type, the policy class of the first data source interface functional description is instantiated, and the policy class of the second data source interface functional description is instantiated. Based on the instantiated policy class of the first data source interface functional description, the required data source is obtained, and based on pre-configured operation permissions, filtered data is determined from the data source, the filtered data is encapsulated, and a data view is obtained. The data view is previewed through the instantiated policy class of the second data source interface functional description, and configuration operations are performed on data nodes in the data view on a preset visualization page to obtain configuration data. The storage device 101 is used to store the data source type, the first data source interface function description, and the second data source interface function description. In this embodiment, the storage device 101 uses a random access memory (RAM) or the like to store the data source type, the first data source interface function description, and the second data source interface function description, and provides them to the computer device 102 for processing.

[0031] Schematically, after obtaining the data source type, the first data source interface function description, and the second data source interface function description of the storage device 101, the computer device 102 instantiates the policy class of the first data source interface function description according to the data source type, and instantiates the policy class of the second data source interface function description. Based on the instantiated policy class of the first data source interface function description, the required data source is obtained and, according to the pre-configured operation permissions, the filtered data is determined from the data source, the filtered data is encapsulated to obtain a data view, and the data view is previewed through the instantiated policy class of the second data source interface function description, and the data nodes in the data view are configured on the preset visualization page to obtain configuration data. In the above process, the required data source can be obtained through the instantiated policy class of the first data source interface function description, and the data nodes in the data view can be configured on the preset visualization page. The data source can be flexibly obtained and the data view can be flexibly configured according to needs, avoiding the configuration of the data view in a customized development manner, thereby overcoming the defects brought by the customized development manner.

[0032] It should be noted that the data view configuration method provided in the embodiment of the present application is generally executed by the computer device 102 , and accordingly, the data view configuration apparatus is generally provided in the computer device 102 .

[0033] The following is a detailed description of the implementation details of the technical solution of the embodiment of the present application:

[0034] Figure 2 is a flowchart of a data view configuration method according to an exemplary embodiment of the present application. The data view configuration method can be executed by a computing processing device. The computing processing device can be Figure 1 The computer device 102 shown in FIG. Figure 2 As shown, the data view configuration method includes at least steps S210 to S240, which are described in detail as follows:

[0035] In step S210, the data source type, the first data source interface function description, and the second data source interface function description are obtained. In one embodiment of the present application, the data source type is determined by different databases, including MySQL (My Structured Query Language) databases, Oracle databases, SQL Server databases, etc. The first data source interface function description includes obtaining a structured query language structure, obtaining a table structure, obtaining a database table list, and obtaining a database list; the second data source interface function description includes generating a data preview, which includes a full data preview and a paged data preview.

[0036] In step S220, the policy class of the functional description of the first data source interface is instantiated according to the data source type, and the policy class of the functional description of the second data source interface is instantiated. In one embodiment of the present application, the process of instantiating the policy class of the functional description of the first data source interface according to the data source type includes: configuring a unique identifier of the data source type; configuring a structured query language of the functional description of the first data source interface according to the unique identifier, and constructing a policy class access interface of the functional description of the first data source interface through a bytecode operation library to complete the instantiation of the policy class of the functional description of the first data source interface; configuring a structured query language of the functional description of the second data source interface according to the unique identifier, and constructing a policy class access interface of the functional description of the second data source interface through a bytecode operation library to complete the instantiation of the policy class of the functional description of the second data source interface. By instantiating the policy class of the functional description of the first data source interface, the function of the first data source interface is realized, and by instantiating the policy class of the functional description of the second data source interface, the function of the second data source interface is realized.

[0037] In step S230, based on the instantiation policy class of the first data source interface functional description, the required data source is obtained and, according to the pre-configured operation permissions, the filtered data is determined from the data source, the filtered data is encapsulated, and a data view is obtained. In one embodiment of the present application, based on the instantiation policy class of the first data source interface functional description, the process of obtaining the required data source includes: configuring a physical connection channel between the application and the target database through a preset connection pool based on the unique identifier of the data source type; loading the protocol adapter of the physical connection channel through a service discovery provision mechanism; the heartbeat detection message format of the physical connection channel complies with the network transmission specification of the data source type; the instantiation policy class of the first data source interface functional description obtains the data source and supplementary data source corresponding to the data source type through the physical connection channel; the supplementary data source is configured through a configuration center; the data source corresponding to the data source type and the supplementary data source are used as the required data sources, the target database includes a MySQL database, an Oracle database, a SQL Server database, or a database of the supplementary data source, etc. The database of the supplementary data source is a database pre-established by developers or technicians as needed (i.e., a custom database), and the instantiation policy class of the first data source interface functional description is used to obtain data from the MySQL database, Oracle database, SQL Server database, and the custom database.

[0038] In another embodiment of the present application, the pre-configured operation permissions are divided into permissions based on business categories and are set according to the needs of business personnel or organizations. After obtaining the filtered data, the data set composed of the filtered data is encapsulated as the minimum granularity to obtain a data view.

[0039] In step S240, the data view is previewed using the instantiated policy class described in the second data source interface function, and configuration operations are performed on the data nodes in the data view on a preset visualization page to obtain configuration data. In one embodiment of the present application, the data view can be managed in a multi-layer grouping tree structure, for example, and displayed in an organized data view format, facilitating instant viewing of data view information, data view structure fields, and data preview. The preset visualization page is a canvas page of a World Wide Web page (Web Page), and configuration operations include dragging and / or connecting.

[0040] In another embodiment of the present application, the required data source can be obtained through the instantiation strategy class described by the first data source interface function, and by configuring the data nodes in the data view on the preset visualization page, the data source can be flexibly obtained and the data view can be flexibly configured according to needs, avoiding the use of customized development to configure the data view, and overcoming the defects brought about by the customized development method.

[0041] In one embodiment of the present application, the process of instantiating the policy class of the first data source interface functional description and the policy class of the second data source interface functional description according to the data source type includes:

[0042] Configure a unique identifier for the data source type. In one embodiment of the present application, different databases correspond to different data source types, which are distinguished by unique identifiers, which are represented by numeric enumeration values. The process of configuring a unique identifier for a data source type can be completed in the Nacos (Dynamic Naming and Configuration Service) configuration management platform, or in other configuration management and service management platforms with equivalent functionality.

[0043] According to the unique identifier, a structured query language for the functional description of the first data source interface is configured, and a policy class access interface for the functional description of the first data source interface is constructed through a bytecode manipulation library to complete the instantiation of the policy class for the functional description of the first data source interface. In one embodiment of the present application, the structured query language for the functional description of the first data source interface is part of the execution program of the policy class access interface for the functional description of the first data source interface. According to the unique identifier, the process of configuring the structured query language for the functional description of the first data source interface includes: configuring the structured query language for the functional description of the first data source interface in Nacos according to the unique identifier and using a factory method and a policy pattern. The bytecode manipulation library can be ByteBuddy, or a Java Bytecode Manipulation Framework (Java Bytecode Manipulation Framework), Javassist, etc. The bytecode manipulation library allows dynamic creation and modification of Java classes at runtime, providing powerful bytecode manipulation capabilities for Java development.

[0044] Based on the unique identifier, a structured query language for the functional description of the second data source interface is configured, and a policy class access interface for the functional description of the second data source interface is constructed through a bytecode operation library to complete the instantiation of the policy class of the functional description of the second data source interface. In one embodiment of the present application, the structured query language for the functional description of the second data source interface is part of the execution program of the policy class access interface for the functional description of the second data source interface. The process of configuring the structured query language for the functional description of the second data source interface based on the unique identifier includes: configuring the structured query language for the functional description of the second data source interface in Nacos based on the unique identifier and using a factory method and a strategy pattern.

[0045] In one embodiment of the present application, based on the instantiation strategy class of the first data source interface functional description, the process of obtaining the required data source includes:

[0046] According to the unique identifier of the data source type, a physical connection channel between the data view configuration application and the target database is created through a preset connection pool. In one embodiment of the present application, the preset connection pool can be a HikariCP (HikariConnection Pool) connection pool or other connection libraries. The physical connection channel between the data view configuration application and the target database is created through the HikariCP (Hikari Connection Pool) connection pool. As a high-performance JDBC (Java Database Connectivity) connection pool component, the HikariCP connection pool can dynamically add new connections to the database. The protocol adapter of the physical connection channel is loaded through a service discovery provision mechanism. Service discovery (ServiceDiscovery) is one of the core mechanisms in a distributed system, which is used to solve the dynamic registration, positioning and routing problems of service instances. The heartbeat detection message format of the physical connection channel follows the network transmission specifications of the data source type. The network transmission specifications of the data source type include: HyperText Transfer Protocol (HTTP), HyperText Transfer Protocol Secure (HTTPS), etc.

[0047] The instantiation strategy class of the first data source interface functional description obtains the data source and the supplementary data source corresponding to the data source type through the physical connection channel. In one embodiment of the present application, the supplementary data source is configured through the configuration center, and the instantiation strategy class of the first data source interface functional description includes an instantiation strategy class for obtaining a structured query language structure, an instantiation strategy class for obtaining a table structure, an instantiation strategy class for obtaining a database table list, and an instantiation strategy class for obtaining a database list. The data source corresponding to the data source type obtained includes a structured query language structure, a table structure, a database table list, a database list, etc. The supplementary data source is a database (i.e., a custom database) pre-established by developers or technicians as needed. Before the instantiation strategy class of the first data source interface functional description obtains the data source and the supplementary data source corresponding to the data source type through the physical connection channel, a data source acquisition request is initiated on the preset visualization page, the data source acquisition request of the preset visualization page is received through the unified interface, and the instantiation strategy class of the first data source interface functional description is obtained according to the required data source type in the data source acquisition request.

[0048] The data source and the supplementary data source corresponding to the data source type are used as the required data source. In one embodiment of the present application, the required data source includes not only MySQL database, Oracle database, SQL Server database, but also a custom database, thereby enriching and expanding the data source.

[0049] In one embodiment of the present application, a process of performing a configuration operation on a data node in a data view on a preset visualization page to obtain configuration data includes:

[0050] Get the type of data node. In one embodiment of the present application, the types of data nodes include data table nodes and structured query language execution nodes, where a data table node refers to a basic unit used to represent or operate a data table in a data model, data flow diagram, ETL (Extract-Transform-Load) process, or database structure, and a structured query language (SQL) execution node refers to a key component in a database management system (DBMS) that receives SQL statements as input and ultimately returns query results or execution status by parsing, optimizing, and executing SQL statements.

[0051] If the type of the data node is a data table node, drag the data table node to the preset visualization page, select the required data field by checking the data field in the data table node, and connect the data fields in different data table nodes by dragging and dropping the connection line, and combine the data fields in the connected data table nodes to obtain the configuration data. In one embodiment of the present application, data driving is realized by the graph editing engine Antv-X6, and the data nodes are configured by dragging on the preset visualization page. The data table node can be directly selected as needed or a new SQL execution node can be created to perform secondary processing on the data. For the data table node, the database list can be switched at any time, and the switching of the data table node can be realized by dragging different data tables to the main canvas of the preset visualization page, and the node configuration area of ​​the preset visualization page displays all the fields in the data table and their detailed information in real time. The data field can be checked as needed, and the checked field and the data corresponding to the checked field are displayed in the data preview area. Refreshing the preview can view the configured data table node data in real time. The node configuration area of ​​the preset visualization page supports configuring multiple data table nodes according to needs. The combination methods include left join or inner join. Multiple data table nodes can be combined by left join or inner join as needed.

[0052] If the type of the data node is a structured query language execution node, the structured query language execution statement corresponding to the structured query language execution node is executed to obtain the required data fields, the data fields in different structured query language execution nodes are connected by dragging and dropping lines, and the data fields in the connected structured query language execution nodes are combined to obtain the configuration data. In one embodiment of the present application, for the SQL execution node, an SQL with a data field filtering function is input in the SQL input area of ​​the node configuration area. The SQL with the data filtering function uses placeholders in the #{placeholder name} manner. After the SQL with the data filtering function is completed, the required data fields in the SQL execution node and the filtered data are obtained, completing the filtering configuration of the SQL execution node; the node configuration area of ​​the preset visualization page supports the configuration of multiple SQL execution nodes according to needs, and the SQL execution nodes are combined with the data fields by selecting left join or inner join as needed.

[0053] In one embodiment of the present application, after obtaining the configuration data, the data view configuration method further includes:

[0054] If the data node type is a data table node, the physical storage information, the data field connection relationship and combination relationship between the data table nodes in the configuration data are extracted. Based on the field name and the table alias to which the field name belongs in the physical storage information, multiple standard identifiers are generated. The multiple standard identifiers are spliced ​​together to obtain the query field. The connection relationship and the combination relationship are generated into a join clause through an abstract syntax tree parser. The query field and the join clause are spliced ​​together to obtain a first structured query language statement. The first structured query language statement is executed to obtain the query data. In one embodiment of the present application, the physical storage information of the field is automatically extracted through the JDBC metadata interface. The physical storage information includes the field name and the table alias to which the field name belongs. Based on the field name and the table alias to which the field name belongs, multiple standard identifiers in the format of `table alias.field name` are generated. The multiple standard identifiers are spliced ​​together to obtain the query field, i.e., the SELECT field projection set.

[0055] If the type of the data node is a structured query language execution node, extract the data field connection relationship and combination relationship between the data table nodes in the configuration data, generate a connection clause from the connection relationship and combination relationship through an abstract syntax tree parser, and obtain a second structured query language statement. Parse the second structured query language statement through the abstract syntax tree parser to obtain an abstract syntax tree, recursively traverse the nodes in the abstract syntax tree, and verify the execution statement type, number of query statements, subquery nesting depth, and number of connection tables in the second structured query language statement. If the execution statement type, number of query statements, subquery nesting depth, and number of connection tables all meet the verification requirements, parse the placeholder tag in the second structured query language statement through the abstract syntax tree parser, obtain the filtering parameter at the placeholder tag through the type-safe parameter, and run the second structured query language statement based on the filtering parameter to obtain query data. In one embodiment of the present application, the screening parameters are derived from a preset visualization page, and the abstract syntax tree parser can be Druid's SQL parsing tool or other parsing tools. The Druid SQL parsing tool is used to parse the second structured query language statement generated based on the configuration data to obtain an abstract syntax tree. The nodes in the abstract syntax tree are recursively traversed to verify the execution statement type, the number of query statements, the subquery nesting depth, and the number of connection tables in the second structured query language statement. When the execution statement type, the number of query statements, the subquery nesting depth, and the number of connection tables all meet the verification requirements, the placeholder tags in the second structured query language statement are parsed by the abstract syntax tree parser, and the screening parameters at the placeholder tags are obtained through type-safe parameters. Based on the screening parameters, the second structured query language statement is run to obtain query data, thereby achieving the effect of controlling SQL execution risks. Druid (Druid Data Source) is a high-performance, powerful, and flexible database connection pool component with functions such as log monitoring, URL monitoring, and SQL monitoring, and is widely used in Java applications.

[0056] In one embodiment of the present application, after obtaining the second structured query language statement, the data view configuration method further includes:

[0057] A hash key of the second structured query language statement is calculated, the hash key is used as a key value for the structured query language execution node, and the preview data and execution risk verification results of the structured query language execution node are locally stored to obtain cached data of the structured query language execution node. In one embodiment of the present application, by using the hash key as a key value for the preview data and execution risk verification results of the structured query language execution node, the uniqueness of the preview data and execution risk verification results of the structured query language execution node is guaranteed when storing the preview data and execution risk verification results of the structured query language execution node, facilitating subsequent rapid retrieval and viewing of data such as the preview data and execution risk verification results of the structured query language execution node via the key value, thereby facilitating improved data processing speed.

[0058] The unique identifier of the data view is used as a key value to locally store the preview data of the data view, thereby obtaining cached data of the data view. In one embodiment of the present application, the unique identifier of the data view is used as a key value to locally store the preview data of the data view. This ensures the uniqueness of the preview data of the data view, facilitates rapid extraction and viewing of the preview data of the data view using the key value, and is conducive to improving data processing speed.

[0059] In one embodiment of the present application, if the second data source interface function description includes: previewing all data and previewing paged data, then the process of previewing the data view using the instantiated policy class of the second data source interface function description includes:

[0060] The entire data preview structured query language statement in the instantiated strategy class of the second data source interface functional description is executed to obtain the data fields and data in the data view. The data fields and data of the data view are returned to a preset visualization page via the Hypertext Transfer Protocol. The data fields and data of the data view are rendered by the visualization engine of the preset visualization page to achieve a preview of the data view. In one embodiment of the present application, before executing the entire data preview structured query language statement in the instantiated strategy class of the second data source interface functional description, a full data preview request is initiated via the preset visualization page, the full data preview request for the preset visualization page is received, and the entire data preview structured query language statement in the instantiated strategy class of the second data source interface functional description is executed based on the full data preview requirement in the full data preview request. The data in the data view is presented in a tabular structure, and all data in the data view is displayed to facilitate a preview of all data in the data view.

[0061] The paginated data preview structured query language statement in the instantiated strategy class of the second data source interface functional description is executed to obtain the data fields and data in the data view, and the data fields and data of the data view are returned to the preset visualization page via the hypertext transfer protocol. The data fields and data of the data view are rendered by the visualization engine of the preset visualization page to achieve a preview of the data view. In one embodiment of the present application, before executing the paginated data preview structured query language statement in the instantiated strategy class of the second data source interface functional description, a paginated data preview request is initiated via the preset visualization page, a paginated data preview request of the preset visualization page is received, and based on all data preview requirements in the paginated data preview request, the paginated data preview structured query language statement in the instantiated strategy class of the second data source interface functional description is executed, the data in the data view is presented in a tabular structure, and the paginated data display through the data view is advantageously used to improve the data query speed.

[0062] Figure 3 is a flowchart of a data view configuration method shown in another exemplary embodiment of the present application. Figure 3 As shown, the process of the data view configuration method includes: (1) creating a new data source connection: establishing a physical connection channel between the data view configuration application and the target database through the HikariCP connection pool; (2) creating a new data view: based on the instantiation strategy class of the first data source interface function description, obtaining the required data source and determining the filter data from the data source according to the pre-configured operation permissions, encapsulating the filter data, obtaining the data view and entering the data view configuration interface; (3) if the type of the data node is a data table node, selecting the data table node and selecting the data field in the data table node for preview, connecting the data fields in different data nodes to obtain the configuration data; (4) if it is necessary to perform secondary processing on the data view through the SQL execution node, creating a new SQL execution node, performing secondary processing on the data view by configuring the structured query language in the newly created SQL execution node, parsing and verifying the structured query language in the newly created SQL execution node, and if the verification passes, connecting the data fields in different SQL execution nodes to obtain the configuration data; (5) previewing the configuration data; (6) saving the data view and previewing the data.

[0063] In one embodiment of the present application, after configuring the structured query language in a newly created SQL execution node, operations such as compiling or precompiling the structured query language in the newly created SQL execution node are required to detect any errors or non-compliance with the syntax rules of the structured query language in the newly created SQL execution node. The process of parsing and validating the structured query language in the newly created SQL execution node can be implemented by referring to the methods for parsing and validating structured query language in SQL execution nodes in related arts.

[0064] This application implements dynamic connection and addition of data sources through online configuration, and can be flexibly configured and deployed according to changes in demand, avoiding the problem of redeployment caused by changes in demand due to customized hard-coding. It performs secondary processing on data views by dragging and dropping data nodes on the web page, combines data nodes in the data view through inner joins or left joins, and previews data fields using a visual representation of the data fields in the data nodes. It parses the abstract syntax tree through a Druid-based SQL parsing tool, checks and verifies the grammatical correctness, integrity, and security of the data view, and implements risk control of the data view. It locally caches the intermediate state verification results of the data node, the data view preview results, and the data view operation results to achieve efficient configuration and efficient operation of the data view. When supporting SQL native syntax, it can parse, verify, connect fields, and map fields to the SQL native syntax, thereby ensuring the real-time and timeliness of query data.

[0065] The following describes an apparatus embodiment of the present application, which can be used to execute the data view configuration method in the above-mentioned embodiment of the present application. For details not disclosed in the apparatus embodiment of the present application, please refer to the above-mentioned embodiment of the data view configuration method of the present application.

[0066] Figure 4 This is a block diagram of a data view configuration device shown in an exemplary embodiment of the present application. The device can be applied to Figure 1 The implementation environment shown is specifically configured in the computer device 102. The apparatus may also be applicable to other exemplary implementation environments and specifically configured in other devices. This embodiment does not limit the implementation environment to which the apparatus is applicable.

[0067] like Figure 4 As shown, the exemplary data view configuration device 400 includes:

[0068] The interface definition module 401 is used to obtain a data source type, a first data source interface function description, and a second data source interface function description.

[0069] The interface instantiation module 402 is used to instantiate the policy class of the first data source interface function description and the policy class of the second data source interface function description according to the data source type.

[0070] The data encapsulation module 403 is used to obtain the required data source based on the instantiation strategy class of the first data source interface functional description and determine the filtered data from the data source according to the pre-configured operation permissions, encapsulate the filtered data, and obtain the data view.

[0071] The view configuration module 404 is used to preview the data view through the instantiation strategy class described by the second data source interface function, and to configure the data nodes in the data view on a preset visualization page to obtain configuration data.

[0072] In one embodiment of the present application, the data source type is determined by different databases, including MySQL (My Structured Query Language) database, Oracle database, SQL Server database, etc.; the first data source interface function description includes obtaining structured query language structure, obtaining table structure, obtaining database table list, and obtaining database list; the second data source interface function description includes generating data preview, and generating data preview includes all data preview and paged data preview.

[0073] In one embodiment of the present application, the process of instantiating the policy class of the first data source interface function description according to the data source type includes: configuring a unique identifier of the data source type; configuring a structured query language of the first data source interface function description according to the unique identifier, and constructing a policy class access interface of the first data source interface function description through a bytecode operation library to complete the instantiation of the policy class of the first data source interface function description; configuring a structured query language of the second data source interface function description according to the unique identifier, and constructing a policy class access interface of the second data source interface function description through a bytecode operation library to complete the instantiation of the policy class of the second data source interface function description. By instantiating the policy class of the first data source interface function description, the function of the first data source interface is realized, and by instantiating the policy class of the second data source interface function description, the function of the second data source interface is realized.

[0074] In one embodiment of the present application, based on the instantiation strategy class of the first data source interface functional description, the process of obtaining the required data source includes: according to the unique identifier of the data source type, creating a data view through a preset connection pool to configure the physical connection channel between the application and the target database; the protocol adapter of the physical connection channel is loaded through the service discovery provision mechanism; the heartbeat detection message format of the physical connection channel follows the network transmission specification of the data source type; the instantiation strategy class of the first data source interface functional description obtains the data source and the supplementary data source corresponding to the data source type through the physical connection channel; the supplementary data source is configured through the configuration center; the data source corresponding to the data source type and the supplementary data source are used as the required data sources, and the target database includes a MySQL database, an Oracle database, an SQL Server database or a database of a supplementary data source, etc. The database of the supplementary data source is a database pre-established by developers or technicians according to needs (i.e., a custom database), and the acquisition of data in the MySQL database, Oracle database, SQL Server database and custom database is achieved through the instantiation strategy class of the first data source interface functional description.

[0075] In some embodiments of the present application, pre-configured operation permissions are divided by business classification and set according to the needs of business personnel or organizations. After obtaining the filtered data, the data set composed of the filtered data is encapsulated as the minimum granularity to obtain a data view.

[0076] Figure 5 is a block diagram of a data view configuration device shown in another exemplary embodiment of the present application. Figure 5As shown, the data view configuration device includes: a data source connection management module, a data view management module, a data view configuration module, and a data view execution module, wherein the data source connection management module is used to enter basic data source information (data source type, mainstream database name, etc.) and supplementary data source information (database name, acquisition path, etc.), and establish connections between the data view configuration application and the basic data source and supplementary data source through the HikariCP connection pool; the data view management module is used to, when the required data source is obtained, determine and filter data from the data source according to pre-configured operation permissions, encapsulate the filtered data, obtain a data view, and preview the data view; the data view configuration module is used to configure data table nodes, configure the structured query language in the newly created SQL execution node to perform secondary processing or data field selection on the data view, connect data fields in different data nodes, obtain configuration data, and preview the configuration data; the data view execution module is used to parse and verify the structured query language in the newly created SQL execution node based on the Druid SQL parsing tool, and if the verification passes, run the newly created SQL execution node, locally cache the parsing results and execution results of the newly created SQL execution node, and run the data view and locally cache the execution results.

[0077] In one embodiment of the present application, the preset visualization page of the data view includes four areas: a data node configuration area, a canvas area, an SQL input area, and a data preview area.

[0078] It should be noted that the data view configuration device provided in the above-described embodiment and the data view configuration method provided in the above-described embodiment share the same concept. The specific manner in which the various modules and units perform their operations has been described in detail in the method embodiments and will not be repeated here. In actual applications, the data view configuration device provided in the above-described embodiment can, as needed, allocate the aforementioned functions to different functional modules. This means that the internal structure of the device can be divided into different functional modules to perform all or part of the aforementioned functions. This is not a limitation herein.

[0079] An embodiment of the present application also provides an electronic device, comprising: one or more processors; a storage device for storing one or more programs, which, when executed by one or more processors, enables the electronic device to implement the data view configuration method provided in the above-mentioned embodiments.

[0080] Figure 6 The following is a schematic diagram showing the structure of a computer system suitable for implementing an electronic device according to an embodiment of the present application. Figure 6The computer system 600 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0081] like Figure 6 As shown, the computer system 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 602 or the program loaded from the storage part 608 into the random access memory (RAM) 603, such as executing the method in the above embodiment. Various programs and data required for system operation are also stored in the RAM 603. The CPU 601, ROM 602 and RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0082] The following components are connected to the I / O interface 605: an input section 606 including a keyboard, a mouse, and the like; an output section 607 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and a speaker; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN (Local Area Network) card or a modem. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. Removable media 611, such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, is installed in the drive 610 as needed, so that computer programs read therefrom can be installed into the storage section 608 as needed.

[0083] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 609, and / or installed from a removable medium 611. When the computer program is executed by the central processing unit (CPU) 601, the various functions defined in the system of the present application are executed.

[0084] It should be noted that the computer-readable medium shown in the embodiments of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, which carries a computer-readable computer program. This propagated data signal can take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. A computer program embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, or any suitable combination thereof.

[0085] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. Among them, each box in the flowchart or block diagram can represent a module, program segment, or part of the code, and the above-mentioned module, program segment, or part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0086] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. In some cases, the names of these units do not constitute limitations on the units themselves.

[0087] Another aspect of the present application provides a computer-readable storage medium having computer-readable instructions stored thereon. When executed by a computer processor, the computer executes the data view configuration methods provided in the aforementioned embodiments. The computer-readable storage medium may be included in the electronic device described in the aforementioned embodiments, or may exist independently and not be incorporated into the electronic device.

[0088] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiment of the application, the features and functions of two or more modules or units described above can be concretized in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be concretized.

[0089] Through the description of the above embodiments, it is easy for those skilled in the art to understand that the example embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the embodiments of the present application.

[0090] Those skilled in the art will readily conceive of other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of this application and include common knowledge or customary techniques in the art that are not disclosed herein.

[0091] It should be understood that the above content is only a preferred exemplary embodiment of the present application and is not intended to limit the implementation scheme of the present application. Ordinary technicians in this field can easily make corresponding changes or modifications based on the main concept and spirit of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection required by the claims.

Claims

1. A data view configuration method, characterized in that: The method comprises: Obtaining a data source type, a first data source interface functional description, and a second data source interface functional description; the data source type is determined by different databases; the first data source interface functional description includes obtaining a structured query language structure, obtaining a table structure, obtaining a database table list, and obtaining a database list; the second data source interface functional description includes generating a data preview; According to the data source type, instantiate the policy class of the first data source interface functional description, and instantiate the policy class of the second data source interface functional description; Based on the instantiated policy class of the functional description of the first data source interface, the required data source is obtained and, according to pre-configured operation permissions, filtered data is determined from the data source, and the filtered data is encapsulated to obtain a data view; The data view is previewed through the instantiated strategy class described in the second data source interface function, and configuration operations are performed on the data nodes in the data view on a preset visualization page to obtain configuration data; the configuration operations include: dragging and / or connecting.

2. The data view configuration method according to claim 1, characterized in that: The process of instantiating the policy class of the first data source interface function description and the policy class of the second data source interface function description according to the data source type includes: Configure the unique identifier of the data source type; Based on the unique identifier, a structured query language for the functional description of the first data source interface is configured, and a policy class access interface for the functional description of the first data source interface is constructed through a bytecode operation library to complete the instantiation of the policy class for the functional description of the first data source interface; the structured query language for the functional description of the first data source interface is part of the execution program of the policy class access interface for the functional description of the first data source interface; According to the unique identifier, the structured query language of the second data source interface function description is configured, and the policy class access interface of the second data source interface function description is constructed through the bytecode operation library to complete the instantiation of the policy class of the second data source interface function description; the structured query language of the second data source interface function description is part of the execution program of the policy class access interface of the second data source interface function description.

3. The data view configuration method according to claim 1, characterized in that: The process of obtaining the required data source based on the instantiation strategy class described in the first data source interface function includes: According to the unique identifier of the data source type, a physical connection channel between the application and the target database is configured by creating a data view through a preset connection pool; a protocol adapter of the physical connection channel is loaded through a service discovery provision mechanism; and a heartbeat detection message format of the physical connection channel complies with the network transmission specification of the data source type; The instantiation strategy class of the first data source interface functional description obtains the data source and supplementary data source corresponding to the data source type through the physical connection channel; the supplementary data source is configured through the configuration center; The data source corresponding to the data source type and the supplementary data source are used as the required data sources.

4. The data view configuration method according to claim 1, wherein: The process of performing configuration operations on the data nodes in the data view on the preset visualization page to obtain configuration data includes: Obtain the type of the data node; If the type of the data node is a data table node, drag the data table node to the preset visualization page, select the required data fields by checking the data fields in the data table node, connect the data fields in different data table nodes by dragging and dropping lines, and combine the data fields in the connected data table nodes to obtain the configuration data; the combination method includes left join or inner join; If the type of the data node is a structured query language execution node, run the structured query language execution statement corresponding to the structured query language execution node to obtain the required data field, connect the data fields in different structured query language execution nodes by dragging and dropping lines, and combine the data fields in the connected structured query language execution nodes to obtain the configuration data.

5. The data view configuration method according to any one of claims 1 to 4, characterized in that: After obtaining the configuration data, the method further includes: If the type of the data node is a data table node, extracting physical storage information from the configuration data, a connection relationship and a combination relationship between data fields of the data table nodes, generating multiple standard identifiers based on the field names in the physical storage information and the table aliases to which the field names belong, and concatenating the multiple standard identifiers to obtain a query field; generating a join clause from the connection relationship and the combination relationship through an abstract syntax tree parser, concatenating the query field and the join clause to obtain a first structured query language statement, and executing the first structured query language statement to obtain query data; If the data node is a structured query language execution node, a connection relationship and a combination relationship of data fields between the data table nodes in the configuration data are extracted, and a join clause is generated from the connection relationship and the combination relationship using an abstract syntax tree parser to obtain a second structured query language statement. The second structured query language statement is parsed using the abstract syntax tree parser to obtain an abstract syntax tree. The nodes in the abstract syntax tree are recursively traversed to verify the execution statement type, the number of query statements, the subquery nesting depth, and the number of connected tables in the second structured query language statement. If the execution statement type, the number of query statements, the subquery nesting depth, and the number of connected tables all meet verification requirements, the placeholder tag in the second structured query language statement is parsed using the abstract syntax tree parser, and a filtering parameter at the placeholder tag is obtained using a type-safe parameter. Based on the filtering parameter, the second structured query language statement is executed to obtain query data; the filtering parameter is derived from the preset visualization page.

6. The data view configuration method according to claim 5, characterized in that: After obtaining the second structured query language statement, the method further includes: Calculating a hash key of the second structured query language statement, using the hash key as a key value of the structured query language execution node, and locally storing preview data and execution risk verification results of the structured query language execution node to obtain cache data of the structured query language execution node; The unique identifier of the data view is used as a key value to locally store the preview data of the data view to obtain cached data of the data view.

7. The data view configuration method according to any one of claims 1 to 4, characterized in that: If the second data source interface function description includes: previewing all data and previewing paged data, then the process of previewing the data view by using the instantiated strategy class of the second data source interface function description includes: Running all data preview structured query language statements in the instantiated strategy class of the second data source interface functional description to obtain data fields and data in the data view, returning the data fields and data of the data view to the preset visualization page via the hypertext transfer protocol, and rendering the data fields and data of the data view via the visualization engine of the preset visualization page to achieve a preview of the data view; Alternatively, run the paging data preview structured query language statement in the instantiated strategy class of the second data source interface function description to obtain the data fields and data in the data view, return the data fields and data of the data view to the preset visualization page via the hypertext transfer protocol, and render the data fields and data of the data view through the visualization engine of the preset visualization page to achieve a preview of the data view.

8. A data view configuration device, characterized in that: include: An interface definition module is used to obtain a data source type, a first data source interface function description, and a second data source interface function description; The data source type is determined by different databases; the first data source interface function description includes obtaining structured query language structure, obtaining table structure, obtaining database table list, and obtaining database list; the second data source interface function description includes generating data preview; An interface instantiation module, configured to instantiate the policy class of the first data source interface function description and the policy class of the second data source interface function description according to the data source type; a data encapsulation module, configured to obtain a required data source based on the instantiated policy class described in the first data source interface function, determine filtered data from the data source according to pre-configured operation permissions, encapsulate the filtered data, and obtain a data view; A view configuration module is used to preview the data view through the instantiated strategy class described by the second data source interface function, and to perform configuration operations on the data nodes in the data view on a preset visualization page to obtain configuration data; the configuration operations include: dragging and / or connecting.

9. An electronic device, characterized in that: include: one or more processors; A storage device is used to store one or more programs, and when the one or more programs are executed by the one or more processors, the electronic device implements the data view configuration method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that Computer-readable instructions are stored thereon, and when the computer-readable instructions are executed by a processor of a computer, the computer is caused to execute the data view configuration method according to any one of claims 1 to 7.

Images