KR102499941B1 - System for providing DBMS based on storage and control method thereof - Google Patents

Abstract

The present invention discloses a storage-based DBMS system and a control method thereof. That is, the present invention creates an object based on storage, retrieves data, and loads data, so as to improve the operational efficiency of the entire system according to parallel distributed processing.

Description

[0001] System for providing DBMS based on storage and control method thereof}

The present invention relates to a storage-based DBMS system and a control method thereof, and more particularly, to a storage-based DBMS system for generating objects, retrieving data, and loading data based on storage, and a control method thereof.

DBMS (database management system) is a software package that integrates functions such as adding, changing, deleting, and searching data, which are necessary processes to manage databases.

These DBMS are divided into hierarchical type, network type, and relational type, and recently, relational type is the mainstream of DBMS.

Korea Patent Registration No. 10-2013149 [Title: Data collection and management method and system for performing it]

An object of the present invention is to provide a storage-based DBMS system that creates objects, retrieves data, and loads data based on storage, and a method for controlling the same.

Another object of the present invention is to provide a storage-based DBMS system that provides a meta management function for data managed based on storage and a control method thereof.

A storage-based DBMS system according to an embodiment of the present invention includes a client providing information related to a SQL command or source file according to user input; and a storage for performing one of a function of creating an object, a data inquiry function, and a data loading function based on the information related to the SQL command or the source file, and providing a function execution result to the client.

As an example related to the present invention, the information related to the source file may include at least one of a source file hostname, a port, a source file format and separator, a schema, a database, a table, a load file format and separator, and a partition. .

As an example related to the present invention, the storage may include a plurality of blocks having a preset size; a reader/writer that creates an object related to the SQL command based on an object creation request; When the received SQL command is a preset create query, the database authority is checked based on the login information related to the client, and when the authority check is successful, parsing and analyzing the SQL command are performed, and the reader/ a parser and analyzer that interworks with a writer to store an audit log for the SQL command in one or more blocks among the plurality of blocks and requests a planner to create an object; Meta data is checked based on the object creation request, the location of the object is checked, the state of the loader and the reader/writer included in the storage are checked, respectively, the SQL command, the location of the checked object and , the planner requesting creation of an object from a worker included in the storage based on the checked state of the loader and the state of the reader/writer; and based on the object creation request, requests the reader/writer to create an object, registers object mapping related to the object created by the reader/writer in the meta data, and transmits result information related to object creation to the parser and analyzer. The parser and analyzer may store another audit log related to the created object in one or more other blocks among the plurality of blocks in cooperation with the reader/writer.

A control method of a storage-based DBMS system according to an embodiment of the present invention includes receiving, by a storage, information related to an SQL command or a source file according to a user input of a client; performing, by the storage, one of an object creation function, a data inquiry function, and a data loading function based on the information related to the received SQL command or source file; and providing a function execution result to the client by the storage.

As an example related to the present invention, the step of performing any one of an object creation function, a data search function, and a data loading function based on the information related to the received SQL command or source file, the received SQL command in advance When a create query is set, a process of checking authority for a database based on login information related to the client by a parser and analyzer included in the storage; performing a parsing and analyzing function for the SQL command by the parser and analyzer when authority check is successful; storing, by the parser and analyzer, an audit log for the SQL command in at least one block among a plurality of blocks, in conjunction with a reader/writer included in the storage; requesting, by the parser and analyzer, object creation to a planner included in the storage; confirming, by the planner, meta data based on the object creation request, and confirming the location of the object; checking, by the planner, the state of the loader and the state of the reader/writer included in the storage, respectively; requesting, by the planner, a worker included in the storage to create an object based on the SQL command, the location of the checked object, and the checked state of the loader and the reader/writer; requesting, by the worker, object creation to the reader/writer based on the object creation request; creating, by the reader/writer, an object related to the SQL command based on an object creation request; registering, by the worker, object mapping related to the created object in the meta data; providing, by the worker, result information related to object creation to the parser and analyzer; and storing another audit log related to the created object in one or more other blocks among the plurality of blocks by the parser and analyzer in association with the reader/writer.

As an example related to the present invention, the step of performing any one of an object creation function, a data search function, and a data loading function based on the information related to the received SQL command or source file, the received SQL command in advance When a set select query is selected, a process of checking authority for a database based on login information related to the client by a parser and analyzer included in the storage; performing a parsing and analyzing function for the SQL command by the parser and analyzer when authority check is successful; storing, by the parser and analyzer, an audit log for the SQL command in one or more blocks among a plurality of blocks, in conjunction with a reader/writer included in the storage; checking meta data based on a data search request by the parser and analyzer, and searching for an index and data location; requesting a data plan from a planner included in the storage based on the searched index and data location by the parser and analyzer; checking a state of a loader included in the storage by the planner; requesting, by the planner, to load data from a worker included in the storage based on the SQL command and the checked state of the loader; checking a state of the reader/writer by the worker; loading data from the reader/writer based on the checked reader/writer state by the worker; generating, by the worker, final data suitable for the select query desired by the client by reducing only a necessary data portion according to the select query among the loaded data; writing the generated final data to the reader/writer by the worker; and providing, by the worker, information related to final data recorded in the reader/writer or the generated final data to the parser and analyzer.

As an example related to the present invention, the process of receiving information related to the final data recorded in the reader/writer or the generated final data provided from the worker by the parser and analyzer; reading the final data from the reader/writer based on the information related to the final data recorded in the reader/writer by the parser and analyzer when the information related to the final data is received; and storing, by the parser and analyzer, another audit log related to the final data read in one or more other blocks among the plurality of blocks in association with the reader/writer.

As an example related to the present invention, the step of performing any one of an object creation function, a data search function, and a data loading function based on the information related to the received SQL command or source file, the received SQL command in advance When an insert query is set, checking authority for a database based on login information related to the client by a parser and analyzer included in the storage; performing a parsing and analyzing function for the SQL command by the parser and analyzer when authority check is successful; storing, by the parser and analyzer, an audit log for the SQL command in at least one block among a plurality of blocks, in conjunction with a reader/writer included in the storage; requesting, by the parser and analyzer, to load data from a planner included in the storage; checking the meta data based on the data load request by the planner, and inquiring the location of the data; checking, by the planner, the state of the loader and the state of the reader/writer included in the storage; requesting, by the planner, to load data from a worker included in the storage based on the SQL command, the location of the checked object, and the checked state of the loader and the reader/writer; loading data desired to be loaded by the client into the reader/writer by the worker in conjunction with the reader/writer; changing metadata information according to data loading by the worker; providing, by the worker, result information related to data loading to the parser and analyzer; and storing another audit log related to data loading in one or more other blocks among the plurality of blocks in association with the reader/writer by the parser and analyzer.

As an example related to the present invention, the step of performing any one of an object creation function, a data search function, and a data loading function based on the received SQL command or information related to the source file includes information related to the source file. upon reception, checking, by a loader included in the storage, authority to a database based on log-in information related to the client; storing, by the loader, an audit log for information related to the source file in at least one block among the plurality of blocks, in conjunction with a reader/writer included in the storage, when authority verification is successful; loading a file by the loader; when the location of the loaded file is the same server or external storage, checking meta data by the loader to inquire the location of an object to be loaded; checking a state of the loader and a state of the reader/writer by the loader; By the loader, in conjunction with the reader/writer, the client to the reader/writer based on the information related to the source file, the location of the checked object, the checked loader status, and the checked writer status A process of loading data to be loaded in; a process of changing meta data information according to data loading by the loader; and storing, by the loader, another audit log related to data loading in one or more other blocks among the plurality of blocks in association with the reader/writer.

As an example related to the present invention, the step of performing any one of an object creation function, a data search function, and a data loading function based on the received SQL command or information related to the source file includes information related to the source file. upon reception, checking, by a loader included in the storage, authority to a database based on log-in information related to the client; storing, by the loader, an audit log for information related to the source file in at least one block among the plurality of blocks, in conjunction with a reader/writer included in the storage, when authority verification is successful; loading a file by the loader; when the loading of the file is copying in storage, checking the meta data by the loader and inquiring the location of the object to be loaded; checking a state of the loader and a state of the reader/writer by the loader; By the loader, in conjunction with the reader/writer, data is read from the reader/writer based on the information related to the source file, the location of the checked object, the checked loader status, and the checked writer status process of deleting; loading data to be loaded by the client into the reader/writer by the loader in conjunction with the reader/writer; a process of changing meta data information according to data loading by the loader; and storing another audit log related to data loading in one or more other blocks among the plurality of blocks by the loader in association with the reader/writer.

The present invention has an effect of improving the operational efficiency of the entire system according to parallel distributed processing by creating objects, retrieving data, and loading data based on storage.

In addition, the present invention has an effect of increasing management efficiency of meta data by providing a meta management function for data managed based on storage.

