A data table creation method, device, electronic equipment, storage medium and program product

Abstract

A data table creation method and device, electronic equipment, storage medium and program product are disclosed. Specific implementation schemes include: determining a metadata submission state; in the case where the metadata submission state indicates that the target metadata submission fails, determining a data submission stage; and determining a creation result of the data table based on the data submission stage and creation state information. The submission state of the target metadata corresponding to the data table is determined based on the metadata submission state, so as to detect abnormal conditions of the data table creation process. The creation result of the data table is determined based on the data submission stage and the creation state information, so as to solve the abnormal conditions in the data table creation process and improve the reliability of the data table creation.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method, apparatus, electronic device, storage medium, and program product for creating data tables. Background Technology

[0002] In cloud-native or distributed databases, table creation is typically not a one-time writing of metadata, but rather a multi-stage process. During table creation, the system might first allocate object identifiers such as table, index, partition, and tablet, then write metadata like remotetablet / index, followed by child metadata like tablet, index, and partition in the catalog, and finally write the user-visible parent metadata (table). If the preceding low-level metadata (metadata or child metadata) has been written, but the final parent metadata has not been successfully written, a problem arises: the SQL layer cannot see the table, but the low-level metadata remains in the metadata service. This type of low-level metadata lacks parent metadata anchoring and can be called orphan metadata.

[0003] Due to several practical impacts of orphan metadata, the final table creation process is in an "uncertain" state when writing to the parent metadata. For example, the metadata service may have actually committed successfully, but the orphan metadata causes the response to be lost in the network, and the compute nodes see a timeout or failure. In this case, if the compute nodes directly delete all low-level metadata, they may mistakenly delete a table that has actually been successfully created; if they do not handle it at all, orphan metadata may remain, thus affecting the table creation process. Summary of the Invention

[0004] This invention provides a method, apparatus, electronic device, storage medium, and program product for creating data tables, in order to resolve abnormal situations during the table creation process and improve the reliability of table creation.

[0005] According to one aspect of the present invention, a method for creating a data table is provided, comprising: Determine the metadata submission status, which includes the submission status of the target metadata, which includes the metadata corresponding to the process of creating the data table; If the metadata submission status indicates that the target metadata submission has failed, a data submission phase is determined, the data submission phase indicating the process of creating the data table; Based on the data submission stage and creation status information, the creation result of the data table is determined, and the creation status information includes the identification information of the target metadata.

[0006] According to another aspect of the present invention, a data table creation apparatus is provided, comprising: The first determining module is used to determine the metadata submission status, which includes the submission status of the target metadata, and the target metadata includes the metadata corresponding to the process of creating the data table; The second determining module is used to determine the data submission stage when the metadata submission status indicates that the target metadata submission has failed, wherein the data submission stage indicates the process of creating the data table; The third determining module is used to determine the creation result of the data table based on the data submission stage and creation status information, wherein the creation status information includes the identification information of the target metadata.

[0007] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the data table creation method according to any embodiment of the present invention.

[0008] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the data table creation method according to any embodiment of the present invention.

[0009] According to another aspect of the present invention, a computer program product is provided, the computer program product comprising a computer program that, when executed by a processor, implements the data table creation method described in any embodiment of the present invention.

[0010] The technical solution of this invention involves determining the metadata submission status; if the metadata submission status indicates that the target metadata submission has failed, determining the data submission stage; and determining the creation result of the data table based on the data submission stage and creation status information. By determining the submission status of the target metadata corresponding to the data table through the metadata submission status, abnormal situations in the data table creation process can be detected. By determining the creation result of the data table through the data submission stage and creation status information, abnormal situations in the data table creation process are resolved, improving the reliability of data table creation.

