Method and device for realizing heterogeneous data conversion dynamic expansion based on general SQL (Structured Query Language)
Through the SQLTransform conversion plug-in and SQLEngine engine based on general SQL, the complexity problem caused by the difference in data source in big data acquisition scenarios is solved, seamless integration and flexible data conversion of multiple data sources are achieved, development difficulty is reduced, and development is improved Development efficiency.
Patent Information
- Application Number
- CN202410932701.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-12
- Publication Date
- 2024-11-12
AI Technical Summary
In the existing technology, in the big data data acquisition scenario, the differences between various data sources lead to complex data acquisition and conversion processes, high configuration costs, and poor versatility of SQL processing functions, which makes it impossible to switch freely between multiple computing engines, resulting in It is difficult to develop.
Using a general SQL-based method, through the SQLTransform conversion plug-in and SQLEngine engine, it supports heterogeneous data conversion, parsing and verifying SQL statements, implementing metadata conversion, and defining custom function interfaces, supporting rapid development of custom functions and implementing data conversion logic customization.
It realizes seamless integration of multiple data sources, reduces the development difficulty of data conversion, supports SQL standard syntax, simplifies the data conversion process, and improves development efficiency and flexibility.
Smart Images

Figure CN118939676A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of data conversion, and in particular to a method and a device for realizing dynamic expansion of heterogeneous data conversion based on general SQL. Background Art
[0002] The scenario of big data collection involves a variety of data sources, such as relational databases, graph databases, document databases, file storage OSS, and message queues. In order to shield the differences in the collection of these data sources and improve the ease of data collection and conversion, an easy-to-use SQL-like statement is needed to parse the data format and type, as well as a dynamically extensible custom function UDF based on SQL to process the data. Therefore, no matter what format the data source is in, SQL statements can be used in a unified way to parse and convert the data, making the data collection and conversion process more convenient and flexible.
[0003] In the existing solutions, solutions based on different conversion configurations can be used to implement data conversion logic for each type of data. Each conversion logic has a corresponding configuration, which is costly and difficult to use. Data processing solutions based on Spark and Flink can also be used. Spark and Flink can access multiple types of data and process them through Spark SQL or Flink SQL. However, the functions processed by SQL must be limited to Spark or Flink's own functions, and cannot be freely switched between multiple computing engines, which has poor versatility. Summary of the invention
[0004] In order to solve the above problems existing in the prior art, the present invention provides a method and device for realizing dynamic expansion of heterogeneous data conversion based on universal SQL, which supports seamless integration of multiple data sources and greatly reduces the development difficulty of data conversion.
[0005] To achieve the above object, the present invention adopts the following technical solutions:
[0006] In one embodiment of the present invention, a method for implementing dynamic expansion of heterogeneous data conversion based on general SQL is proposed, and the method includes:
[0007] The SQLTransform plug-in uses query SQL statements and configuration information to achieve heterogeneous data conversion with the support of the SQLEngine engine, supports different table structures and data types, and achieves metadata conversion;
[0008] The SQLEngine engine parses the query SQL statement, verifies its grammatical correctness, and filters and converts the input data according to the query SQL statement, and finally converts it into new data rows that meet the query requirements;
[0009] The SqlParse parser parses the query SQL statement and converts the query SQL statement into the corresponding abstract syntax tree AST structure.
[0010] Furthermore, a general custom function interface is defined to support quick definition of a custom function of a SQLTransform transformation plug-in.
[0011] Furthermore, the SQLTransform transformation plug-in is defined to support customizing your own data transformation logic.
[0012] Furthermore, the SQLEngine engine constructs a description of the output data structure according to the parsed query SQL statement.
[0013] In one embodiment of the present invention, a device for implementing dynamic expansion of heterogeneous data conversion based on general SQL is also proposed, and the device includes:
[0014] SQLTransform plug-in is used to use query SQL statements and configuration information to realize the conversion of heterogeneous data with the support of SQLEngine engine, support different table structures and data types, and realize metadata conversion;
[0015] SQLEngine is used to parse the query SQL statement, verify its grammatical correctness, filter and convert the input data according to the query SQL statement, and finally convert it into new data rows that meet the query requirements;
[0016] The SqlParse parser is used to parse the query SQL statement and convert the query SQL statement into the corresponding abstract syntax tree AST structure.
[0017] Furthermore, a general custom function interface is defined to support quick definition of a custom function of a SQLTransform transformation plug-in.
[0018] Furthermore, the SQLTransform transformation plug-in is defined to support customizing your own data transformation logic.
[0019] Furthermore, the SQLEngine engine constructs a description of the output data structure according to the parsed query SQL statement.
[0020] In one embodiment of the present invention, a computer device is also proposed, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the aforementioned method for dynamically expanding heterogeneous data conversion based on general SQL is implemented.
[0021] In one embodiment of the present invention, a computer-readable storage medium is further provided, wherein the computer-readable storage medium stores a computer program for executing a method for dynamically extending heterogeneous data conversion based on general SQL.
[0022] Beneficial effects:
[0023] 1. The present invention provides a solution for heterogeneous data conversion based on general SQL, supports seamless integration of multiple data sources, and greatly reduces the development difficulty of data conversion.
[0024] 2. The present invention adopts a plug-in design and defines a SQLTransform conversion plug-in, based on which one can customize one's own data conversion logic.
[0025] 3. The present invention designs a SQLEngine engine to parse and execute SQL queries, supports SQL standard syntax, and describes conversion logic with standard SQL statements.
[0026] 4. The present invention defines a universal user-defined function interface SeacrabUDF, which can conveniently and quickly develop and integrate various user-defined functions.
[0027] 5. The entire architecture of the present invention is loosely coupled, and each module is coupled through an interface, which supports modular development and is easy to upgrade and maintain. BRIEF DESCRIPTION OF THE DRAWINGS
[0028] Figure 1 It is a flow chart of a method for realizing dynamic expansion of heterogeneous data conversion based on general SQL of the present invention;
[0029] Figure 2 This is a simple SQL conversion logic block diagram of an embodiment of the present invention;
[0030] Figure 3 It is a complex SQL conversion logic block diagram of an embodiment of the present invention;
[0031] Figure 4 It is a schematic diagram of the structure of a device for realizing dynamic expansion of heterogeneous data conversion based on general SQL of the present invention;
[0032] Figure 5 It is a schematic diagram of the computer device structure of the present invention. DETAILED DESCRIPTION
[0033] The principles and spirit of the present invention will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided only to enable those skilled in the art to better understand and implement the present invention, and are not intended to limit the scope of the present invention in any way. On the contrary, these embodiments are provided to make the present disclosure more thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art.
[0034] Those skilled in the art will appreciate that the embodiments of the present invention may be implemented as a system, device, apparatus, method or computer program product. Therefore, the present disclosure may be specifically implemented in the following forms, namely: complete hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.
[0035] According to an embodiment of the present invention, a method for dynamically expanding heterogeneous data conversion based on general SQL is proposed, which supports seamless integration of multiple data sources and greatly reduces the development difficulty of data conversion.
[0036] The principle and spirit of the present invention are explained in detail below with reference to several representative embodiments of the present invention.
[0037] Figure 1 This is a flow chart of the method for implementing dynamic expansion of heterogeneous data conversion based on general SQL of the present invention. Figure 1 As shown, the implementation logic of this method is as follows:
[0038] 1. SQLTransform conversion plug-in
[0039] The main function of the SQLTransform plug-in is to use query SQL statements and configuration information to achieve heterogeneous data conversion with the support of the SQLEngine engine, and to adapt to different table structures and data types, and to achieve metadata conversion to ensure the integrity and consistency of the data structure during the conversion process.
[0040] (1) Constructor:
[0041] The constructor receives a read-only configuration object and table structure information, from which it extracts the SQL query, engine type, and input table name and field information.
[0042] Construct a data type object based on the table structure information to describe the data type of the input row.
[0043] (2) Configuration settings and verification:
[0044] The setConfig(Config pluginConfig) method (a method used to set the configuration information of the plug-in) is used to read and verify the values of the SQL query and engine type from the configuration.
[0045] (3) Lifecycle management:
[0046] The open() method (a method that initializes the SQL engine instance before data processing and preprocesses SQL queries and related tuning parameters) initializes the SQLEngine engine instance before processing data, and calls its init method to preprocess SQL queries and related tuning parameters.
[0047] The tryOpen() method (used to ensure that the SQLEngine engine is initialized correctly before use) ensures that it has been initialized correctly each time it needs to be used.
[0048] (4) Data conversion logic:
[0049] Row-level transformation: The transformRow(SeaCrabRow inputRow) method (row-level transformation method) is responsible for transforming the input data row according to the provided SQL query. The specific process is to call sqlEngine.transformBySQL(inputRow) (used to transform the value of a row of specific data) to execute the SQL query, and then encapsulate the query results into a new SeaCrabRow list and return it.
[0050] Metadata conversion logic:
[0051] a. Row type conversion: The transformRowType(SeaCrabRowType inputRowType) method (a method used to convert the type of a row of data) obtains the new row type structure generated after the SQL query by calling sqlEngine.typeMapping() (used to map the corresponding relationship between specific data and data types).
[0052] b. Table structure conversion: The transformTableSchema() method (a method used to convert table metadata) builds a new TableSchema based on the output column information after executing the SQL query. First, get the field name and data type of the new table; then, keep the metadata information such as the primary key constraint and foreign key constraint of the original table and map them to the new table structure; finally, create a Column (data column) object based on the new column information, and keep the original column's length, whether it is nullable, default value, and comments as much as possible.
[0053] 2. SQLEngine
[0054] The SQLEngine engine provides a lightweight conversion engine for processing heterogeneous data, converting heterogeneous data into a unified SeaCrabRow data row, which is used to parse query SQL statements, verify their grammatical correctness, and filter and convert input data based on query SQL statements, and finally convert it into a new data row that meets the query requirements. The following is a detailed explanation of its core functions:
[0055] (1) initEngine initializes the engine:
[0056] Receives three parameters: the input table name, a SeaCrabRowType object representing the input data structure, and the SQL statement to be executed.
[0057] Initialize internal private member variables, including the original SQL statement, the parsed SQL body part query selector (PlainSelect), and three auxiliary instances of SQL function (SQLFunction), SQL filter (SQLFilter), and SQL data type (SQLType).
[0058] All available user-defined functions (UDFs) are dynamically loaded through the SPI mechanism and passed to the SQLType instance to support the use of these UDFs in subsequent processing.
[0059] Call the built-in parseSQL method of SqlParser (the default built-in method of SqlParser parser, used for parsing database-like languages) to parse the incoming SQL statement.
[0060] (2)parseSQL parses SQL:
[0061] Use the SqlParser library to parse the input SQL string, generate an abstract syntax tree AST, and extract the SELECT statement body as a PlainSelect object.
[0062] If an error is encountered during the parsing process, an exception is thrown with specific error information.
[0063] (3) validateSQL:
[0064] Strict syntax and semantics validation is performed on the parsed query SQL statement to ensure that it complies with the query specifications supported by the engine: the table name in the FROM clause must be consistent with the input table name, and the database schema or alias cannot be specified; full column selection (*) is not allowed in the SELECT clause, and each selection item must be a clear column reference or calculation expression.
[0065] (4) typeMapping type mapping:
[0066] Build a description of the output data structure, i.e. a new SeaCrabRowType object, according to the parsed query SQL statement.
[0067] Traverse all selection items in the query and determine the output field name and its corresponding data type based on the expression type.
[0068] If an input column mapping list is provided, the mappings are updated according to the input column names involved in the expression.
[0069] (5) transformBySQL transforms data:
[0070] Input a row of raw data and execute the conversion logic based on the parsed and verified query SQL statement: perform a scan operation, where "scan" actually directly returns all field values of the input row; execute the filtering conditions according to the WHERE clause to determine whether to retain the row of data; perform a mapping operation, calculate the value of the corresponding output field for each selected item SelectItem, and call the SQLFunction.computeForValue method (a calculation method for database-like language functions, which can be used for data calculation, date calculation, custom calculation, etc.) to complete the calculation.
[0071] Creates a new data row object based on the calculated output field array, sets relevant metadata, such as row type and table ID, and returns the result.
[0072] 3. SqlParse parser
[0073] It mainly provides the function of parsing query SQL statements and converting query SQL statements into corresponding abstract syntax tree AST structures. The following is a detailed description of the main methods:
[0074] parse(Reader statementReader): Reads the SQL statement from the given Reader object and parses it into a Statement object.
[0075] parse(String sql): Receives a SQL statement in string form and parses it into a Statement object.
[0076] parse(String sql, Consumer <sqlparser>consumer): It also receives a SQL statement in string form, but allows the function passed in through the Consumer interface to modify the behavior of the parser before parsing, such as setting a specific parsing mode or rule.
[0077] newParser(String sql): Creates a new SqlParser parser instance (a parser used to parse database-like languages, which can read data in the same way as the database language) to parse the given SQL string.
[0078] newParser(InputStream is) and newParser(InputStream is, String encoding): Creates a new SqlParser instance based on an input stream and an optional character encoding to read and parse SQL statements from the input stream.
[0079] parseAST(String sql): Parses a SQL statement and returns the root node of its abstract syntax tree.
[0080] parse(InputStream is) and parse(InputStream is, String encoding): Read and parse SQL statements from the input stream into Statement objects.
[0081] parseExpression(String expression), parseExpression(String expression, boolean allowPartialParse) and overloaded versions: These methods are used to parse SQL expressions, accept options to allow partial parsing, and allow the parser to be configured through the Consumer if necessary.
[0082] parseCondExpression(String condExpr) and its overloaded versions: specifically for the parsing of conditional expressions, usually appearing after the WHERE clause.
[0083] parseStatement(SqlParser parser) and parseStatements(CCJSqlParserparser): These two methods use the given SqlParser parser to parse a single SQL statement or a group of SQL statements, and use asynchronous execution internally to prevent long blocking.
[0084] streamStatements(StatementListener listener, InputStream is, String encoding): Reads multiple SQL statements continuously from the input stream and processes each statement through the passed in listener.
[0085] 4. User-defined function (UDF)
[0086] To make the SQLTransform plug-in more convenient to use, we support the plug-in's custom function UDF and provide a new set of custom function interfaces. You only need to implement the following SPI interface to quickly define a custom function UDF.
[0087]
[0088]
[0089] First, we provide a custom interface named SeacrabUDF, which mainly provides three methods.
[0090] First is functionName(), this method is used to return the name of the custom function;
[0091] Then there is resultType(), which is used to specify the return type of a custom function. Each custom function has a return type. Most custom functions specify a return type by default, but in some cases the return type is determined based on the input type.
[0092] Finally, evaluate() is used to calculate the custom function. Its input parameter is the input parameter value of the corresponding custom function, and after calculation, it returns a certain result.
[0093] It should be noted that, although the operations of the method of the present invention are described in a specific order in the above embodiments and the accompanying drawings, this does not require or imply that the operations must be performed in the specific order, or that all the operations shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.
[0094] In order to more clearly explain the above method for dynamically expanding heterogeneous data conversion based on general SQL, a specific embodiment is used for illustration below. However, it should be noted that this embodiment is only for better illustrating the present invention and does not constitute an improper limitation to the present invention.
[0095] Example:
[0096] 1. Simple SQL conversion
[0097] The SQLTransform plug-in reads the configuration information, parses the configuration information and SQL statements, and the SQLEngine engine performs specific data conversion processing actions. Define the field structure of the acquisition source to form a virtual table. Execute SQL statements based on the virtual table, process the corresponding fields through SQL functions, and the processing results can be registered as a new virtual table. SQL statements can continue to be executed based on the new virtual machine for processing and conversion. Virtual tables do not actually store data, but are only used to identify the intermediate process of data processing. Data from any virtual table can be written to the target storage.
[0098] like Figure 2 As shown in the figure, the upper layer is the Connector (data connector), and the Source (data source) connects to read the upstream data. The upstream data can be offline data or real-time data source. The downstream is the Sink (data writing target) layer, which mainly adds SQL conversion logic in the middle and supports UDF. Then there is the extended Transform (data conversion) layer, which includes SQL capabilities. SQL only supports simple SQL, similar to Select certain fields, and then add corresponding function processing, and also supports filtering conditions. Therefore, SQL is parsed, an abstract syntax tree is generated, and then a physical execution plan is generated. At the same time, it also has a large number of built-in function libraries, including commonly used functions, such as numeric, character, and time functions. It also supports UDF, and integrates the UDF developed by yourself into the function library through the SPI plug-in for calling. After parsing the abstract syntax tree and physical execution plan of SQL, there will be two steps, one is type conversion and the other is data conversion, that is, the two interface methods mentioned above. Type conversion is to convert the input type to the output type. Not only the simple type of the field, type conversion may also involve functions and constants. For example, if you directly select 1, the 1 here is actually a constant, so some constants and functions need to be converted. Functions usually have a specified return type, such as numeric functions and string functions have fixed return types. However, in some cases, the return type may be uncertain, and the output type may need to be determined based on the type of the input field, so the function needs to be processed recursively to obtain the final return type. The next layer is the data converter, which converts data through physical execution plans, function libraries, and filter conditions. Its input is the value of each field, that is, the value of each field in each row. After calculation through the physical execution plan, the value of each field in the output row is obtained.
[0099] 2. Complex SQL conversion
[0100] like Figure 3 As shown, when we need to splice Join information, when we get data here, each row of data has a main table, and then the Join information will be read from the cache. If it does not exist in the cache, the corresponding dimension table information in the original table may be queried from the data source, or the dimension table information may be queried and cached in the LRU cache, and then the physical execution plan of Join is spliced, and finally the data is spliced into a row of frame table data and written to the corresponding target library. By defining the Connector of Joinsource and loading the configuration of Source, data is obtained from the source according to the Join key, and the data is fully loaded into the cache, and there are cache strategies such as LRU cache and no cache. If the main table data is sharded, it is recommended to use Join key for sharding to ensure that the main table data and dimension table data fall in the same shard. In addition, for the extension of the SQLEngine engine, it is also necessary to perform parsing and running of the physical execution plan that supports Join. The configuration is as follows:
[0101]
[0102]
[0103]
[0104] 3. UDF
[0105] For SQL-like data conversion, you can freely develop custom functions. The following is a simple example of implementation:
[0106]
[0107]
[0108]
[0109]
[0110] From the above examples, we can see that the custom function is very concise and efficient. First, the first method defined is to return the UDF name, named IP_BELONG; second, specify the type of the UDF return result, and define the return type as a string; finally, the calculation logic of the UDF is to convert the IP address into the location based on the basic comparison table of IP addresses and locations.
[0111] Based on the same inventive concept, the present invention also proposes a device for implementing dynamic expansion of heterogeneous data conversion based on universal SQL. The implementation of the device can refer to the implementation of the above method, and the repeated parts will not be repeated. The term "module" used below can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.
[0112] Figure 4 Schematic diagram of the structure of the device for realizing dynamic expansion of heterogeneous data conversion based on general SQL of the present invention. Figure 4 As shown, the device comprises:
[0113] The SQLTransform plug-in 101 is used to use query SQL statements and configuration information to achieve heterogeneous data conversion under the support of the SQLEngine engine, support different table structures and data types, and achieve metadata conversion.
[0114] Define the SQLTransform transformation plug-in 101 to support customizing your own data transformation logic.
[0115] Defines a general custom function interface to support quick definition of a custom function for the SQLTransform transformation plug-in.
[0116] The SQLEngine engine 102 is used to parse the query SQL statement, verify its grammatical correctness, and filter and convert the input data according to the query SQL statement, and finally convert it into a new data row that meets the query requirements.
[0117] The SQLEngine engine 102 constructs a description of the output data structure according to the parsed query SQL statement.
[0118] The SqlParse parser 103 is used to parse the query SQL statement and convert the query SQL statement into a corresponding abstract syntax tree AST structure.
[0119] It should be noted that although several modules of the apparatus for implementing dynamic expansion of heterogeneous data conversion based on general SQL are mentioned in the above detailed description, this division is only exemplary and not mandatory. In fact, according to an embodiment of the present invention, the features and functions of two or more modules described above can be concretized in one module. Conversely, the features and functions of one module described above can be further divided into multiple modules for concretization.
[0120] Based on the above invention concept, Figure 5 As shown, the present invention also proposes a computer device 200, including a memory 210, a processor 220, and a computer program 230 stored in the memory 210 and executable on the processor 220. When the processor 220 executes the computer program 230, the aforementioned method for dynamically expanding heterogeneous data conversion based on general SQL is implemented.
[0121] Based on the aforementioned inventive concept, the present invention further proposes a computer-readable storage medium, which stores a computer program for executing the aforementioned method for dynamically extending heterogeneous data conversion based on general SQL.
[0122] The method and device for realizing dynamic expansion of heterogeneous data conversion based on universal SQL proposed in the present invention support seamless integration of multiple data sources, greatly reducing the development difficulty of data conversion; adopt plug-in design, define SQLTransform conversion plug-in, based on which one can customize one's own data conversion logic; design SQLEngine engine to parse and execute SQL queries, support SQL standard syntax, and describe conversion logic with standard SQL statements; define a universal custom function interface SeacrabUDF, which can conveniently and quickly develop and integrate various custom functions; the whole architecture is loosely coupled, and each module is coupled through an interface, supporting modular development, and facilitating upgrade and maintenance.
[0123] Although the spirit and principle of the present invention have been described with reference to several specific embodiments, it should be understood that the present invention is not limited to the disclosed specific embodiments, and the division of various aspects does not mean that the features in these aspects cannot be combined to benefit, and such division is only for the convenience of expression. The present invention is intended to cover various modifications and equivalent arrangements contained in the spirit and scope of the attached claims.
[0124] Regarding the limitation of the protection scope of the present invention, those skilled in the art should understand that, based on the technical solution of the present invention, various modifications or variations that can be made by those skilled in the art without creative work are still within the protection scope of the present invention.< / sqlparser>
Claims
1. A method for implementing dynamic expansion of heterogeneous data conversion based on general SQL, characterized in that: The method includes: The SQLTransform plug-in uses query SQL statements and configuration information to achieve heterogeneous data conversion with the support of the SQLEngine engine, supports different table structures and data types, and achieves metadata conversion; The SQLEngine engine parses the query SQL statement, verifies its grammatical correctness, and filters and converts the input data according to the query SQL statement, and finally converts it into new data rows that meet the query requirements; The SqlParse parser parses the query SQL statement and converts the query SQL statement into the corresponding abstract syntax tree AST structure.
2. The method for implementing dynamic expansion of heterogeneous data conversion based on general SQL according to claim 1, characterized in that: Defines a general custom function interface to support quick definition of a custom function for the SQLTransform transformation plug-in.
3. The method for implementing dynamic expansion of heterogeneous data conversion based on general SQL according to claim 1, characterized in that: Define the SQLTransform transformation plug-in to support customizing your own data transformation logic.
4. The method for implementing dynamic expansion of heterogeneous data conversion based on general SQL according to claim 1, characterized in that: The SQLEngine engine constructs a description of the output data structure according to the parsed query SQL statement.
5. A device for realizing dynamic expansion of heterogeneous data conversion based on general SQL, characterized in that: The device includes: SQLTransform plug-in is used to use query SQL statements and configuration information to realize the conversion of heterogeneous data with the support of SQLEngine engine, support different table structures and data types, and realize metadata conversion; SQLEngine is used to parse the query SQL statement, verify its grammatical correctness, filter and convert the input data according to the query SQL statement, and finally convert it into new data rows that meet the query requirements; The SqlParse parser is used to parse the query SQL statement and convert the query SQL statement into the corresponding abstract syntax tree AST structure.
6. The device for implementing dynamic expansion of heterogeneous data conversion based on general SQL according to claim 5, characterized in that: Defines a general custom function interface to support quick definition of a custom function for the SQLTransform transformation plug-in.
7. The device for implementing dynamic expansion of heterogeneous data conversion based on general SQL according to claim 5, characterized in that: Define the SQLTransform transformation plug-in to support customizing your own data transformation logic.
8. The device for implementing dynamic expansion of heterogeneous data conversion based on general SQL according to claim 5, characterized in that: The SQLEngine engine constructs a description of the output data structure according to the parsed query SQL statement.
9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 4 is implemented.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program for executing the method according to any one of claims 1 to 4.
Citation Information
Patent Citations
SQL (Structured Query Language) resolver and method
CN108255837A
An SQL execution efficiency static analysis method
CN109669952A
Full-link pressure measurement data distribution system and method based on SQL (Structured Query Language) engine
CN115185989A
Cited By
Cross-source SQL (Structured Query Language) method and device
CN119357219A