1 is a block diagram showing the configuration of a storage-based DBMS system according to an embodiment of the present invention.
2 is a diagram showing an example of a DBMS with a logical top-down structure according to an embodiment of the present invention.
3 is a flowchart illustrating a control method of a storage-based DBMS system according to an embodiment of the present invention.

It should be noted that technical terms used in the present invention are only used to describe specific embodiments and are not intended to limit the present invention. In addition, technical terms used in the present invention should be interpreted in terms commonly understood by those of ordinary skill in the art to which the present invention belongs, unless specifically defined otherwise in the present invention, and are excessively inclusive. It should not be interpreted in a positive sense or in an excessively reduced sense. In addition, when the technical terms used in the present invention are erroneous technical terms that do not accurately express the spirit of the present invention, they should be replaced with technical terms that those skilled in the art can correctly understand. In addition, general terms used in the present invention should be interpreted as defined in advance or according to context, and should not be interpreted in an excessively reduced sense.

Also, singular expressions used in the present invention include plural expressions unless the context clearly dictates otherwise. Terms such as "consisting of" or "comprising" in the present invention should not be construed as necessarily including all of the various elements or steps described in the invention, and some of the elements or steps may not be included. It should be construed that it may, or may further include additional components or steps.

In addition, terms including ordinal numbers such as first and second used in the present invention may be used to describe components, but components should not be limited by the terms. Terms are used only to distinguish one component from another. For example, a first element may be termed a second element, and similarly, a second element may be termed a first element, without departing from the scope of the present invention.

Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the accompanying drawings, but the same or similar components are given the same reference numerals regardless of reference numerals, and redundant description thereof will be omitted.

In addition, in describing the present invention, if it is determined that a detailed description of a related known technology may obscure the gist of the present invention, the detailed description will be omitted. In addition, it should be noted that the accompanying drawings are only for easily understanding the spirit of the present invention, and should not be construed as limiting the spirit of the present invention by the accompanying drawings.

1 is a block diagram showing the configuration of a storage-based DBMS system 10 according to an embodiment of the present invention.

As shown in FIG. 1, the storage-based DBMS system 10 is composed of a client 100 and a plurality of storages 200. Not all of the components of the storage-based DBMS system 10 shown in FIG. 1 are essential components, and the storage-based DBMS system 10 may be implemented by more components than those shown in FIG. In addition, the storage-based DBMS system 10 may be implemented with fewer components.

The client 100 and the storage 200 each include a communication unit (not shown) for performing a communication function with other terminals, a storage unit (not shown) for storing various information and programs (or applications), A display unit (not shown) for displaying various information and program execution results, an audio output unit (not shown) for outputting audio information corresponding to the various information and program execution results, and controlling various components and functions of each terminal It may include a control unit (not shown) and the like for doing so.

The client (or terminal) 100 communicates with the plurality of storages 200 and the like.

In addition, the client 100 includes a smart phone, a portable terminal, a mobile terminal, a foldable terminal, a personal digital assistant (PDA), a PMP ( Portable Multimedia Player terminal, telematics terminal, navigation terminal, personal computer, notebook computer, slate PC, tablet PC, ultrabook, wearable device (including wearable devices, for example, watch-type terminals (Smartwatch), glass-type terminals (Smart Glass), HMD (Head Mounted Display), etc.), Wibro terminals, IPTV (Internet Protocol Television) terminals, smart TVs, It can be applied to various terminals such as digital broadcasting terminals, AVN (Audio Video Navigation) terminals, A/V (Audio/Video) systems, and flexible terminals.

In addition, the client 100 performs a login procedure (or login function) through one storage 200 having a high process or system margin among the plurality of storages 200 . At this time, the client 100 may perform the login procedure using a pre-registered ID and password, a barcode or QR code including the ID, a preset authentication token, and the like.

In addition, the client 100 receives information related to a SQL command or source file according to user input (or user selection/touch/control). Here, the SQL commands include create query, select query, insert/update query, delete query, truncate query, drop query, grant query, revoke query, and the like. In addition, the information related to the source file includes information on the source file hostname, port, source file format and separator, schema, database, table, load file format and separator, partition, and the like.

In addition, the client 100 transmits information related to the received SQL command or source file to the storage 200 . At this time, the client 100 receives information related to the SQL command or source file through a dedicated app provided by the storage 200, and transmits information related to the received SQL command or source file to the storage 200. ) can be transmitted.

In addition, the client 100 receives information indicating that there is no right to create an object provided from the storage 200 in response to a previously input SQL command (including, for example, create query, etc.), and receives the received information. Displays (or outputs) information indicating that there is no permission to create the specified object.

In addition, the client 100 receives an object creation result provided from the storage 200 (or the parser and analyzer 220) in response to a previously input SQL command (including, for example, create query, etc.), The received object creation result is displayed (or output). Here, the object creation result includes information on whether or not the object to be created in the client 100 is created (eg, object creation failure information, object creation success information, etc.), date and time information, and the like.

In addition, the client 100 receives information indicating that there is no right to retrieve data provided from the storage 200 in response to a previously input SQL command (including, for example, a select query), and the received Displays (or outputs) information indicating that there is no authority for data inquiry.

In addition, the client 100 receives a data search result provided from the storage 200 (or the parser and analyzer 220) in response to a previously input SQL command (eg, including a select query, etc.), The received data inquiry result is displayed (or output). Here, the data search result includes information on the object to be searched by the client 100 (eg, including information on object search failure when object search fails, information on the corresponding object when object search succeeds, etc.), date and time, and including visual information, etc.

In addition, the client 100 receives information indicating that there is no right to load data provided from the storage 200 in response to a previously entered SQL command (eg, an insert query, an update query, etc.), Displays (or outputs) information indicating that there is no authority for loading the received data.

In addition, the client 100 receives a data load result provided from the storage 200 (or the parser and analyzer 220) in response to a previously entered SQL command (eg, insert query/update query, etc.). and displays (or outputs) the received data load result. Here, the data load result includes information on whether the data to be loaded by the client 100 has been successfully loaded (eg, data load failure information, data load success information, etc.), date and time information, and the like.

In addition, the client 100 receives information indicating that there is no authority for loading data provided from the storage 200 in response to the previously input information related to the source file, and the authority for loading the received data is Displays (or outputs) information indicating that there is none.

In addition, the client 100 receives a table data deletion result provided from the storage 200 (or the parser and analyzer 220) in response to a previously input SQL command (including, for example, a delete query). and displays (or outputs) the data deletion result in the received table. Here, the data deletion result of the table includes a table name to be deleted from the client 100, data to be deleted, data deletion date and time information, and the like.

In addition, the client 100 receives a data deletion result of a table provided from the storage 200 (or the parser and analyzer 220) in response to a previously input SQL command (including, for example, truncate query, etc.) and displays (or outputs) the data deletion result in the received table. Here, the data deletion result of the table includes a table name to be deleted from the client 100, data to be deleted, data deletion date and time information, and the like.

In addition, the client 100 receives a table data deletion result provided from the storage 200 (or the parser and analyzer 220) in response to a previously input SQL command (including, for example, a drop query). and displays (or outputs) the data deletion result in the received table. Here, the data deletion result of the table includes a table name to be deleted from the client 100, data to be deleted, meta information related to the deleted data, data deletion date and time information, and the like.

In addition, the client 100 receives a permission assignment result provided from the storage 200 (or the parser and analyzer 220) in response to a previously input SQL command (eg, including a grant query, etc.), Displays (or outputs) the received authority allocation result. Here, the permission allocation result includes the database name for providing (or assigning) the permission to the client 100, information on a specific client 100 to which the permission is to be assigned, date and time information of permission assignment, and the like.

In addition, the client 100 receives a permission release result provided from the storage 200 (or the parser and analyzer 220) in response to a previously input SQL command (including, for example, revoke query, etc.), Displays (or outputs) the received permission release result. Here, the permission release result includes a database name for releasing permission from the client 100, information on another specific client 100 to release permission, date and time information of permission release, and the like.

In addition, the client 100 receives another data load result provided from the storage 200 (or the loader 210) in response to the information related to the previously provided source file, and the received other data load result display (or output). Here, the other data loading result includes information on whether the data to be loaded by the client 100 has been successfully loaded (eg, data loading failure information, data loading success information, etc.), date and time information, etc. .

The storage 200 communicates with the client 100 and the like.

Also, the storage 200 may be implemented in the form of a web server, database server, proxy server, or the like. In addition, one or more of a network load balancing mechanism and various software enabling the corresponding storage 200 to operate on the Internet or other networks may be installed in the storage 200, and through this, it may be implemented as a computerized system. can Also, the network can be an http/https network, a private line, an intranet or any other network. Furthermore, the connection between the client 100 and the storage 200 may be connected through a secure network to prevent data from being attacked by any hacker or other third party. In addition, the storage 200 may include a plurality of database servers, and these database servers may be implemented in a manner that is separately connected to the storage 200 through any type of network connection including a distributed database server architecture. there is.