[0011] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0012] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0013] Figure 1 This is a flowchart of a data table creation method provided in Embodiment 1 of the present invention; Figure 2 This is a flowchart of a method for determining the creation result according to Embodiment 2 of the present invention; Figure 3 This is a flowchart of a second submission stage provided according to Embodiment 2 of the present invention; Figure 4 This is a schematic diagram of the structure of a data table creation device according to Embodiment 3 of the present invention; Figure 5 This is a block diagram of an electronic device provided according to Embodiment 4 of the present invention. Detailed Implementation

[0014] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0015] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0016] Example 1 Figure 1This is a flowchart of a data table creation method according to Embodiment 1 of the present invention. This embodiment is applicable to the creation of data tables. The method can be executed by a data table creation device, which can be implemented in hardware and / or software. The data table creation device can be configured in an electronic device, which can be equipped with computing nodes. Figure 1 As shown, the method includes: S110. Determine the metadata submission status.

[0017] The metadata submission status includes the submission status of the target metadata, which includes the metadata corresponding to the process of creating the data table.

[0018] In this embodiment, the metadata submission status can be understood as the submission status of the target metadata involved in the process of creating a data table. Target metadata can be understood as the metadata involved in the process of creating a data table, and target metadata may include child metadata, parent metadata, etc.

[0019] Specifically, after a user initiates a data table creation operation, the compute nodes sequentially write the target metadata into the metadata service, and the metadata service then submits the target metadata back to the compute nodes. During this process, the submission status of the target metadata is monitored as the metadata submission status. Therefore, the metadata submission status indicates whether the target metadata has been successfully submitted.

[0020] For example, target metadata may include table parent metadata, tablet child metadata, index child metadata, partition child metadata, catalog metadata, remote metadata, etc. During the creation of a data table, object IDs such as table, index, partition, and tablet are first assigned, then remote tablet / index metadata is written, then child metadata such as tablet, index, and partition in the catalog are written, and finally the user-visible table parent metadata is written.

[0021] S120. If the metadata submission status indicates that the target metadata submission has failed, determine the data submission stage.

[0022] The data submission phase indicates the process of creating the data table.

[0023] In this embodiment, the data submission phase can indicate the data table creation process, and the data submission phase can be determined by whether the first parent metadata contained in the target metadata has been successfully submitted. The first parent metadata can be understood as the parent metadata contained in the target metadata, and the first parent metadata can be used to anchor metadata other than the first parent metadata in the target metadata.

[0024] Specifically, if the metadata commit status indicates that the target metadata commit failed, it means that the data table creation process has been forced to pause. In this case, it is necessary to determine the data commit status based on whether the first parent metadata contained in the target metadata has been committed.

[0025] S130. Based on the data submission stage and creation status information, determine the creation result of the data table.

[0026] The creation status information includes the identification information of the target metadata.

[0027] In this embodiment, creation status information can be understood as the identification information of the target metadata recorded during the creation process of the data table. Creation status information can be used to identify the target metadata involved in the data table creation process. Creation result can indicate whether the data table was successfully created, and the creation result can include creation success, creation failure, and creation exception. A creation exception indicates that it is impossible to determine whether the data table was successfully created.

[0028] Specifically, when the metadata submission status indicates that the target metadata submission failed, the creation result of the data table is determined based on the identified data submission stage and the creation status information. If the data submission stage indicates that the first parent metadata has not yet been submitted, the creation result of the data table can be directly determined as creation failure. If the data submission stage indicates that the first parent metadata has been submitted, further operations are required to determine the creation result of the data table.

[0029] The technical solution of this invention involves determining the metadata submission status; if the metadata submission status indicates that the target metadata submission has failed, determining the data submission stage; and determining the creation result of the data table based on the data submission stage and creation status information. By determining the submission status of the target metadata corresponding to the data table through the metadata submission status, abnormal situations in the data table creation process can be detected. By determining the creation result of the data table through the data submission stage and creation status information, abnormal situations in the data table creation process are resolved, improving the reliability of data table creation.

[0030] Based on the above embodiments, modified embodiments of the above embodiments are proposed. It should be noted that, in order to keep the description brief, only the differences from the above embodiments are described in the modified embodiments.