In addition, the storage 200 includes a CPU (not shown), a disk (DISK) (not shown), a memory (not shown), a database management system (DBMS) (not shown), and the like ( or configuration). Here, the DBMS stores (or manages) a plurality of data (or tables) collected from various servers and/or devices.

1, the storage 200 includes a loader 210, a parser and analyzer 220, a planner 230, a worker 240, a reader/writer 250, and a plurality of blocks 260. ) is composed of Not all of the components of the storage 200 shown in FIG. 1 are essential components, and the storage 200 may be implemented with more components than those shown in FIG. 1 or fewer components. Storage 200 may also be implemented. Here, the plurality of storages 200 may be configured as a distributed storage or a distributed system.

The concept of terms used in the present invention is summarized as follows.

First, a file is composed of blocks. Here, the block is stored as data of a predefined size, and the corresponding data may be encrypted and stored according to settings.

Also, a directory is composed of files or directories.

DBMS (Database Management System) is composed of schema, database, table, and partition, and as shown in FIG. 2, the corresponding configuration items have a logical top-down structure. , those configurations are mapped to directories in the storage meta.

A partition can exist in a table, and that partition can have sub-partitions.

If the bottom is a partition or table, file information is mapped.

In addition, a column/index in a table is stored and managed in a separate memory/disk (not shown).

The table is a collection of data composed of rows and columns, and represents a data storage space in which tables with the same attributes/relationships are gathered, and the partition represents physical division of table data into small units that are easy to manage. A collection of tables, most of which are divided into business units, and the schema is a collection of databases, which are separated for management according to security/business policies between systems.

In this way, the storage 200 may perform meta management on the corresponding storage.

Here, the meta management represents a description of the directory/file structure of DBMS objects on storage, and some of the corresponding functions can be individually performed.

In addition, one of the storages 200 having a high process or system margin among the plurality of storages 200 may perform a login procedure (or login function). At this time, the storage 200 may perform the login procedure using an ID and password pre-registered with the client 100, a barcode or QR code including the corresponding ID, a preset authentication token, and the like.

In addition, the storage 200 receives information related to a SQL command or source file according to a user input (or user selection/touch/control) of the client 100 . Here, the SQL commands include create query, select query, insert/update query, delete query, truncate query, drop query, grant query, revoke query, and the like. In addition, the information related to the source file includes information on the source file hostname, port, source file format and separator, schema, database, table, load file format and separator, partition, and the like.

At this time, the storage 200 performs a format check (or error check) on the received SQL command, and provides corresponding error information to the client 100 when there is an error in the format of the corresponding SQL command.

In addition, the storage 200 performs a format check (or error check) on the information related to the received source file, and if there is an error in the format of the information related to the source file, the corresponding error information is sent to the client 100. ) is provided.

The loader 210 communicates with the parser and analyzer 220 , the planner 230 , the worker 240 , the reader/writer 250 , and the plurality of blocks 260 .

In addition, the loader 210 performs a function of loading a file to be loaded in the client 100 by interworking with the reader/writer 250 .

In addition, when information related to the source file is received, the loader 210 transfers the data (or source file) requested by the client 100 to the storage 200 in response to the received information related to the source file. (or database), and provides (or transmits) the data loading result to the client 100.

That is, when information related to the source file is received, the loader 210 checks database authority (eg, schema, database, table, etc. authority) based on login information related to the corresponding client 100 do.

As a result of the above check, if the authorization check fails (or if the login information related to the client 100 does not have data loading / database authorization / is not set), the loader 210 does not have authorization to load data Provides (or transmits) information indicating the to the client 100.

In addition, as a result of the above check, if the authority check is successful (or if the log-in information related to the client 100 is in a state where the data load/authority for the database is present/set), the loader 210 reads the reader/writer ( 250), an audit log for information related to a corresponding source file is stored in one block 260 among the plurality of blocks 260.

Also, the loader 210 loads a file (or the source file).

When the location of the loaded file is the same server or external storage, the loader 210 checks the meta data and inquires (or checks) the location of the object to be loaded.

In addition, the loader 210 checks the state of the loader 210 (including, for example, process utilization rate/throughput rate, etc.) and the state of the reader/writer 250 (including, for example, process utilization rate/throughput rate, etc.) .

In addition, the loader 210 interworks with the reader/writer 250 to obtain information related to the source file, the location of the checked object, the state of the checked loader 210, and the checked writer 250. The data (or the source file) to be loaded in the corresponding client 100 is loaded (or written) into the reader/writer 250 based on the state of .

In addition, the loader 210 changes (or updates) information (eg, including an index) of corresponding meta data according to data loading.

In addition, the loader 210 interworks with the reader/writer 250 to store other audit logs related to data loading in one or more other blocks 260 among the plurality of blocks 260 .

In addition, the loader 210 provides (or transmits) the data loading result to the client 100 . Here, the data loading result is information on whether the data (or the source file) to be loaded by the client 100 has been successfully loaded (for example, data/source file loading failure information, data/source file loading success information, etc.) including), date and time information, etc.

In addition, when the loading of the file is copying in the storage, the loader 210 checks meta data and inquires (or checks) the location of the object to be loaded.

In addition, the loader 210 checks the state of the loader 210 (including, for example, process utilization rate/throughput rate, etc.) and the state of the reader/writer 250 (including, for example, process utilization rate/throughput rate, etc.) .

In addition, the loader 210 interworks with the reader/writer 250 to obtain information related to the source file, the location of the checked object, the checked state of the loader 210, and the reader/writer 250. Data (or directories/files) are deleted from the reader/writer 250 based on the status of .

In addition, the loader 210 interworks with the reader/writer 250 to load (or record).

In addition, the loader 210 changes (or updates) information (eg, including an index) of corresponding meta data according to data loading.

In addition, the loader 210 interworks with the reader/writer 250 to store another audit log related to data loading in another one or more blocks 260 among the plurality of blocks 260 .

In addition, the loader 210 provides (or transmits) other data loading results to the client. Here, the other data loading result includes information on whether the data to be loaded by the client 100 has been successfully loaded (eg, data loading failure information, data loading success information, etc.), date and time information, etc. .

The parser & analyzer 220 communicates with the loader 210, the planner 230, the worker 240, the reader/writer 250, and the plurality of blocks 260.

In addition, the parser and analyzer 220 performs user authentication and authority checks, and parses/analyzes SQL statements requested by the client 100 (or the user of the client 100) to find a certain file/directory, etc. Performs a function to decide whether to read.

In addition, when the received SQL command is a preset create query, the parser and analyzer 220 has database authority (for example, schema, database, table, etc.) based on login information related to the corresponding client 100. permission).

As a result of the above check, if the authorization check fails (or if the login information related to the client 100 has no authorization for the database / is not set), the storage 200 (or the storage included in the storage 200) The parser and analyzer 220 provides (or transmits) information indicating that there is no right to create an object to the client 100 .

In addition, as a result of the above check, if the authority check is successful (or if the login information related to the client 100 has authority for the database/is set), the parser and analyzer 220 executes an SQL command (or create query). ) to perform parsing and analysis functions.

In addition, the parser and analyzer 220 works with the reader/writer 250 included in the storage 200 to store audit logs for corresponding SQL commands (or create queries) in one or more of the plurality of blocks 260. Save to block 260.

In addition, the parser and analyzer 220 requests the planner 230 to create an object.

In addition, after a corresponding object is created according to the object creation request, the parser and analyzer 220 receives result information related to object creation provided from the worker 240 .

Also, the parser and analyzer 220 works with the reader/writer 250 to store other audit logs related to previously created objects in one or more other blocks 260 among the plurality of blocks 260 .

Also, the parser and analyzer 220 provides (or transmits) the object creation result to the client. Here, the object creation result includes information on whether or not the object to be created in the client 100 is created (eg, object creation failure information, object creation success information, etc.), date and time information, and the like.

When the received SQL command is a preset select query, the parser and analyzer 220 grants database authority (eg, schema, database, table, etc. authority) based on login information related to the corresponding client 100. Check the

As a result of the check, if the authorization check fails (or if the login information related to the client 100 does not have data retrieval/authority for the database/is not set), the parser and analyzer 220 is used for data retrieval. Information indicating that there is no authority is provided (or transmitted) to the client 100 .

In addition, as a result of the above check, if the authorization check is successful (or if the login information related to the client 100 is in a state where the authorization for data inquiry/database is present/set), the parser and analyzer 220 executes an SQL command ( or select query) to perform parsing and analysis functions.

In addition, the parser and analyzer 220 interworks with the reader/writer 250 to store an audit log for a corresponding SQL command (or select query) in one or more blocks 260 among the plurality of blocks 260. do.

In addition, the parser and analyzer 220 checks meta data based on a data search request, and searches for an index and data location (or an index and data location in relation to data to be searched). At this time, when the metadata is retrieved, if the corresponding information is encrypted and stored, the parser and analyzer 220 retrieves the encryption key and then searches the index and data location related to the data to be retrieved using the encryption key. may be

Also, the parser and analyzer 220 requests a data plan from the planner 230 based on the searched index and data location.

In addition, the parser and analyzer 220 provides (or transmits) information related to the final data recorded in the reader/writer 250 provided (or transmitted) by the worker 240 (for example, block information in which the final data is recorded, block location information, etc.), the final data, etc. are received.

In addition, when information related to the final data is received, the parser & analyzer 220 receives the final data from the reader/writer 250 based on the information related to the final data recorded in the reader/writer 250. Read (or read) data.

In addition, the parser and analyzer 220 interworks with the reader/writer 250 to store another audit log related to the last data read in one or more other blocks 260 among the plurality of blocks 260 .

In addition, the parser and analyzer 220 provides (or transmits) the data search result to the client. Here, the data retrieval result includes information on the object to be queried by the client 100 (eg, information on object retrieval failure when object retrieval fails, information on the corresponding object when object retrieval succeeds, etc.), date and including visual information, etc.

If the received SQL command is a preset insert query (or update query), the parser and analyzer 220 performs database authority (eg, schema, database, privileges on tables, etc.)

As a result of the above check, if permission check fails (or if the login information related to the client 100 does not have data load/database permission/unset), the storage 200 (or the storage 200) The parser and analyzer 220 included in ) provides (or transmits) information indicating that there is no authority for data loading to the client 100 .

In addition, as a result of the above check, if the authorization check is successful (or if the log-in information related to the client 100 is in a state where the authorization for data loading/database is present/set), the parser and analyzer 220 executes an SQL command ( Or perform parsing and analysis functions for insert query/update query).

In addition, the parser and analyzer 220 interworks with the reader/writer 250 to record an audit log for a corresponding SQL command (or insert query/update query) at one or more blocks 260 among the plurality of blocks 260. ) is stored in

In addition, the parser and analyzer 220 requests the planner 230 included in the storage 200 to load data.

In addition, the parser and analyzer 220 receives result information related to data loading provided from the worker 240 according to data loading.

In addition, the parser and analyzer 220 interworks with the reader/writer 250 to store other audit logs related to data loading in one or more other blocks 260 among the plurality of blocks 260 .

Also, the parser and analyzer 220 provides (or transmits) the data loading result to the client. Here, the data loading result includes information on whether the data to be loaded by the client 100 has been successfully loaded (eg, data loading failure information, data loading success information, etc.), date and time information, and the like.

The planner 230 communicates with the loader 210 , the parser and analyzer 220 , the worker 240 , the reader/writer 250 , and the plurality of blocks 260 .

In addition, the planner 230 performs a function of determining the data read order and merge/reduce order by referring to indexes or data statistical values according to the SQL requested for analysis. do.

In addition, if the received SQL command is a preset create query, the planner 230 checks meta data based on the object creation request from the parser and analyzer 220, and determines the location of the object (or the object to be created). Check whether the object exists in the metadata/whether a directory or file related to the object to be created exists).

In addition, the planner 230 determines the status of the loader 210 included in the storage 200 (eg, process utilization/throughput) and the status of the reader/writer 250 (eg, process utilization/throughput). including processing rate, etc.) are checked respectively.

In addition, the planner 230 determines information contained in the storage 200 based on the SQL command, the location of the checked object, the checked state of the loader 210 and the reader/writer 250, and the like. The worker 240 is requested to create an object.

In addition, when the received SQL command is a preset select query, the planner 230 determines the status of the loader 210 (for example, process usage rate / processing rate, etc.) is checked.

In addition, the planner 230 requests the worker 240 to load data based on the SQL command and the checked state of the loader 210 . At this time, the planner 230 checks the component state (including, for example, the state of the loader 210, etc.) and requests a data load to a component of the system with low usage, thereby improving the operational efficiency of the entire system. there is.

In addition, when the received SQL command is a preset insert query (or update query), the planner 230 checks meta data according to a data load request from the parser and analyzer 220, and locates the data. (or whether the object to be loaded does not exist in meta data) is queried (or checked).

In addition, the planner 230 checks the status of the loader 210 (including, for example, process utilization/throughput) and the status of the reader/writer 250 (including, for example, process utilization/throughput). .

In addition, the planner 230 determines the worker 240 based on the SQL command, the location of the checked object, the checked state of the loader 210, the checked state of the reader/writer 250, and the like. Request data loading.

The worker 240 communicates with the loader 210 , the parser and analyzer 220 , the planner 230 , the reader/writer 250 , and the plurality of blocks 260 .

In addition, the worker 240 requests the reader/writer 250 to store/read data, reads only a necessary part of the read data, or merges/reduces the read data to match the requested SQL syntax. It performs the function of creating the final data that fits.

Also, when the received SQL command is a preset create query, the worker 240 requests the reader/writer 250 to create an object based on the object creation request of the planner 230 .

In addition, when a related object is created in the reader/writer 250 according to the object creation request, the worker 240 registers object mapping related to the created object in the metadata.

In addition, the worker 240 provides result information related to object creation to the parser and analyzer 220 .

When the received SQL command is a preset select query, the worker 240 determines the status of the reader/writer 250 (eg, process utilization/throughput, etc.) according to the planner 230's data load request. check the

In addition, the worker 240 loads data (or data corresponding to the select query) from the reader/writer 250 based on the checked state of the reader/writer 250 .

In addition, the worker 240 reduces only a necessary data part according to the select query among the loaded data to generate (or create) final data suitable for the corresponding select query that the corresponding client 100 intends to retrieve. ).

In addition, the worker 240 records (or writes/writes) the generated (or created) final data to the reader/writer 250 .

In addition, the worker 240 transmits information related to the final data recorded in the reader/writer 250 (eg, including block information in which the final data is recorded, block location information, etc.), the generated final data, and the like. Provided (or transmitted) to the parser and analyzer 220. At this time, when the amount of data is small (or when the capacity of the generated final data is less than a preset reference value), the worker 240 directly transmits the generated final data to the parser and analyzer 220 through communication. In addition, when the amount of data is large (or when the capacity of the generated final data exceeds the reference value), the worker 240 instead of transmitting the generated final data, the final data recorded in the reader/writer 250 Data-related information (eg, block information in which the final data is recorded, block location information, etc.) is delivered to the parser and analyzer 220 .

In addition, when the received SQL command is a preset insert query (or update query), the worker 240 interworks with the reader/writer 250 according to the data load request of the planner 230, / Loads (or writes) the data to be loaded in the corresponding client 100 into the writer 250. At this time, the table must be created in advance, and the number of columns in the table and the separator in the file must be the same. Also, if a partition exists, the partition must be specified.

In addition, the worker 240 changes (or updates) information (eg, including an index) of corresponding meta data according to data loading.

In addition, the worker 240 provides result information related to data loading to the parser and analyzer 220 .

The reader/writer 250 communicates with the loader 210, the parser and analyzer 220, the planner 230, the worker 240, and the plurality of blocks 260.

In addition, the reader/writer 250 performs a function of directly storing or reading data into a file in the distributed storage 200 .

In addition, when the received SQL command is a preset create query, the reader/writer 250 interworks with the parser and analyzer 220 to create an audit log for the corresponding SQL command (or create query) in the plurality of Store in one or more blocks 260 of the blocks 260.

In addition, the reader/writer 250 creates an object (or mapped directory/file) related to the SQL command based on the object creation request of the worker 240.

In addition, the reader/writer 250 works with the parser and analyzer 220 to store other audit logs related to previously created objects in one or more other blocks 260 among the plurality of blocks 260 .

As such, when the received SQL command is a preset create query, the storage 200 stores an object (or database object) (eg, database, table, partition) corresponding to the received SQL command (or create query). etc.) is created, and the object creation result (or database object creation result) is provided (or transmitted) to the client 100.

When the received SQL command is a preset select query, the reader/writer 250 interworks with the parser and analyzer 220 to write an audit log for the corresponding SQL command (or select query) to the plurality of blocks ( 260) in one or more blocks 260.

In addition, the reader/writer 250 interworks with the worker 240 to record (or load) final data generated by the corresponding worker 240 .

In addition, the reader/writer 250 interworks with the parser and analyzer 220 to store another audit log related to the final data in one or more other blocks 260 among the plurality of blocks 260 .

As such, when the received SQL command is a preset select query, the storage 200 searches for data corresponding to the received SQL command (or select query), and sends the data search result to the client 100. Provide (or send).