[0031] In one embodiment, the determination of the data submission phase includes: If the first parent metadata contained in the target metadata is not committed, the data submission stage corresponding to the data table is determined as the first submission stage. The first parent metadata includes the parent metadata in the target metadata. The first parent metadata is used to anchor the metadata in the target metadata other than the first parent metadata. If the first parent metadata contained in the target metadata has been committed, the data commit stage corresponding to the data table is determined to be the second commit stage.

[0032] In this embodiment, the first submission phase can be understood as the phase in which the first parent metadata has not yet been submitted to the metadata service. The second submission phase can be understood as the phase in which the first parent metadata has been submitted to the metadata service, but no response signal has been received from the metadata service.

[0033] Specifically, if the first parent metadata contained in the target metadata has not been committed, it means the target metadata commit failure occurred before the first parent metadata was committed, and the data commit stage corresponding to the data table is determined to be the first commit stage. If the first parent metadata contained in the target metadata has been committed, it means the first parent metadata has been committed to the metadata service, but no response signal has been received from the metadata service. Reasons for this situation include, for example, network communication failure or timeout between the compute node and the metadata service. In this case, it cannot be determined whether the metadata service received the first parent metadata sent by the compute node; therefore, the data commit stage corresponding to the data table is determined to be the second commit stage.

[0034] In one embodiment, prior to determining the metadata submission status, the method further includes: In response to a second creation operation of the data table, an object identifier is assigned to the data table, the object identifier including an identifier of the target metadata; The object identifier is recorded in the creation status information.

[0035] In this embodiment, the second creation operation can be understood as a user-initiated data table creation operation. The object identifier can be understood as the identifier of the target metadata.

[0036] For example, once an object identifier is assigned during the creation of a data table, the object identifier is recorded in the creation status information. Object identifiers can include table id (table object identifier), index id (index object identifier), partition id (partition object identifier), tablet id (shard object identifier), etc. The creation status information ensures that even if the parent metadata of the table is not subsequently written, it knows which child metadata should be cleaned up.

[0037] Example 2 Figure 2 This is a flowchart of a method for determining the creation result according to Embodiment 2 of the present invention. This embodiment focuses on the method for determining the creation result of the data table in the above embodiment. Figure 2 As shown, the method includes: S210. Determine the metadata submission status.

[0038] S220. If the metadata submission status indicates that the target metadata submission has failed, determine the data submission stage.

[0039] S230. If the data submission stage is the first submission stage, determine that the creation result of the data table is a creation failure, and clear the target metadata corresponding to the creation status information.

[0040] Specifically, if the data submission phase is the first submission phase, it means the target metadata submission failure occurred before the final first parent metadata submission. It can be determined that the second creation operation of the data table initiated by the user failed. In this case, based on the object identifier contained in the creation status information, the target metadata already written to the metadata service during the creation process of this data table is cleared.

[0041] For example, the target metadata corresponding to the creation status information may include catalog metadata and remote metadata.

[0042] S240. If the data submission stage is the second submission stage, determine the readback result and determine the creation result of the data table based on the readback result.

[0043] The readback result indicates whether the second parent metadata was successfully read, which includes parent metadata read from the metadata service.

[0044] In this embodiment, the readback result indicates whether the second parent metadata was successfully read, which can be achieved by the compute node reading the second parent metadata from the metadata service. The second parent metadata can be understood as the parent metadata contained in the metadata service.

[0045] Specifically, if the data submission phase is the second submission phase, it means the target metadata submission failed after the first parent metadata had already been submitted. At this point, the first parent metadata has been submitted to the metadata service, but no response signal has been received from the metadata service. Therefore, the target metadata corresponding to the creation status information cannot be immediately cleared. Instead, an attempt should be made to read back the second parent metadata from the metadata service, determine the readback result, and decide on the next action based on the result.