In addition, when the received SQL command is a preset insert query (or update query), the reader/writer 250 interworks with the parser and analyzer 220 to generate the corresponding SQL command (or insert query/update query) An audit log for is stored in one or more blocks 260 of the plurality of blocks 260 .

In addition, the reader/writer 250 interworks with the worker 240 to load (or write) data to be loaded in the corresponding client 100 into the reader/writer 250 .

In addition, the reader/writer 250 interworks with the parser and analyzer 220 to store other audit logs related to data loading in one or more other blocks 260 among the plurality of blocks 260 .

In this way, when the received SQL command is a preset insert query (or update query), the storage 200 responds to the received SQL command (or insert/update query) by requesting a load from the client 100. Data is loaded into the storage 200 (or database), and data loading results are provided (or transmitted) to the client 100 .

In addition, when information related to the source file is received, the reader/writer 250 checks the authority for data loading, and then creates an audit log for the information related to the source file in conjunction with the loader 210. It is stored in one or more blocks 260 of the plurality of blocks 260.

In addition, when the location of the loaded file is the same server or external storage, the reader/writer 250 interworks with the loader 210 to obtain information related to the source file, the location of the identified object, and the check Load (or write) the data (or the source file) to be loaded by the corresponding client 100 into the reader/writer 250 based on the checked loader 210 state, the checked writer 250 state, etc. )do.

In addition, the reader/writer 250 interworks with the loader 210 to store other audit logs related to data loading in one or more other blocks 260 among the plurality of blocks 260 .

As such, if the location of the loaded file is the same server or external storage, the same server directly reads the file, and the external system (or external storage) uses S3 or a communication protocol (eg http, https, RPC (Remote Procedure) Call), IPC (Inter Process Communication), etc.) can be used to read and load files.

In addition, when the loading of the file is a copy in storage, the reader/writer 250 interworks with the loader 210 to obtain information related to the source file, the location of the checked object, and the checked loader ( Based on the state of 210), the state of the reader/writer 250, etc., data (or directory/file) is deleted from the reader/writer 250.

In addition, the reader/writer 250 interworks with the loader 210 to load data (or directory/file/source file) to be loaded in the corresponding client 100 into the reader/writer 250 (or record).

In addition, the reader/writer 250 interworks with the loader 210 to store another audit log related to data loading in another one or more blocks 260 among the plurality of blocks 260 .

In this way, when the loading of the file is copying in the storage, if the same directory or file exists, the directory or file can be deleted and then loaded.

In addition, in this way, when information related to the source file is received, the storage 200 transmits the data (or source file) requested by the client 100 to be loaded in response to the received information related to the source file. 200 (or database), and provides (or transmits) the data loading result to the client 100.

In addition, the reader/writer 250 may perform an encryption function for information (or data) using an encryption key.

Also, the reader/writer 250 may perform a decryption function for the encrypted information using a decryption key corresponding to the encryption key.

The plurality of blocks 260 communicate with (or connect to) the loader 210, the parser and analyzer 220, the planner 230, the worker 240, the reader/writer 250, and the like.

Also, some blocks 260 among the plurality of blocks 260 record audit logs under the control of the loader 210 or the parser and analyzer 220 .

Also, some of the blocks 260 among the plurality of blocks 260 record (or load) data under the control of the loader 210 or the parser and analyzer 220 .

Also, when the received SQL command is a preset delete query, the storage 200 performs a delete function for table data to be deleted by the client 100 . At this time, the storage 200 deletes only data of the table, and does not delete meta information related to the data.

In addition, the storage 200 generates a table data deletion result according to data deletion of the corresponding table, and provides (or transmits) the created table data deletion result to the client 100 . Here, the data deletion result of the table includes a table name to be deleted from the client 100, data to be deleted, data deletion date and time information, and the like.

Also, when the received SQL command is a preset truncate query, the storage 200 performs a delete function for table data to be deleted by the client 100 . At this time, the storage 200 deletes only data of the table, and does not delete meta information related to the data. Here, the difference between the delete query and the truncate query is that data deleted by the corresponding delete query dp is moved to the recycle bin (or temporarily deleted file storage area) for later restoration and then deleted after a preset period of time.

In addition, the storage 200 generates a table data deletion result according to data deletion of the corresponding table, and provides (or transmits) the created table data deletion result to the client 100 . Here, the data deletion result of the table includes a table name to be deleted from the client 100, data to be deleted, data deletion date and time information, and the like.

Also, when the received SQL command is a preset drop query, the storage 200 performs a delete function for table data to be deleted by the client 100 . At this time, the storage 200 deletes meta information related to the data of the corresponding table along with the data of the table.

In addition, the storage 200 generates a table data deletion result according to deletion of data and related meta information in the corresponding table, and provides (or transmits) the created table data deletion result to the client 100. Here, the data deletion result of the table includes a table name to be deleted from the client 100, data to be deleted, meta information related to the deleted data, data deletion date and time information, and the like.

In addition, when the received SQL command is a preset grant query, the storage 200 is directed to a specific client 100 to which permission is to be assigned to a database for providing (or assigning) permission in the client 100. Executes the privilege assignment function for the database.

In addition, the storage 200 generates a permission allocation result according to the permission allocation for the corresponding database, and provides (or transmits) the generated permission allocation result to the client 100 . Here, the permission allocation result includes the database name for providing (or assigning) the permission to the client 100, information on a specific client 100 to which the permission is to be assigned, date and time information of permission assignment, and the like.

In addition, when the received SQL command is a preset revoke query, the storage 200 is a database corresponding to another specific client 100 that wants to release privileges for the database for releasing privileges from the client 100. Performs permission release function for .

In addition, the storage 200 generates a permission release result according to permission release for the corresponding database, and provides (or transmits) the generated permission release result to the client 100 . Here, the permission release result includes a database name for releasing permission from the client 100, information on another specific client 100 to release permission, date and time information of permission release, and the like.

In this way, objects can be created based on storage, data can be retrieved, and data can be loaded.

In addition, a meta management function may be provided for data managed based on storage in this way.

Hereinafter, a method for controlling a storage-based DBMS system according to the present invention will be described in detail with reference to FIGS. 1 to 3 .

3 is a flowchart illustrating a control method of a storage-based DBMS system according to an embodiment of the present invention.

First, the client 100 performs a login procedure (or login function) through one storage 200 having a high process or system margin among the plurality of storages 200 . At this time, the client 100 may perform the login procedure using a pre-registered ID and password, a barcode or QR code including the ID, a preset authentication token, and the like.

For example, the first client 100 performs a login procedure using the first storage 200 among the plurality of storages 200, a first ID, and a first password (S1110).

Thereafter, the storage 200 receives information related to a SQL command or source file according to a user input (or user selection/touch/control) of the client 100 . Here, the SQL commands include create query, select query, insert/update query, delete query, truncate query, drop query, grant query, revoke query, and the like. In addition, the information related to the source file includes information on the source file hostname, port, source file format and separator, schema, database, table, load file format and separator, partition, and the like.

For example, the first storage receives a first SQL command including a first create query to create a new object (eg, a first table) according to a user input of the first client.

As another example, the first storage receives a second SQL command including a second select query to retrieve data included in the first column or the second column in the second table according to the user input of the first client. do.

As another example, the first storage receives a third SQL command including a third insert query to load third data into a third table according to a user input of the first client.

As another example, the first storage receives information related to a fourth source file in order to load a fourth file according to a user input of the first client (S1120).

Then, when the received SQL command is a preset create query, the storage 200 stores an object (or database object) (eg, database, table, partition, etc.) corresponding to the received SQL command (or create query). including), and provides (or transmits) an object creation result (or a database object creation result) to the client 100.

That is, when the received SQL command is a preset create query, the storage 200 (or the parser and analyzer 220 included in the storage 200) is based on login information related to the client 100. Check the privileges on the database (for example, privileges on schemas, databases, tables, etc.).

As a result of the above check, if the permission check is successful (or if the login information related to the client 100 has permission for the database/is set), the parser and analyzer 220 responds to the SQL command (or create query). It performs parsing and analysis functions for

In addition, the parser and analyzer 220 works with the reader/writer 250 included in the storage 200 to store audit logs for corresponding SQL commands (or create queries) in one or more of the plurality of blocks 260. Save to block 260.

In addition, the parser and analyzer 220 requests the planner 230 included in the storage 200 to create an object.

In addition, the planner 230 checks metadata based on the object creation request, and checks the location of the object (or whether the object to be created exists in the metadata/whether a directory or file related to the object to be created exists). ) to check.

In addition, the planner 230 determines the status of the loader 210 included in the storage 200 (eg, process utilization/throughput) and the status of the reader/writer 250 (eg, process utilization/throughput). including processing rate, etc.) are checked respectively.

In addition, the planner 230 determines information contained in the storage 200 based on the SQL command, the location of the checked object, the checked state of the loader 210 and the reader/writer 250, and the like. The worker 240 is requested to create an object.

In addition, the worker 240 requests the reader/writer 250 to create an object based on the object creation request.

In addition, the reader/writer 250 creates an object (or mapped directory/file) related to the SQL command based on the object creation request.

Also, the worker 240 registers object mapping related to the created object in the meta data.

In addition, the worker 240 provides result information related to object creation to the parser and analyzer 220 .

Also, the parser and analyzer 220 works with the reader/writer 250 to store other audit logs related to previously created objects in one or more other blocks 260 among the plurality of blocks 260 .

Also, the parser and analyzer 220 provides (or transmits) the object creation result to the client. Here, the object creation result includes information on whether or not the object to be created in the client 100 is created (eg, object creation failure information, object creation success information, etc.), date and time information, and the like.

In addition, the client 100 receives an object creation result provided from the storage 200 (or the parser and analyzer 220) in response to a previously input SQL command (including, for example, create query, etc.), The received object creation result is displayed (or output).

For example, when the received SQL command is a preset create query (eg, the first create query), the first parser and analyzer 220 included in the first storage stores login information related to the first client. Based on this, check the privileges on the database.

As a result of the check, when the first client has authority for the database, the first parser and analyzer performs parsing and analyzing functions for the first create query.

In addition, the first parser and analyzer interworks with the first reader/writer included in the first storage to store the 1-1 audit log for the 1st create query in the 1-1 of the plurality of blocks 260. Store in block 1 (260).

In addition, the first parser and analyzer requests the first planner included in the first storage to create an object.

In addition, the first planner checks meta data based on the object creation request to check the location of the object.

In addition, the first planner checks the state of the first loader 210 included in the first storage and the state of the first reader/writer 250 included in the first storage, respectively.

In addition, the first planner is included in the first storage based on the first create query, the location of the checked object, the checked state of the first loader, the checked state of the first reader/writer, and the like. The first worker 260 is requested to create an object.

In addition, the first worker requests the first reader/writer to create an object based on the object creation request.

In addition, the first reader/writer creates a first object (eg, a first table) corresponding to the first create query based on the object creation request.

Also, the first worker registers a first object mapping related to the created first object in the meta data.

In addition, the first worker provides first result information related to object creation to the first parser and analyzer.

In addition, the first parser and analyzer interworks with the first reader/writer and stores the first to second audit logs related to the generated first object in the first to second blocks 260 among the plurality of blocks. .

Also, the first parser and analyzer provides a first object creation result (eg, one table created) to the first client.

In addition, the first client receives a first object creation result provided from the first parser and analyzer in response to the first create query, and displays the received first object creation result (S1130).

In addition, when the received SQL command is a preset select query, the storage 200 searches data corresponding to the received SQL command (or select query) and provides a data search result to the client 100. (or transmit)

That is, when the received SQL command is a preset select query, the parser and analyzer 220 has database authority (eg, schema, database, table, etc.) based on login information related to the corresponding client 100. permission).

As a result of the check, if the authorization check is successful (or if the login information related to the client 100 has data inquiry/database authorization/set state), the parser and analyzer 220 executes an SQL command (or select query) to perform parsing and analysis functions.

In addition, the parser and analyzer 220 interworks with the reader/writer 250 to store an audit log for a corresponding SQL command (or select query) in one or more blocks 260 among the plurality of blocks 260. do.

In addition, the parser and analyzer 220 checks meta data based on a data search request, and searches for an index and data location (or an index and data location in relation to data to be searched).

Also, the parser and analyzer 220 requests a data plan from the planner 230 based on the searched index and data location.

In addition, the planner 230 checks the state of the loader 210 (eg, including process utilization/processing rate).

In addition, the planner 230 requests the worker 240 to load data based on the SQL command and the checked state of the loader 210 .

In addition, the worker 240 checks the state of the reader/writer 250 (eg, including process utilization/processing rate).

In addition, the worker 240 loads data (or data corresponding to the select query) from the reader/writer 250 based on the checked state of the reader/writer 250 .

In addition, the worker 240 reduces only a necessary data part according to the select query among the loaded data to generate (or create) final data suitable for the corresponding select query that the corresponding client 100 intends to retrieve. ).

In addition, the worker 240 records (or writes/writes) the generated (or created) final data to the reader/writer 250 .

In addition, the worker 240 transmits information related to the final data recorded in the reader/writer 250 (eg, including block information in which the final data is recorded, block location information, etc.) and the generated final data. Provided (or transmitted) to the parser and analyzer 220. At this time, when the amount of data is small (or when the capacity of the generated final data is less than a preset reference value), the worker 240 directly transmits the generated final data to the parser and analyzer 220 through communication. In addition, when the amount of data is large (or when the capacity of the generated final data exceeds the reference value), the worker 240 replaces the transmission of the generated final data with the final data recorded in the reader/writer 250. Data-related information (eg, block information in which the final data is recorded, block location information, etc.) is delivered to the parser and analyzer 220 .

In addition, when information related to the final data is received, the parser & analyzer 220 receives the final data from the reader/writer 250 based on the information related to the final data recorded in the reader/writer 250. Read (or read) data.

In addition, the parser and analyzer 220 interworks with the reader/writer 250 to store another audit log related to the last data read in one or more other blocks 260 among the plurality of blocks 260 .

In addition, the parser and analyzer 220 provides (or transmits) the data search result to the client. Here, the data search result includes information on the object to be searched by the client 100 (eg, including information on object search failure when object search fails, information on the corresponding object when object search succeeds, etc.), date and time, and including visual information, etc.

In addition, the client 100 receives a data search result provided from the storage 200 (or the parser and analyzer 220) in response to a previously input SQL command (eg, including a select query, etc.), The received data inquiry result is displayed (or output).

For example, when the received SQL command is a preset select query (eg, the second select query), the first parser and analyzer 220 included in the first storage stores login information related to the first client. Based on this, check the authority for data inquiry.

As a result of the confirmation, when the first client has the right to retrieve data, the first parser and analyzer performs parsing and analyzing functions for the second select query.

In addition, the first parser and analyzer interworks with the first reader/writer 250 included in the first storage to generate the 2-1 audit log for the second select query among the plurality of blocks 260. It is stored in the 2-1st block 260.

Also, the first parser and analyzer checks meta data based on the data search request, and searches for a second index and a location of second data related to a second table to be searched.

In addition, the first parser and analyzer requests a data plan from the first planner 230 included in the first storage based on the second index and the location of the second data.

Also, the first planner checks the state of the first loader 210 included in the first storage.

In addition, the first planner requests data load from the first worker 240 included in the first storage based on the second select query and the checked state of the first loader.

Also, the first worker checks the state of the first reader/writer.

Also, the first worker loads second data (or a second table) corresponding to the second select query from the first reader/writer based on the checked state of the first reader/writer.

In addition, the first worker reduces only the necessary data part (for example, the first column to the second column in the second table) according to the second select query among the loaded second data to obtain the corresponding second select query 2-1 data (or 2-1 table), which is the final data that fits, is created.

In addition, the first worker writes 2-1 data, which is the generated final data, to the first reader/writer.

In addition, the first worker provides information related to the 2-1 data recorded in the first reader/writer to the first parser and analyzer when the amount of the generated final data exceeds a preset reference value. .

In addition, the first parser and analyzer reads the 2-1 data, which is the final data, from the first reader/writer based on the information related to the 2-1 data recorded in the first reader/writer.

In addition, the first parser and analyzer interworks with the first reader/writer to store the 2-2 audit log related to the read 2-1 data in the 2-2 block 260 among the plurality of blocks. do.

In addition, the first parser and analyzer determines the second data search result (for example, the index included in the 2-1 table and the first column corresponding to Name and the second column corresponding to Age). 10 Kim 30, 20 Park 32, 30 Jeong 31, etc.) composed of rows are provided to the first client.

In addition, the first client receives a second data search result provided from the first parser and analyzer in response to the second select query, and displays the received second data search result (S1140).

In addition, when the received SQL command is a preset insert query (or update query), the storage 200 stores the data load-requested by the client 100 in response to the received SQL command (or insert/update query). is loaded into the storage 200 (or database), and a data loading result is provided (or transmitted) to the client 100.

That is, when the received SQL command is a preset insert query (or update query), the parser and analyzer 220 has database authority (e.g. schema, Privileges on databases, tables, etc.)

As a result of the check, if the authorization check is successful (or if the login information related to the client 100 has data load/database authorization/set), the parser and analyzer 220 executes an SQL command (or insert query/update query) to perform parsing and analysis functions.