[0046] Optionally, determining the creation result of the data table based on the readback result includes: If the readback result is successful, determine the second parent metadata. If the second parent metadata matches the first parent metadata, then determine that the creation result of the data table is successful; otherwise, determine that the creation result of the data table is abnormal. If the readback result is a read failure, the creation result of the data table is determined to be a creation exception, and a recovery anchor point is created, which includes the target metadata.

[0047] In this embodiment, the recovery anchor point can be used to record target metadata. The recovery anchor point can be used to enable subsequent recovery processes to relocate the metadata remaining in the recovery anchor point and perform deterministic cleanup.

[0048] Specifically, if the readback result indicates a successful read, the second parent metadata is determined. The first and second parent metadata are compared. If the second parent metadata matches the first parent metadata, it means the compute node has written the first parent metadata into the metadata service, completing the table construction, and the table creation result can be determined as successful. If the second parent metadata does not match the first parent metadata, it means it cannot be determined whether the first parent metadata was successfully written into the metadata service; therefore, it cannot be determined whether the table creation was successful, and the table creation result is determined to be a creation error.

[0049] If the read-back result indicates a read failure, it means that it cannot be determined whether the first parent metadata was successfully written to the metadata service. Therefore, the creation result of the data table is determined to be a creation exception. At this time, the target metadata corresponding to the creation status information cannot be cleared immediately, but the status cannot be discarded either. Therefore, a hidden recovery anchor point needs to be created, and the target metadata at this time needs to be written into the recovery anchor point so that subsequent processes can clean up the target metadata of this data table creation process.

[0050] Exemplary, exemplary Figure 3 This is a flowchart of a second submission stage provided according to Embodiment 2 of the present invention. Figure 3 As shown, the read result is determined by checking if the actual table row exists. If the table row exists, the read result is considered successful. If the table row does not exist, the read result is considered unsuccessful.

[0051] Optionally, after creating the recovery anchor point, the following steps are also included: In response to the first creation operation of the data table, the creation result of the data table is determined based on the recovery anchor point. The first creation operation includes a re-initiation of the creation operation of the data table after the data table creation fails and / or an anomaly occurs.

[0052] In this embodiment, the first creation operation can be understood as the user initiating another data table creation operation after the data table creation corresponding to the first creation operation fails or is abnormal.

[0053] Specifically, if the creation of a data table corresponding to the first creation operation fails or encounters an error, and the user initiates a second creation operation for the data table, the creation result of the data table corresponding to the second creation operation can be determined based on the recovery anchor. The recovery anchor is not a normally visible table, but rather the cleanup entry point for subsequent table creation retry or background recovery tasks.

[0054] The technical solution of this invention, when the data submission stage is the first submission stage, determines that the creation result of the data table is a creation failure and clears the target metadata corresponding to the creation status information; when the data submission stage is the second submission stage, determines the readback result and determines the creation result of the data table based on the readback result. By determining whether to perform the clearing operation during the data submission stage, the long-term persistence of orphan metadata is avoided, and accidental deletion of the data table is prevented, thus improving the reliability of data table creation.

[0055] Example 3 Figure 4 This is a schematic diagram of a data table creation device according to Embodiment 3 of the present invention. Figure 4 As shown, the device includes: The first determining module 310 is used to determine the metadata submission status, wherein the metadata submission status includes the submission status of the target metadata, and the target metadata includes the metadata corresponding to the process of creating the data table; The second determining module 320 is used to determine a data submission stage when the metadata submission status indicates that the target metadata submission has failed, wherein the data submission stage indicates the process of creating the data table; The third determining module 330 is used to determine the creation result of the data table based on the data submission stage and creation status information, wherein the creation status information includes the identification information of the target metadata.

[0056] The data table creation apparatus provided in this embodiment of the invention determines the metadata submission status through a first determining module; determines the data submission stage through a second determining module when the metadata submission status indicates that the target metadata submission has failed; and determines the data table creation result based on the data submission stage and creation status information through a third determining module. Through the cooperation of these modules, the submission status of the target metadata corresponding to the data table is determined by the metadata submission status to detect abnormal situations in the data table creation process, and the creation result is determined by the data submission stage and creation status information. This solves the problem of abnormal situations in the data table creation process and improves the reliability of data table creation.

[0057] In one embodiment, the second determining module 320 is specifically used for: If the first parent metadata contained in the target metadata is not committed, the data submission stage corresponding to the data table is determined as the first submission stage. The first parent metadata includes the parent metadata in the target metadata. The first parent metadata is used to anchor the metadata in the target metadata other than the first parent metadata. If the first parent metadata contained in the target metadata has been committed, the data commit stage corresponding to the data table is determined to be the second commit stage.

[0058] In one embodiment, the third determining module 330 includes: The first determining unit is used to determine that the creation result of the data table is a creation failure when the data submission stage is the first submission stage, and to clear the target metadata corresponding to the creation status information. The second determining unit is configured to determine the readback result when the data submission stage is the second submission stage, and determine the creation result of the data table based on the readback result. The readback result indicates whether the second parent metadata was successfully read, and the second parent metadata includes parent metadata read from the metadata service.

[0059] In one embodiment, the second determining unit includes: The first determining subunit is used to determine the second parent metadata if the read-back result is successful. If the second parent metadata matches the first parent metadata, the creation result of the data table is determined to be successful; otherwise, the creation result of the data table is determined to be abnormal. The second determining subunit is used to determine that the creation result of the data table is a creation exception when the readback result is a read failure, and to create a recovery anchor point, wherein the recovery anchor point includes a method for recording the target metadata.

[0060] In one embodiment, the second determining unit further includes a third determining subunit, specifically used for: In response to the first creation operation of the data table, the creation result of the data table is determined based on the recovery anchor point. The first creation operation includes a re-initiation of the creation operation of the data table after the data table creation fails and / or an anomaly occurs.

[0061] In one embodiment, the data table creation apparatus further includes an allocation module, specifically used for: In response to a second creation operation of the data table, an object identifier is assigned to the data table, the object identifier including an identifier of the target metadata; The object identifier is recorded in the creation status information.

[0062] The data table creation device provided in this embodiment of the invention can execute the data table creation method provided in any embodiment of the invention. Through the cooperation and collaborative work between the modules, the data table is created, and it has the corresponding functional modules and beneficial effects of the execution method.

[0063] Example 4 According to embodiments of the present invention, the present invention also provides an electronic device, a computer-readable storage medium, and a computer program product.

[0064] Figure 5 This is a block diagram of an electronic device according to Embodiment 4 of the present invention, which implements the data table creation method described in the embodiments of the present invention. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (such as helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0065] like Figure 5As shown, the electronic device 410 includes at least one processor 411 and a memory, such as a read-only memory (ROM) 412 or a random access memory (RAM), communicatively connected to the at least one processor 411. The memory stores computer programs executable by the at least one processor. The processor 411 can perform various appropriate actions and processes based on the computer program stored in the ROM 412 or loaded from storage unit 418 into the RAM 413. The RAM 413 can also store various programs and data required for the operation of the electronic device 410. The processor 411, ROM 412, and RAM 413 are interconnected via a bus 414. An input / output (I / O) interface 415 is also connected to the bus 414.

[0066] Multiple components in the electronic device are connected to the I / O interface 415, including: an input unit 416, such as a keyboard, mouse, etc.; an output unit 417, such as various types of displays, speakers, etc.; a storage unit 418, such as a disk, optical disk, etc.; and a communication unit 419, such as a network card, modem, wireless transceiver, etc. The communication unit 419 allows the electronic device to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0067] Processor 411 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 411 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 411 performs the various methods and processes described above, such as data table creation methods.