In addition, the parser and analyzer 220 interworks with the reader/writer 250 to record an audit log for a corresponding SQL command (or insert query/update query) at one or more blocks 260 among the plurality of blocks 260. ) is stored in

In addition, the parser and analyzer 220 requests the planner 230 included in the storage 200 to load data.

In addition, the planner 230 checks meta data based on the data loading request, and inquires (or checks) the location of the data (or whether an object to be loaded does not exist in the meta data).

In addition, the planner 230 checks the status of the loader 210 (including, for example, process utilization/throughput) and the status of the reader/writer 250 (including, for example, process utilization/throughput). .

In addition, the planner 230 determines the worker 240 based on the SQL command, the location of the checked object, the checked state of the loader 210, the checked state of the reader/writer 250, and the like. Request data loading.

In addition, the worker 240 interworks with the reader/writer 250 to load (or record) data to be loaded in the corresponding client 100 into the reader/writer 250 .

In addition, the worker 240 changes (or updates) information (eg, including an index) of corresponding meta data according to data loading.

In addition, the worker 240 provides result information related to data loading to the parser and analyzer 220 .

In addition, the parser and analyzer 220 interworks with the reader/writer 250 to store other audit logs related to data loading in one or more other blocks 260 among the plurality of blocks 260 .

Also, the parser and analyzer 220 provides (or transmits) the data loading result to the client. Here, the data load result includes information on whether the data to be loaded by the client 100 has been successfully loaded (eg, data load failure information, data load success information, etc.), date and time information, and the like.

In addition, the client 100 receives a data load result provided from the storage 200 (or the parser and analyzer 220) in response to a previously entered SQL command (eg, insert query/update query, etc.). and displays (or outputs) the received data load result.

For example, when the received SQL command is a preset insert query (for example, the third insert query), the first parser and analyzer 220 included in the first storage stores login information related to the first client. Based on this, the authority for data loading is checked.

As a result of the confirmation, when the first client has the right to load data, the first parser and analyzer performs a function of parsing and analyzing the third insert query.

In addition, the first parser and analyzer interworks with the first reader/writer 250 included in the first storage to store the 3-1 audit log for the third insert query among the plurality of blocks 260. It is stored in the 3-1 block (260).

In addition, the first parser and analyzer requests the first planner 230 included in the first storage to load data.

In addition, the first planner checks meta data based on the data loading request, and searches for a location of data related to a third table to be loaded.

Also, the first planner checks the state of the first loader 210 included in the first storage and the state of the first reader/writer.

In addition, the first planner is included in the first storage based on the third insert query, the location of the checked object, the checked state of the first loader, the checked state of the first reader/writer, and the like. A data loading request is made to the first worker 240 .

In addition, the first worker loads third data into a third table of the first reader/writer in association with the first reader/writer.

In addition, the first worker changes information of corresponding meta data according to loading of the third data.

Also, the first worker provides third result information related to the loading of the third data to the first parser and analyzer.

In addition, the first parser and analyzer interworks with the first reader/writer and stores the 3-2 audit log related to the data loading in the 3-2 block 260 among the plurality of blocks.

Also, the first parser and analyzer provides a third data loading result (eg, 1 row inserted) to the first client.

In addition, the first client receives a third data load result provided from the first parser and analyzer in response to the third insert query, and displays the received third data load result (S1150).

In addition, when information related to the source file is received, the storage 200 transmits the data (or source file) requested by the client 100 to be loaded in response to the received information related to the source file to the storage 200. (or database), and provides (or transmits) the data loading result to the client 100.

That is, when information related to the source file is received, the loader 210 included in the storage 200 obtains database authority (eg schema, database, privileges on tables, etc.)

As a result of the check, if the authorization check is successful (or if the log-in information related to the client 100 has data loading/database authorization/set state), the loader 210 reads the reader/writer 250 In conjunction with, an audit log for information related to a corresponding source file is stored in one or more blocks 260 of the plurality of blocks 260.

Also, the loader 210 loads a file (or the source file).

When the location of the loaded file is the same server or external storage, the loader 210 checks the meta data and inquires (or checks) the location of the object to be loaded.

In addition, the loader 210 checks the state of the loader 210 (including, for example, process utilization rate/throughput rate, etc.) and the state of the reader/writer 250 (including, for example, process utilization rate/throughput rate, etc.) .

In addition, the loader 210 interworks with the reader/writer 250 to obtain information related to the source file, the location of the checked object, the state of the checked loader 210, and the checked writer 250. The data (or the source file) to be loaded in the corresponding client 100 is loaded (or written) into the reader/writer 250 based on the state of .

In addition, the loader 210 changes (or updates) information (eg, including an index) of corresponding meta data according to data loading.

In addition, the loader 210 interworks with the reader/writer 250 to store other audit logs related to data loading in one or more other blocks 260 among the plurality of blocks 260 .

In addition, the loader 210 provides (or transmits) the data loading result to the client 100 . Here, the data loading result is information on whether the data (or the source file) to be loaded by the client 100 has been successfully loaded (for example, data/source file loading failure information, data/source file loading success information, etc.) including), date and time information, etc.

In addition, the client 100 receives a data load result provided from the storage 200 (or the loader 210) in response to the previously provided source file related information, and displays the received data load result (or output).

In addition, when the loading of the file is copying in the storage, the loader 210 checks meta data and inquires (or checks) the location of the object to be loaded.

In addition, the loader 210 checks the state of the loader 210 (including, for example, process utilization rate/throughput rate, etc.) and the state of the reader/writer 250 (including, for example, process utilization rate/throughput rate, etc.) .

In addition, the loader 210 interworks with the reader/writer 250 to obtain information related to the source file, the location of the checked object, the checked state of the loader 210, and the reader/writer 250. Data (or directories/files) are deleted from the reader/writer 250 based on the status of .

In addition, the loader 210 interworks with the reader/writer 250 to load (or record).

In addition, the loader 210 changes (or updates) information (eg, including an index) of corresponding meta data according to data loading.

In addition, the loader 210 interworks with the reader/writer 250 to store another audit log related to data loading in another one or more blocks 260 among the plurality of blocks 260 .

In addition, the loader 210 provides (or transmits) other data loading results to the client. Here, the other data loading result includes information on whether the data to be loaded by the client 100 has been successfully loaded (eg, data loading failure information, data loading success information, etc.), date and time information, etc. .

In addition, the client 100 receives another data load result provided from the storage 200 (or the loader 210) in response to the information related to the previously provided source file, and the received other data load result display (or output).

For example, upon receiving the information related to the fourth source file, the first loader 210 included in the first storage checks the authority for data loading based on the login information related to the first client.

As a result of the check, when the first client has the right to load data, the first loader interworks with the first reader/writer 250 included in the first storage to obtain data related to the fourth source file. A 4-1 audit log for information is stored in the 4-1 block 260 among the plurality of blocks 260 .

Also, the first loader loads a fourth file included in information related to the fourth source file to be loaded.

When the location of the loaded fourth file is the same as the first storage, the first loader checks meta data and inquires the location of an object related to the fourth file to be loaded.

In addition, the first loader checks the state of the first loader and the state of the first reader/writer 250 included in the first storage.

In addition, the first loader interworks with the first reader/writer to obtain information related to the fourth source file, the location of the checked object, the checked state of the first loader, and the checked first reader/writer. The fourth file included in the information related to the fourth source file is loaded into the first reader/writer based on the state of .

In addition, the first loader changes corresponding meta data information according to data loading of the fourth file.

In addition, the 1st loader interworks with the 1st reader/writer and stores the 4-2nd audit log related to the loading of the 4th file in the 4-2nd block 260 among the plurality of blocks.

Also, the first loader provides a fourth data loading result (eg, 1 file inserted) to the first client.

In addition, the first client receives a fourth data loading result provided from the first loader in response to the information related to the fourth source file, and displays the received fourth data loading result.

As another example, upon receiving the information related to the fourth source file, the first loader 210 included in the first storage checks the authority for data loading based on the login information related to the first client. .

As a result of the check, when the first client has the right to load data, the first loader interworks with the first reader/writer 250 included in the first storage to obtain data related to the fourth source file. The 5-1 audit log for information is stored in the 5-1 block 260 among the plurality of blocks 260 .

Also, the first loader loads a fourth file included in information related to the fourth source file to be loaded.

When the loading of the loaded fourth file is a copy in storage, the first loader checks meta data and inquires the location of an object related to the fourth file to be loaded.

Also, the first loader checks a state of the first loader and a state of a first reader/writer included in the first storage.

In addition, the first loader interworks with the first reader/writer to obtain information related to the fourth source file, the location of the checked object, the checked state of the first loader, and the checked first reader/writer. Existing data is deleted from the first reader/writer based on the state of .

Also, the first loader loads a fourth file included in information related to the fourth source file to be loaded into the first reader/writer in association with the first reader/writer.

In addition, the first loader changes corresponding metadata information according to the loading of the fourth file.

In addition, the 1st loader interworks with the 1st reader/writer and stores the 5-2nd audit log related to the loading of the 4th file in the 5-2nd block 260 among the plurality of blocks.

Also, the first loader provides a fifth data loading result (eg, 1 file inserted) to the first client.

In addition, the first client receives a fifth data load result provided from the first loader in response to the information related to the fourth source file, and displays the received fifth data load result (S1160).

As described above, the embodiment of the present invention can improve the operational efficiency of the entire system according to parallel distributed processing by creating objects based on storage, retrieving data, and loading data.

In addition, as described above, the embodiment of the present invention provides a meta management function for data managed based on storage, thereby increasing meta data management efficiency.

The foregoing may be modified and modified by those skilled in the art without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are not intended to limit the technical idea of the present invention, but to explain, and the scope of the technical idea of the present invention is not limited by these embodiments. The protection scope of the present invention should be construed according to the following claims, and all technical ideas within the equivalent range should be construed as being included in the scope of the present invention.

10: storage-based DBMS system 100: client
200: multiple storage 210: loader
220: Parser and Analyzer 230: Planner
240: Walker 250: Reader/Writer
260: multiple blocks

Claims (10)

A client that provides information related to a SQL command or source file according to user input; and
A storage for performing one of an object creation function, a data search function, and a data loading function based on the SQL command or information related to the source file, and providing a function execution result to the client,
The storage is
a plurality of blocks of a preset size;
a reader/writer that creates an object related to the SQL command based on an object creation request;
When the received SQL command is a preset create query, the authority to the database is checked based on the login information related to the client, and when the authority check is successful, parsing and analysis of the SQL command are performed, and the reader/ a parser and analyzer that interworks with a writer to store an audit log for the SQL command in one or more blocks among the plurality of blocks and requests a planner to create an object;
Meta data is checked based on the object creation request, the location of the object is checked, the state of the loader and the reader/writer included in the storage are checked, respectively, the SQL command, the location of the checked object and , the planner requesting creation of an object from a worker included in the storage based on the checked state of the loader and the state of the reader/writer; and
Based on the object creation request, the reader/writer is requested to create an object, object mapping related to the object created by the reader/writer is registered in the meta data, and result information related to object creation is sent to the parser and analyzer. Including the worker provided,
The parser and analyzer,
Storage-based DBMS system characterized by storing another audit log related to the created object in one or more other blocks among the plurality of blocks in association with the reader/writer. According to claim 1,
Information related to the source file,
A storage-based DBMS system comprising at least one of a source file hostname, port, source file format and identifier, schema, database, table, load file format and identifier, and partition. delete Receiving, by the storage, information related to an SQL command or a source file according to a user input of a client;
performing, by the storage, one of an object creation function, a data inquiry function, and a data loading function based on the information related to the received SQL command or source file; and
Providing, by the storage, a function execution result to the client;
The step of performing any one of the object creation function, data search function, and data load function based on the received SQL command or information related to the source file,
When the received SQL command is a preset create query, checking authority for a database based on login information related to the client by a parser and analyzer included in the storage;
performing a parsing and analyzing function for the SQL command by the parser and analyzer when authority check is successful;
storing, by the parser and analyzer, an audit log for the SQL command in one or more blocks among a plurality of blocks, in conjunction with a reader/writer included in the storage;
requesting, by the parser and analyzer, object creation to a planner included in the storage;
confirming, by the planner, meta data based on the object creation request, and confirming the location of the object;
checking, by the planner, the state of the loader and the state of the reader/writer included in the storage, respectively;
requesting, by the planner, a worker included in the storage to create an object based on the SQL command, the location of the checked object, and the checked state of the loader and the reader/writer;
requesting, by the worker, object creation to the reader/writer based on the object creation request;
creating, by the reader/writer, an object related to the SQL command based on an object creation request;
registering, by the worker, object mapping related to the created object in the meta data;
providing, by the worker, result information related to object creation to the parser and analyzer; and
and storing another audit log related to the created object in one or more other blocks among the plurality of blocks by the parser and analyzer in conjunction with the reader/writer. control method. delete According to claim 4,
The step of performing any one of the object creation function, data search function, and data load function based on the received SQL command or information related to the source file,
When the received SQL command is a preset select query, checking authority for a database based on login information related to the client by a parser and analyzer included in the storage;
performing a parsing and analyzing function for the SQL command by the parser and analyzer when authority check is successful;
storing, by the parser and analyzer, an audit log for the SQL command in one or more blocks among a plurality of blocks, in conjunction with a reader/writer included in the storage;
checking meta data based on a data search request by the parser and analyzer, and searching for an index and data location;
requesting a data plan from a planner included in the storage based on the searched index and data location by the parser and analyzer;
checking a state of a loader included in the storage by the planner;
requesting, by the planner, to load data from a worker included in the storage based on the SQL command and the checked state of the loader;
checking a state of the reader/writer by the worker;
loading data from the reader/writer based on the checked reader/writer state by the worker;
generating, by the worker, final data suitable for the select query desired by the client by reducing only a necessary data portion according to the select query among the loaded data;
writing the generated final data to the reader/writer by the worker; and
and providing, by the worker, information related to final data recorded in the reader/writer or the generated final data to the parser and analyzer. According to claim 6,
receiving, by the parser and analyzer, information related to final data recorded in the reader/writer provided from the worker or the generated final data;
reading the final data from the reader/writer based on the information related to the final data recorded in the reader/writer by the parser and analyzer when the information related to the final data is received; and
and storing, by the parser and analyzer, another audit log related to the final data read in one or more other blocks among the plurality of blocks, in conjunction with the reader/writer. How to control the system. According to claim 4,
The step of performing any one of the object creation function, data search function, and data load function based on the received SQL command or information related to the source file,
When the received SQL command is a preset insert query, checking authority for a database based on login information related to the client by a parser and analyzer included in the storage;
performing a parsing and analyzing function for the SQL command by the parser and analyzer when authority check is successful;
storing, by the parser and analyzer, an audit log for the SQL command in one or more blocks among a plurality of blocks, in conjunction with a reader/writer included in the storage;
requesting, by the parser and analyzer, to load data from a planner included in the storage;
checking the meta data based on the data load request by the planner, and inquiring the location of the data;
checking, by the planner, the state of the loader and the state of the reader/writer included in the storage;
requesting, by the planner, to load data from a worker included in the storage based on the SQL command, the location of the checked object, and the checked state of the loader and the reader/writer;
loading data desired to be loaded by the client into the reader/writer by the worker in conjunction with the reader/writer;
changing metadata information according to data loading by the worker;
providing, by the worker, result information related to data loading to the parser and analyzer; and
and storing another audit log related to data loading in one or more other blocks among the plurality of blocks by the parser and analyzer in conjunction with the reader/writer. method. According to claim 4,
The step of performing any one of the object creation function, data search function, and data load function based on the received SQL command or information related to the source file,
verifying, by a loader included in the storage, authority to a database based on login information related to the client when receiving information related to the source file;
storing, by the loader, an audit log for information related to the source file in at least one block among a plurality of blocks, in conjunction with a reader/writer included in the storage, when the authority check is successful;
loading a file by the loader;
when the location of the loaded file is the same server or external storage, checking meta data by the loader to inquire the location of an object to be loaded;
checking a state of the loader and a state of the reader/writer by the loader;
By the loader, in conjunction with the reader/writer, the client to the reader/writer based on the information related to the source file, the location of the checked object, the checked loader status, and the checked writer status A process of loading data to be loaded in;
a process of changing meta data information according to data loading by the loader; and
and storing, by the loader, another audit log related to data loading in one or more other blocks among the plurality of blocks, in conjunction with the reader/writer. According to claim 4,
The step of performing any one of the object creation function, data search function, and data load function based on the received SQL command or information related to the source file,
verifying, by a loader included in the storage, authority to a database based on login information related to the client when receiving information related to the source file;
storing, by the loader, an audit log for information related to the source file in at least one block among a plurality of blocks, in conjunction with a reader/writer included in the storage, when the authority check is successful;
loading a file by the loader;
when the loading of the file is copying in storage, checking the meta data by the loader and inquiring the location of the object to be loaded;
checking a state of the loader and a state of the reader/writer by the loader;
By the loader, in conjunction with the reader/writer, data is read from the reader/writer based on the information related to the source file, the location of the checked object, the checked loader status, and the checked writer status process of deleting;
loading data to be loaded by the client into the reader/writer by the loader in conjunction with the reader/writer;
a process of changing meta data information according to data loading by the loader; and
A method of controlling a storage-based DBMS system, comprising the step of storing, by the loader, another audit log related to data loading in one or more other blocks among the plurality of blocks, in conjunction with the reader/writer. .

Images