[0068] In some embodiments, the data table creation method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 418. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 410 via ROM 412 and / or communication unit 419. When the computer program is loaded into RAM 413 and executed by processor 411, one or more steps of the data table creation method described above may be performed. Alternatively, in other embodiments, processor 411 may be configured to perform the data table creation method by any other suitable means (e.g., by means of firmware).

[0069] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0070] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0071] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0072] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0073] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0074] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0075] In some embodiments, the computer program product includes a computer program that, when executed by a processor, implements the data table creation method provided in the embodiments of the present invention.

[0076] The technical solution of this invention provides a data table creation method, apparatus, electronic device, storage medium, and program product. It determines the metadata submission status; if the metadata submission status indicates that the target metadata submission has failed, it determines a data submission stage; based on the data submission stage and creation status information, it determines the creation result of the data table. By determining the submission status of the target metadata corresponding to the data table through the metadata submission status, it detects abnormal situations in the data table creation process. By determining the creation result of the data table through the data submission stage and creation status information, it solves the problem of abnormal situations in the data table creation process and improves the reliability of data table creation.

[0077] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0078] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A data table creating method characterized by comprising: include: Determine the metadata submission status, which includes the submission status of the target metadata, which includes the metadata corresponding to the process of creating the data table; If the metadata submission status indicates that the target metadata submission has failed, a data submission phase is determined, the data submission phase indicating the process of creating the data table; Based on the data submission stage and creation status information, the creation result of the data table is determined, and the creation status information includes the identification information of the target metadata.

2. The method of claim 1, wherein, The data submission determination stage includes: If the first parent metadata contained in the target metadata is not committed, the data submission stage corresponding to the data table is determined as the first submission stage. The first parent metadata includes the parent metadata in the target metadata. The first parent metadata is used to anchor the metadata in the target metadata other than the first parent metadata. If the first parent metadata contained in the target metadata has been committed, the data commit stage corresponding to the data table is determined to be the second commit stage.

3. The method of claim 1, wherein, The determination of the data table creation result based on the data submission stage and creation status information includes: If the data submission stage is the first submission stage, the creation result of the data table is determined to be a creation failure, and the target metadata corresponding to the creation status information is cleared; In the case that the data submission stage is the second submission stage, the readback result is determined, and the creation result of the data table is determined based on the readback result. The readback result indicates whether the second parent metadata was successfully read, and the second parent metadata includes parent metadata read from the metadata service.

4. The method of claim 3, wherein, Determining the creation result of the data table based on the readback result includes: If the readback result is successful, determine the second parent metadata. If the second parent metadata matches the first parent metadata, then determine that the creation result of the data table is successful; otherwise, determine that the creation result of the data table is abnormal. If the readback result is a read failure, the creation result of the data table is determined to be a creation exception, and a recovery anchor point is created, which includes the target metadata.

5. The method of claim 4, wherein, Following the creation of the recovery anchor point, the following is also included: In response to the first creation operation of the data table, the creation result of the data table is determined based on the recovery anchor point. The first creation operation includes a re-initiation of the creation operation of the data table after the data table creation fails and / or an anomaly occurs.

6. The method of claim 1, wherein, Before determining the metadata submission status, the following is also included: In response to a second creation operation of the data table, an object identifier is assigned to the data table, the object identifier including an identifier of the target metadata; The object identifier is recorded in the creation status information.

7. A data table creating apparatus characterized by comprising: include: The first determining module is used to determine the metadata submission status, which includes the submission status of the target metadata, and the target metadata includes the metadata corresponding to the process of creating the data table; The second determining module is used to determine the data submission stage when the metadata submission status indicates that the target metadata submission has failed, wherein the data submission stage indicates the process of creating the data table; The third determining module is used to determine the creation result of the data table based on the data submission stage and creation status information, wherein the creation status information includes the identification information of the target metadata.

8. An electronic device, comprising: The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the data table creation method according to any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the data table creation method according to any one of claims 1-6.

10. A computer program product, characterised in that, The computer program product includes a computer program that, when executed by a processor, implements the data table creation method according to any one of claims 1-6.

Images