Data mounting methods, devices, equipment, storage media and software products
By storing data type mounting configuration data in configuration files, the mounting location is automatically determined, solving the problem of poor data mounting flexibility in existing technologies. This achieves an efficient and flexible data mounting solution, reducing manpower consumption and time costs.
Patent Information
- Application Number
- CN202211436364.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-11-16
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2042-11-16
AI Technical Summary
Existing data mounting methods are inflexible, requiring the development of separate mounting programs for each type of data asset, and involve frequent code modifications, resulting in low efficiency.
The configuration file stores mount configuration data of various data types, automatically determines the mount location based on the data type, avoids code modification, and supports flexible changes to directory structure and mount rules.
It improves the efficiency and flexibility of data mounting, reduces manpower consumption and mounting time, and supports the rapid mounting of new data types and the dynamic adjustment of existing rules.
Smart Images

Figure CN115718631B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of cloud computing, and more particularly to a data mounting method, apparatus, device, storage medium, and program product. Background Technology
[0002] To manage data assets, they need to be mounted onto directories according to certain rules. Data assets include, but are not limited to, databases, database tables, and data interfaces. Different types of data assets have different directory structures, and the mounting rules used for different directory structures also differ.
[0003] Therefore, a separate mounting program needs to be developed for each type of data asset, and the data assets can be mounted to the corresponding directory by executing the mounting program.
[0004] However, the mounting rules mentioned above are hardcoded into the mounting program. A single mounting program can only be used with one directory structure. If the directory structure changes, the mounting rules must be modified accordingly through changes to the mounting program's code. Therefore, the existing mounting method is inflexible, time-consuming, labor-intensive, and inefficient. Summary of the Invention
[0005] This invention provides a data mounting method, apparatus, device, storage medium, and program product to improve data mounting efficiency and flexibility, and reduce data mounting time and manpower consumption.
[0006] In a first aspect, embodiments of the present invention provide a data mounting method, the method comprising:
[0007] In response to the detection of a data mount command, the data to be mounted is obtained based on the data mount command, and the data type of the data to be mounted is determined;
[0008] Read the mount configuration data corresponding to the data type from the configuration file. The mount configuration data includes: directory structure data and mount rule data.
[0009] The mounting location of the data to be mounted in the directory is determined based on the directory structure data and mounting rule data.
[0010] The data to be mounted is mounted to the directory based on the mount location.
[0011] Secondly, embodiments of the present invention also provide a data mounting device, the device comprising:
[0012] A data type determination module is used to respond to the detection of a data mounting instruction, obtain the data to be mounted based on the data mounting instruction, and determine the data type of the data to be mounted.
[0013] The mount configuration data reading module is used to read mount configuration data corresponding to the data type from the configuration file. The mount configuration data includes: directory structure data and mount rule data.
[0014] The mount location determination module is used to determine the mount location of the data to be mounted in the directory based on the directory structure data and mount rule data.
[0015] The data mounting module is used to mount the data to be mounted to the directory based on the mounting location.
[0016] Thirdly, embodiments of the present invention also provide an electronic device, the electronic device comprising:
[0017] At least one processor; and
[0018] A memory communicatively connected to the at least one processor; wherein,
[0019] 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 mounting method according to any embodiment of the present invention.
[0020] Fourthly, embodiments of the present invention also provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the data mounting method as described in any of the embodiments of the present invention.
[0021] Fifthly, embodiments of the present invention also provide a computer program product, including a computer program that, when executed by a processor, implements the data mounting method as described in any of the embodiments of the present invention.
[0022] In this embodiment of the invention, in response to the detection of a data mount command, the data to be mounted is obtained based on the data mount command, and the data type of the data to be mounted is determined. Mount configuration data, including directory structure data and mount rule data corresponding to the data type, is read from the configuration file. The mount location of the data to be mounted in the directory is determined based on the directory structure data and mount rule data. The data to be mounted is then mounted to the directory based on the mount location. Thus, this solution pre-stores mount configuration data corresponding to various data types in the configuration file. When it is necessary to mount the data to be mounted to the directory, the data is mounted according to the mount configuration data corresponding to the data type stored in the configuration file. Therefore, if a new data type is added, the mount configuration data corresponding to the new data type is written into the configuration file, which enables the mounting of the new data type without needing to redevelop the mount program for the new data type. Furthermore, if the directory structure and / or mount rules corresponding to an existing data type change, the corresponding mount configuration data in the configuration file is updated based on the changed directory structure and / or mount rules, which enables the corresponding change of the mount scheme without modifying the mount program code. In summary, this solution can effectively improve data mounting efficiency and flexibility, while reducing data mounting time and manpower consumption. Attached Figure Description
[0023] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.
[0024] Figure 1 A flowchart illustrating the data mounting method provided in an embodiment of the present invention;
[0025] Figure 2 A schematic diagram of the root node of data assets provided in an embodiment of the present invention;
[0026] Figure 3 A schematic diagram of a directory structure provided for an embodiment of the present invention;
[0027] Figure 4 This is another flowchart illustrating the data mounting method provided in an embodiment of the present invention;
[0028] Figure 5 A schematic diagram of a data mounting method provided in an embodiment of the present invention;
[0029] Figure 6 This is yet another flowchart illustrating the data mounting method provided in this embodiment of the invention;
[0030] Figure 7 A schematic diagram of the data mounting device provided in an embodiment of the present invention;
[0031] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation
[0032] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present invention, and not all of the structures.
[0033] It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. Furthermore, in the description of this invention, terms such as "first," "second," etc., are used only for distinguishing descriptions and should not be construed as indicating or implying relative importance. The acquisition, storage, use, and processing of data in the technical solution of this invention all comply with relevant national laws and regulations.
[0034] Figure 1 This is a flowchart illustrating a data mounting method provided in an embodiment of the present invention. This embodiment is applicable to the management of data assets, such as mounting data assets onto a directory according to certain rules. This method can be executed by the data mounting device in this embodiment, which can be implemented using software and / or hardware. In a specific embodiment, the device can be integrated into an electronic device, such as a computer or server. The following embodiments will illustrate this using the integration of the device into an electronic device as an example. Figure 1 The method may specifically include the following steps:
[0035] S101, in response to the detection of a data mount command, obtain the data to be mounted based on the data mount command, and determine the data type of the data to be mounted.
[0036] Mounting can be understood as the process by which the operating system makes computer files and directories on a storage device (such as a hard drive or shared resource) accessible to users through the computer's file system. Data mounting can be understood as the process by which the operating system makes data accessible to users through the computer's file system.
[0037] Specifically, in response to the detection of a data mount command, the data to be mounted can be obtained based on the data identifier to be mounted in the data mount command, and the data type of the data to be mounted can be determined.
[0038] For example, the data to be mounted can be a data asset, and the types of data assets can include, but are not limited to, databases, database tables, and data interfaces. Data assets can be understood as data resources owned or controlled by the group, capable of bringing future economic benefits to the group, and recorded in a physical or electronic manner, including but not limited to databases (structured, semi-structured, unstructured), tables, fields, data specifications, data tags, indicators, reports, data models, and data products. Assuming the data to be mounted is A, and the identifier of the data to be mounted is B, in response to the detection of a data mounting instruction, the data to be mounted (A) can be obtained based on the identifier (B) of the data to be mounted in the data mounting instruction, and the data type of the data to be mounted can be determined to be a data interface.
[0039] S102, read the mount configuration data corresponding to the data type from the configuration file. The mount configuration data includes: directory structure data and mount rule data.
[0040] Mount configuration data can be understood as the configuration data required to mount data of a corresponding data type. This data can include the directory structure data and mount rule data corresponding to that data type. The directory structure can be a tree structure, and the directory structure data can be the structural data of that tree structure, including the root node data and the number of sub-nodes. The mount rule data can include the mountable data types corresponding to each level, as well as the mount matching conditions for each level except the lowest level. The configuration file can be understood as a file that stores the mount configuration data corresponding to each data type. The configuration file can include the mount configuration data for each data type. For example... Figure 2 As shown in the example, there are three types of data assets, and the root nodes in the directory structure corresponding to each data asset are A1, A2, and A3, respectively.
[0041] Taking node A3 as an example, such as Figure 3 As shown, node A3 has two sub-nodes, A31 and A32; node A31 has five sub-nodes, A311, A312, A313, A314, and A315. Node A32 has one sub-node, A321; node A321 has three sub-nodes, A3211 and A3212.
[0042] from Figure 2 and Figure 3As can be seen, the directory structure of the data assets is a tree structure, which includes one root node, such as root node A3. Root node A3 includes three levels: the first level S1 includes two nodes, A31 and A32; the second level S2 includes six nodes, A311, A312, A313, A314, A315, and A321; and the third level S3 includes two nodes, A3211 and A3212.
[0043] Specifically, mount configuration data corresponding to the data type of the data to be mounted can be read from the configuration file.
[0044] For example, if the data type of the data to be mounted is a data interface, the directory structure data and mounting rule data corresponding to the data type (data interface) of the data to be mounted can be read from the configuration file.
[0045] S103, determine the mount location of the data to be mounted in the directory based on the directory structure data and mount rule data.
[0046] Specifically, the mount location of the data to be mounted in the directory is determined based on the directory structure data and mount rule data, including:
[0047] Step a1: Determine the target level to which the data to be mounted will be mounted, based on the mountable data types corresponding to each level.
[0048] The target level can be understood as the level that successfully matches the data type identifier of the data to be mounted. Mountable data types can include, but are not limited to, databases, database tables, and data interfaces.
[0049] Specifically, the data types that can be mounted and the data types of the data to be mounted can be matched for each level. If the match is successful, the level corresponding to the successfully matched data type can be determined as the target level to which the data to be mounted is mounted.
[0050] For example, if the data type of the data to be mounted is "organization," and there are two levels under the root node of the directory structure, the first level under the root node is S1, and the second level under the root node is S2. The mountable data type corresponding to the first level is "organization," and the mountable data type corresponding to the second level is "system." The mountable data types (organization and system) corresponding to the two levels can be matched with the data type (organization) of the data to be mounted. If S1 matches successfully, then the level (S1) corresponding to the successfully matched mountable data type (organization) can be determined as the target level to which the data to be mounted is attached.
[0051] Step a2: Determine whether the target level is the next level of the root node. If so, determine the root node as the parent node for mounting the data to be mounted. Otherwise, based on the mounting matching conditions of each level above the target level, determine the parent node for mounting the data to be mounted in the directory.
[0052] Specifically, the mounting matching condition can be a condition used to determine the node in the corresponding level that matches the data to be mounted. If the level of the node that matches the data to be mounted is the level above the target level, then the node that matches the data to be mounted is determined as the parent node.
[0053] For example, if the data type of the data to be mounted is "organization", assuming there are three levels under the root node of the corresponding directory structure, the first level is S1, and the data type that can be mounted at level S1 is "organization", the second level is S2, and the data type that can be mounted at level S2 is "system", and the third level is S3, and the data type that can be mounted at level S3 is "data interface". By determining the target level to which the data to be mounted is mounted according to the data types that can be mounted at each level, it can be determined that the target level (S1) is the next level of the root node. In this case, the root node is determined to be the parent node to which the data to be mounted is mounted.
[0054] If the data type of the data to be mounted is a data interface, by determining the target level to which the data to be mounted is S3 based on the mountable data types corresponding to each level, we can ascertain that the target level S3 is not the next level below the root node. Therefore, based on the mounting matching conditions corresponding to the S1 and S2 levels above the target level (S3), we can determine the parent node to which the data to be mounted is mounted in the directory. Specifically, the mounting matching condition for the S1 level is: the organization identifier corresponding to the data interface to be mounted is consistent with the organization identifier of the node; the mounting matching condition for the S2 level is: the system identifier corresponding to the data interface to be mounted is consistent with the system identifier of the node. Here, the organization identifier can be understood as the organization name.
[0055] For example, the S1 level includes the following nodes: Figure 3 As shown in the diagram, A31 and A32 have organizational identifiers of M1 and M2, respectively. The organizational identifier corresponding to the data interface to be mounted is M2. Therefore, it can be determined that the node in the S1 level whose organizational identifier matches the organizational identifier corresponding to the data interface to be mounted is A32. However, since the S1 level is not the parent level of the target level, the node A32 matching the data to be mounted is not a parent node. Continuing, the node in the S2 level whose system identifier matches the system identifier corresponding to the data interface to be mounted is A321. Since the S2 level is the parent level of the target level, the node (A321) matching the data to be mounted is a parent node.
[0056] In this embodiment, based on the mountable data types corresponding to each level, the target level to which the data to be mounted is determined. It is then determined whether the target level is the next level below the root node. If so, the root node is determined as the parent node for mounting the data to be mounted. Otherwise, based on the mounting matching conditions corresponding to each level above the target level, the parent node for mounting the data to be mounted in the directory is determined. This allows for a more accurate determination of the parent node for mounting the data to be mounted based on the hierarchical relationship of each node, thereby improving the mounting efficiency and accuracy of data mounting.
[0057] S104, mounts the data to be mounted to the directory based on the mount location.
[0058] Specifically, the mount path of the data to be mounted in the directory is generated based on the parent node, and the mount path is saved to the directory node information table.
[0059] For example, continuing the example above, the data type of the data to be mounted is a data interface. The first level under the root node is S1, the second level is S2, and the third level is S3. The data to be mounted is... Figure 3 The data corresponding to node A3211 in the table. If the target level to which the data to be mounted is S3, and node A321 is the parent node to which the data to be mounted is mounted, the mounting path of the data to be mounted in the directory can be generated based on the parent node (A321) as A3-A32-A321-A3211. The mounting path is saved to the directory node information table, and the data to be mounted is mounted to the directory according to the mounting path.
[0060] In this embodiment, mounting configuration data corresponding to various data types are pre-stored in the configuration file. When data to be mounted needs to be mounted to a directory, the mounting is performed according to the mounting configuration data corresponding to the data type stored in the configuration file. Therefore, if a new data type is added, the mounting configuration data corresponding to the new data type is written into the configuration file, and the data of the new data type can be mounted without having to redevelop the mounting program for the new data type. Furthermore, if the directory structure and / or mounting rules corresponding to existing data types change, the corresponding mounting configuration data in the configuration file is updated based on the changed directory structure and / or mounting rules, and the mounting scheme is changed accordingly without modifying the mounting program code. In summary, this solution can effectively improve data mounting efficiency and flexibility, and reduce data mounting time and manpower consumption.
[0061] In some embodiments, the data type of the data to be mounted can be a database table, and the name of the root node can be "database table". The root node can include three levels, and the data types that can be mounted at each level can be: database, data model, and database table. The mounting matching conditions for the other levels, except for the lowest level, are: the value of the database identifier field in the database table to be mounted is consistent with the database identifier of the node, and the value of the data model identifier field in the database table to be mounted is consistent with the data model identifier of the node. This allows for a more accurate determination of the parent node to mount the data in the directory when the data type of the data to be mounted is a database table. In this context, "database identifier" can be understood as the identity identifier of the database, and the database identifier field can be understood as the identity identifier field of the database. The field value of the database identifier field can be understood as the field value of the identity identifier field of the database. For example, in database O-G11, the identifier field of database O-G11 is O, and the field value of the identifier field of database O-G11 is G11. Similarly, "data model identifier" can be understood as the identity identifier of the data model, and the data model identifier field can be understood as the identity identifier field of the data model. For example, in data model MODEL-I11, the data model identifier field of data model MODEL-I11 is MODEL, and the field value of the identifier field of data model MODEL-I11 is I11.
[0062] Specifically, the parent node for mounting the data to be mounted in the directory can be determined by checking whether the value of the database identifier field in the database table to be mounted is consistent with the database identifier of the node, and whether the value of the data model identifier field in the database table to be mounted is consistent with the data model identifier of the node.
[0063] For example, if the data type of the data to be mounted is a database table, and the root node of the directory structure is the database table, with three levels below the database table: the first level is T1, where the data type that can be mounted at level T1 is database; the second level is T2, where the data type that can be mounted at level T2 is data model (Schema); and the third level is T3, where the data type that can be mounted at level T3 is database table. By determining the target level to which the data to be mounted is mounted based on the data types that can be mounted at each level, it can be determined that the target level (T3) is not the next level below the root node (database table). Therefore, based on the mounting matching conditions of the T1 and T2 levels above the target level (T3), the parent node to which the data to be mounted is mounted in the directory can be determined.
[0064] Assume that the T1 level includes nodes B1, B2, and B3, with database identifier G1 for B1, G2 for B2, and G3 for B3, and the value of the database identifier field in the database table to be mounted is G3; the T2 level includes nodes B31 and B32, with data model identifier I1 for B31 and I2 for B32, and the value of the data model identifier field in the database table to be mounted is I2.
[0065] We can determine that the node in level T1 whose database identifier matches the value of the database identifier field in the database table to be mounted is B3. B3 is located in level T1, which is not the parent level of the target level. Therefore, the node matching the data to be mounted is not a parent node. Continuing, we determine that the node in level T2 whose data model identifier matches the value of the data model identifier field in the database table to be mounted is B32. B32 is located in level T2, which is the parent level of the target level (T3). Therefore, the node matching the data to be mounted (B32) is a parent node.
[0066] In some embodiments, the data type of the data to be mounted can be a data interface, and the name of the root node can be "data interface". The root node can include three levels, with the corresponding mountable data types for each level being: organization, system, and data interface. The mounting matching conditions for the levels other than the lowest level are: the organization identifier corresponding to the data interface to be mounted must match the organization identifier of the node, and the system identifier corresponding to the data interface to be mounted must match the system identifier of the node. This allows for a more accurate determination of the parent node to mount the data in the directory when the data type of the data to be mounted is a data interface. Here, the organization identifier can be understood as the identity identifier of the organization, and the system identifier can be understood as the identity identifier of the system.
[0067] Specifically, the parent node for mounting the data to be mounted in the directory can be determined by checking whether the organization identifier corresponding to the data interface to be mounted is consistent with the organization identifier of the node, and whether the system identifier corresponding to the data interface to be mounted is consistent with the system identifier of the node.
[0068] For example, if the data type of the data to be mounted is a data interface, and the root node of the directory structure is the data interface, and there are three levels under the data interface, where the first level is U1, the data type that can be mounted at the U1 level is organization, the second level is U2, the data type that can be mounted at the U2 level is system, and the third level is U3, the data type that can be mounted at the U3 level, by determining the target level to which the data to be mounted is mounted based on the data types that can be mounted at each level, it can be determined that the target level (U3) is not the next level of the root node. Therefore, based on the mounting matching conditions of the U1 and U2 levels above the target level (U3), the parent node to which the data to be mounted is mounted in the directory can be determined.
[0069] The mounting matching condition at the U1 level can be: the organization identifier corresponding to the data interface to be mounted is consistent with the organization identifier of the node in the U1 level.
[0070] The mounting matching condition for the U2 layer can be: the system identifier corresponding to the data interface to be mounted is consistent with the system identifier of the node in the U2 layer.
[0071] Assume that the U1 level includes nodes C1, C2, and C3, with the organization identifier of C1 being J1, C2 being J2, and C3 being J3, and the organization identifier corresponding to the data interface to be attached being J3; the U2 level includes nodes C31 and C32, with the system identifier of C31 being K1, C32 being K2, and the system identifier corresponding to the data interface to be attached being K2.
[0072] We can determine that the node whose organizational identifier in the U1 level matches the organizational identifier of the data interface to be mounted is C3. C3 is located in the U1 level, which is not the upper level of the target level. Therefore, the node matching the data to be mounted is not a parent node. Continuing, we determine that the node whose system identifier in the U2 level matches the system identifier of the data interface to be mounted is C32. C32 is located in the U2 level, which is the upper level of the target level (U3). Therefore, we can determine that the node matching the data to be mounted (C32) is a parent node.
[0073] Figure 4 This is another flowchart illustrating the data mounting method provided in an embodiment of the present invention, see reference. Figure 4 Specifically, it may include the following steps:
[0074] S401, in response to the detection of a data mount command, obtain the data to be mounted based on the data mount command, and determine the data type of the data to be mounted.
[0075] S402, Read the mount configuration data corresponding to the data type from the configuration file. The mount configuration data includes: directory structure data and mount rule data. The directory structure can be a tree structure. Accordingly, the directory structure data can include the root node data and the number of sub-levels of the root node; the mount rule data can include the mountable data types corresponding to each level, and the mount matching conditions corresponding to each level except the lowest level.
[0076] S403, determine the target level to which the data to be mounted is mounted based on the mountable data types corresponding to each level.
[0077] S404, determine whether the target level is the next level of the root node. If the target level is the next level of the root node, proceed to step S405; if the target level is not the next level of the root node, proceed to step S406.
[0078] S405, determine the root node as the parent node of the data to be mounted.
[0079] After executing step S405, proceed to step S407.
[0080] S406, based on the mounting matching conditions corresponding to each level above the target level, determine the parent node in the directory to mount the data to be mounted.
[0081] Specifically, based on the mount matching conditions corresponding to each level above the target level, the parent node for mounting the data to be mounted in the directory is determined, including:
[0082] Step b1: Take the next level of the root node as the current level, and take the set of nodes in the current level as the current node set.
[0083] Step b2: Based on the mounting matching conditions corresponding to the current level, match the data to be mounted with each node in the current node set to obtain the nodes in the current level that match the data to be mounted.
[0084] Step b3: If the current level is the level above the target level, then the node that matches the data to be mounted is determined as the parent node for mounting the data in the directory; otherwise, the level below the current level is taken as the new current level, the set of child nodes of the node that matches the data to be mounted is taken as the new current child node set, and the operation of matching the data to be mounted with each node in the current node set is returned to execute according to the mounting matching conditions corresponding to the current level.
[0085] For example, if the data type to be mounted is a data interface, the first level under the root node in its directory structure is S1, and the S1 level can mount the data type as organization. The second level is S2, and the S2 level can mount the data type as system. The third level is S3, and the S3 level can mount the data type as data interface. The first level includes nodes A31 and A32.
[0086] If the target level is S3, it can be determined that the target level (S3) is not the next level of the root node. Therefore, the next level of the root node (S1) can be taken as the current level, and the set of nodes in the current level can be taken as the current node set {A31, A32}.
[0087] The mounting matching condition for the S1 level can be: the organization identifier corresponding to the data interface to be mounted is consistent with the organization identifier of the node in the S1 level.
[0088] Based on the mounting matching conditions corresponding to the current level S1, the node whose organization identifier is consistent with the organization identifier in the current node set {A31, A32} is determined to be A31. The level of A31 is S1. If the S1 level is not the next level above the target level, then the next level of the S1 level (S2) is taken as the current level, and the set of child nodes under S31 in the current level is taken as the current node set {A311, A312, A313, A314, A315}.
[0089] The mounting matching condition at the S2 level can be: the system identifier corresponding to the data interface to be mounted is consistent with the system identifier of the node in the S2 level.
[0090] Based on the mounting matching conditions corresponding to the current level S2, the node whose organization identifier matches the organization identifier in the current node set {A311, A312, A313, A314, A315} is identified as A311. The level of A311 is S2, which is the upper level of the target level (S3). Therefore, the node A311 that matches the data to be mounted is identified as the parent node for mounting the data to be mounted in the directory, and the data to be mounted is mounted under A311.
[0091] In this embodiment, the level below the root node is taken as the current level, and the set of nodes in the current level is taken as the current node set. Based on the mounting matching conditions corresponding to the current level, the data to be mounted is matched with each node in the current node set to obtain the node in the current level that matches the data to be mounted. If the current level is the level above the target level, the node matching the data to be mounted is determined as the parent node for mounting the data in the directory; otherwise, the level below the current level is taken as the new current level, and the node matching the data to be mounted is determined as the parent node for mounting the data in the directory. The set of child nodes of a point is taken as the new current child node set, and the operation of matching the data to be mounted with each node in the current node set is performed according to the mounting matching conditions corresponding to the current level. This allows for more accurate matching of the data to be mounted with each node in the current node set at each level, thereby obtaining the node that matches the data to be mounted and determining the parent node of the data to be mounted in the directory, thus improving the accuracy of determining the parent node of the data to be mounted in the directory.
[0092] S407 generates the mount path of the data to be mounted in the directory based on the parent node.
[0093] Specifically, the mount path of the data to be mounted in the directory is generated based on the parent node, including:
[0094] Step c1: Form a node pair by pairing the parent node with the node corresponding to the data to be mounted, and form a node pair by pairing the nodes in the adjacent level that match the data to be mounted.
[0095] For example, if the first three levels under the root node are S1, S2, and S3, the first level includes nodes A31 and A32, and the second level includes nodes A311, A312, A313, A314, A315, and A321. If the parent node is A321, and the node corresponding to the data to be mounted is A3211, then the parent node A321 and the node corresponding to the data to be mounted, A3211, can be paired as (A321, A3211). Similarly, the nodes in adjacent levels S1 and S2 that match the data to be mounted can be paired as (A32, A321).
[0096] Step c2: For each node pair, use the node identifier of the parent node in the current node pair as the source identifier and the node identifier of the child node in the current node pair as the target identifier. Then, associate and store the source identifier and target identifier in a preset temporary table. Here, the node identifier can be understood as the node name.
[0097] For example, if the node pairs are (A32, A321) and (A321, A3211), the node identifier of the upper-level node A32 in the current node pair (A32, A321) is used as the source identifier, and the node identifier of the lower-level node (A321) in the current node pair is used as the target identifier. The source identifier A32 and the target identifier A321 are associated and stored in a preset temporary table. The node identifier A321 of the upper-level node in the current node pair (A321, A3211) is used as the source identifier, and the node identifier (A3211) of the lower-level node in the current node pair is used as the target identifier. The source identifier A321 and the target identifier A3211 are associated and stored in a preset temporary table.
[0098] Step c3: Based on the root node data and the data in the preset temporary table, generate the mount path of the data to be mounted in the directory.
[0099] Specifically, the mounting path of the data to be mounted in the directory can be generated according to the hierarchical relationship of the nodes corresponding to the root node identifier in the root node data, the source identifier and the target identifier stored in the preset temporary table.
[0100] For example, based on the root node identifier A3 and two records stored in the preset temporary table: (source node A32, target node A321) and (source node A321, target node A3211), the mounting path of the data to be mounted in the directory is generated according to the hierarchical relationship as: data asset A3-A32-A321-A3211.
[0101] In this embodiment, the parent node and the node corresponding to the data to be mounted are paired together, and the nodes in the adjacent levels that match the data to be mounted are also paired together. For each pair of nodes, the node identifier of the upper-level node in the current pair is used as the source identifier, and the node identifier of the lower-level node in the current pair is used as the target identifier. The source identifier and the target identifier are associated and stored in a preset temporary table. Based on the root node data and the data in the preset temporary table, the mounting path of the data to be mounted in the directory is generated more accurately.
[0102] S408 saves the mount path to the directory node information table.
[0103] S409, in response to detecting a trigger operation on any node in the displayed directory, reads the mount path of the triggered node from the directory node information table.
[0104] For example, in response to the detection of a trigger operation on a node (A3211) in the displayed directory, the mount path of the triggered node (A3211) can be read from the directory node information table as: A3-A32-A321-A3211.
[0105] S410: Obtain the mounted data corresponding to the triggered node based on the mounted path of the triggered node, and display the mounted data.
[0106] For example, based on the mount path (A3-A32-A321-A3211) of the triggered node (A3211), the mounted data corresponding to the triggered node is obtained and displayed.
[0107] In this embodiment, the mount path of the triggered node can be quickly read from the directory node information table including the mount path, and the mounted data corresponding to the triggered node can be obtained based on the mount path of the triggered node. The mounted data can then be displayed, which improves the display speed of the mounted data and increases the convenience and flexibility of displaying the mounted data.
[0108] In this embodiment, mounting configuration data corresponding to various data types are pre-stored in the configuration file. When data to be mounted needs to be mounted to a directory, the mounting is performed according to the mounting configuration data corresponding to the data type stored in the configuration file. Therefore, if a new data type is added, the mounting configuration data corresponding to the new data type is written into the configuration file, and the data of the new data type can be mounted without having to redevelop the mounting program for the new data type. Furthermore, if the directory structure and / or mounting rules corresponding to existing data types change, the corresponding mounting configuration data in the configuration file is updated based on the changed directory structure and / or mounting rules, and the mounting scheme is changed accordingly without modifying the mounting program code. In summary, this solution can effectively improve data mounting efficiency and flexibility, and reduce data mounting time and manpower consumption.
[0109] Figure 5 A schematic diagram of the data mounting method provided in an embodiment of the present invention is shown below. Figure 5As shown, before mounting data, mounting information checks are required, including: confirming the existence of all nodes for automatic database mounting; confirming that the database is the first class in the configuration group; and confirming the completeness of the configuration group's configuration information, such as matching rules and level names. Since mounting between levels requires an aggregation relationship configuration, this aggregation relationship can be understood as the mounting priority between levels. For example, the root node may have three levels: the first level corresponds to a database as the mountable data type, the second level to a data model, and the third level to a database table. Data to be mounted at the third level can only be mounted at the second level, and data to be mounted at the second level can only be mounted at the first level. Therefore, it is necessary to confirm whether the hierarchical order between each level is correct; confirm whether the root node for database mounting exists; confirm whether the parent node of the data to be mounted is the root node; and confirm whether the directory structure data and mounting rule data are complete. This can ensure that data mounting fails due to a missing root node or an incorrect hierarchical order between levels, and can also prevent data mounting failure due to incomplete directory structure data and mounting rule data.
[0110] After completing the mount information check, the data type of the data to be mounted is determined, and the mount configuration data is read according to the data type. Then, node pairs are determined based on the mount configuration data, mainly including: determining the parent node of the target level of the data to be mounted based on the mount rule data in the mount configuration data; forming node pairs by pairing the parent node with the node corresponding to the data to be mounted; and forming node pairs by pairing nodes in adjacent levels that match the data to be mounted. The node identifier of the upper-level node in the node pair is used as the source identifier, and the node identifier of the lower-level node in the node pair is used as the target identifier. The source identifier and target identifier are associated and stored in a preset temporary table. Based on the root node data and the data in the preset temporary table, the mount path of the data to be mounted in the directory is generated. The mount path is saved to the directory node information table, and finally, the data is mounted according to the mount path.
[0111] Figure 6 This is another flowchart illustrating the data mounting method provided in this embodiment of the invention. (Refer to...) Figure 6 Specifically, it may include the following steps:
[0112] S601, in response to detecting a directory configuration command, obtains the data type identifier to be configured and the mount configuration data input through the visual interface based on the directory configuration command.
[0113] The data type identifier can be understood as the name of the data type.
[0114] Specifically, in response to the detection of a directory configuration command, the system can obtain the data type identifier to be configured and the mount configuration data (directory structure data and mount rule data) input through the visual interface based on the directory configuration command.
[0115] For example, when a user inputs mount configuration data through a visual interface, a data record to be filled in can be displayed in the visual interface for each level in hierarchical order. Each data record includes at least four fields to be filled in: the data identifier for accepting mount, the feature identifier for accepting mount, the mount data identifier, and the mount feature identifier. The data identifier for accepting mount represents the mountable data type identifier of the current level, the mount data identifier represents the mountable data type identifier of the next level of the current level, and the feature identifier for accepting mount and the mount feature identifier represent the mount matching conditions of the corresponding level.
[0116] S602, writes the data type identifier and mounting configuration data into the configuration file.
[0117] For example, if the data type to be configured is a database table, and the data type identifier of the database table is G1, the data type identifier (G1) and the mount configuration data (directory structure data and mount rule data) are written into the configuration file accordingly.
[0118] In this embodiment, if a new data type is added, the mounting configuration data corresponding to the new data type is written into the configuration file, thus enabling the mounting of the new data type without needing to redevelop the mounting program for the new data type. Furthermore, if the directory structure and / or mounting rules corresponding to an existing data type change, the corresponding mounting configuration data in the configuration file is updated based on the changed directory structure and / or mounting rules, thus changing the mounting scheme accordingly without modifying the mounting program code. In summary, this solution effectively improves data mounting efficiency and flexibility, while reducing data mounting time and manpower consumption.
[0119] Figure 7 This is a schematic diagram of a data mounting device provided in an embodiment of the present invention. This embodiment is applicable to the management of data assets, such as mounting data assets to a directory according to certain rules. The device can be implemented using software and / or hardware, and can be integrated into an electronic device, such as… Figure 7 As shown, the data mounting device specifically includes:
[0120] The data type determination module 701 is used to respond to the detection of a data mounting instruction, obtain the data to be mounted based on the data mounting instruction, and determine the data type of the data to be mounted.
[0121] Mount configuration data reading module 702 is used to read mount configuration data corresponding to the data type from the configuration file. The mount configuration data includes: directory structure data and mount rule data.
[0122] Mount location determination module 703 is used to determine the mount location of the data to be mounted in the directory based on the directory structure data and mount rule data;
[0123] The data mounting module 704 is used to mount the data to be mounted to the directory based on the mounting location.
[0124] Optionally, the directory structure is a tree structure, and the directory structure data includes the root node data and the number of levels below the root node; the mounting rule data includes the mountable data types corresponding to each level, and the mounting matching conditions corresponding to each level except the lowest level.
[0125] Mounting location determination module 703 is specifically used for:
[0126] Based on the mountable data types corresponding to each level, determine the target level to which the data to be mounted will be mounted;
[0127] Determine whether the target level is the next level of the root node. If so, determine that the root node is the parent node for mounting the data to be mounted. Otherwise, determine the parent node for mounting the data to be mounted in the directory based on the mounting matching conditions of each level above the target level.
[0128] Optionally, the mount location determination module 703 determines the parent node in the directory to mount the data to be mounted, based on the mount matching conditions corresponding to each level above the target level, including:
[0129] The next level of the root node is taken as the current level, and the set of nodes in the current level is taken as the current node set.
[0130] Based on the mounting matching conditions corresponding to the current level, the data to be mounted is matched with each node in the current node set to obtain the node in the current level that matches the data to be mounted.
[0131] If the current level is the level above the target level, then the node that matches the data to be mounted is determined as the parent node for mounting the data in the directory; otherwise, the level below the current level is taken as the new current level, the set of child nodes of the node that matches the data to be mounted is taken as the new current child node set, and the operation of matching the data to be mounted with each node in the current node set according to the mounting matching conditions corresponding to the current level is returned.
[0132] Optionally, the data mounting module 704 is specifically used for:
[0133] The mount path of the data to be mounted in the directory is generated based on the parent node;
[0134] Save the mount path to the directory node information table.
[0135] Optionally, the data mounting module 704 generates the mount path of the data to be mounted in the directory based on the parent node, including:
[0136] The parent node and the node corresponding to the data to be mounted are paired together, and the nodes in the adjacent levels that match the data to be mounted are paired together.
[0137] For each node pair, the node identifier of the upper-level node in the current node pair is used as the source identifier, and the node identifier of the lower-level node in the current node pair is used as the target identifier. The source identifier and the target identifier are associated and stored in a preset temporary table.
[0138] Based on the root node data and the data in the preset temporary table, the mount path of the data to be mounted in the directory is generated.
[0139] Optionally, the data mounting module 704 is also specifically used for:
[0140] In response to detecting a trigger operation on any node in the displayed directory, the mount path of the triggered node is read from the directory node information table;
[0141] Based on the mounting path of the triggered node, obtain the mounted data corresponding to the triggered node, and display the mounted data.
[0142] Optionally, the data type of the data to be mounted is a database table, the root node is a database table, and the root node includes three levels, with the data types that can be mounted corresponding to each level being: database, data model, and database table.
[0143] The mounting matching conditions for all levels except the lowest level are as follows: the value of the database identifier field in the database table to be mounted is consistent with the database identifier of the node, and the value of the data model identifier field in the database table to be mounted is consistent with the data model identifier of the node.
[0144] Optionally, the data type of the data to be mounted is a data interface, the root node is a data interface, and the root node includes three levels, with the data types that can be mounted corresponding to each level being: organization, system, and data interface.
[0145] The mounting matching conditions for all levels except the lowest level are as follows: the organization identifier corresponding to the data interface to be mounted is consistent with the organization identifier of the node, and the system identifier corresponding to the data interface to be mounted is consistent with the system identifier of the node.
[0146] Furthermore, the device also includes:
[0147] The mount configuration data acquisition module is used to respond to the detection of a directory configuration command, and to acquire the data type identifier to be configured and the mount configuration data input through the visual interface based on the directory configuration command.
[0148] The data writing module is used to write the data type identifier and the mounting configuration data into the configuration file.
[0149] The data mounting device provided in this embodiment of the invention can execute the data mounting method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method execution.
[0150] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Figure 8 A block diagram is shown of an exemplary electronic device 12 suitable for implementing embodiments of the present invention. Figure 8 The electronic device 12 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of the present invention.
[0151] like Figure 8 As shown, the electronic device 12 is represented in the form of a general-purpose computing device. The components of the electronic device 12 may include, but are not limited to: one or more processors or processing units 16, system memory 28, and bus 18 connecting different system components (including system memory 28 and processing unit 16).
[0152] Bus 18 represents one or more of several bus architectures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the various bus architectures. For example, these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus.
[0153] Electronic device 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by electronic device 12, including volatile and non-volatile media, removable and non-removable media.
[0154] System memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. Electronic device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 34 may be used to read and write non-removable, non-volatile magnetic media (… Figure 8 Not shown; usually referred to as a "hard drive"). Although Figure 8 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk") and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 18 via one or more data media interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of the embodiments of the present invention.
[0155] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in memory 28. Such program modules 42 include—but are not limited to—an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. Program modules 42 typically perform the functions and / or methods described in the embodiments of the present invention.
[0156] Electronic device 12 can also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), and with one or more devices that enable a user to interact with electronic device 12, and / or with any device that enables electronic device 12 to communicate with one or more other computing devices (e.g., network card, modem, etc.). This communication can be performed via input / output (I / O) interface 22. Furthermore, in this embodiment, electronic device 12 and display 24 are not separate entities, but are embedded in a mirror, so that when the display surface of display 24 is not displayed, the display surface of display 24 and the mirror surface visually blend together. Additionally, electronic device 12 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 20. As shown, network adapter 20 communicates with other modules of electronic device 12 via bus 18. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with electronic device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.
[0157] The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, such as implementing a data mounting method provided in this embodiment of the invention: in response to detecting a data mounting instruction, it obtains the data to be mounted based on the data mounting instruction and determines the data type of the data to be mounted; it reads mounting configuration data corresponding to the data type from a configuration file, the mounting configuration data including: directory structure data and mounting rule data; it determines the mounting position of the data to be mounted in the directory based on the directory structure data and mounting rule data; and it mounts the data to be mounted to the directory based on the mounting position. This solution pre-stores mounting configuration data corresponding to various data types in a configuration file. When data needs to be mounted to a directory, the mounting is performed according to the stored mounting configuration data corresponding to the data type. Therefore, if a new data type is added, the mounting configuration data corresponding to the new data type is written into the configuration file, enabling the mounting of data of the new data type without the need to redevelop the mounting program for the new data type. Furthermore, if the directory structure and / or mounting rules corresponding to existing data types change, the corresponding mounting configuration data in the configuration file is updated based on the changed directory structure and / or mounting rules, thus changing the mounting scheme accordingly without modifying the mounting program code. In summary, this solution effectively improves data mounting efficiency and flexibility, while reducing mounting time and manpower consumption.
[0158] This invention provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the data mounting method provided in all embodiments of this invention: in response to detecting a data mounting instruction, obtaining data to be mounted based on the data mounting instruction and determining the data type of the data to be mounted; reading mounting configuration data corresponding to the data type from a configuration file, the mounting configuration data including directory structure data and mounting rule data; determining the mounting location of the data to be mounted in the directory based on the directory structure data and mounting rule data; and mounting the data to be mounted to the directory based on the mounting location. This solution pre-stores mounting configuration data corresponding to various data types in a configuration file. When data needs to be mounted to a directory, the mounting is performed according to the stored mounting configuration data corresponding to the data type. Therefore, if a new data type is added, the mounting configuration data corresponding to the new data type is written into the configuration file, enabling the mounting of data of the new data type without the need to redevelop the mounting program for the new data type. Furthermore, if the directory structure and / or mounting rules corresponding to existing data types change, the corresponding mounting configuration data in the configuration file is updated based on the changed directory structure and / or mounting rules, thus changing the mounting scheme accordingly without modifying the mounting program code. In summary, this solution effectively improves data mounting efficiency and flexibility, while reducing mounting time and manpower consumption.
[0159] Any combination of one or more computer-readable media may be used. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in connection with an instruction execution system, apparatus, or device.
[0160] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of sending, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device.
[0161] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.
[0162] Computer program code for performing the operations of this invention can be written in one or more programming languages or a combination thereof. Programming languages include object-oriented programming languages such as Java, Smalltalk, and C++, as well as conventional procedural programming languages such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0163] This invention also provides a computer program product, including a computer program that, when executed by a processor, implements the data mounting method provided in any embodiment of this invention.
[0164] In implementing the computer program product, computer program code for performing the operations of this invention can be written in one or more programming languages or a combination thereof. Programming languages include object-oriented programming languages such as Java, Smalltalk, and C++, as well as conventional procedural programming languages such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0165] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.
Claims
1. A data mounting method, characterized in that, The method includes: In response to the detection of a data mount command, the data to be mounted is obtained based on the data mount command, and the data type of the data to be mounted is determined; Read the mount configuration data corresponding to the data type from the configuration file. The mount configuration data includes: directory structure data and mount rule data. The mounting location of the data to be mounted in the directory is determined based on the directory structure data and mounting rule data. Mount the data to be mounted to the directory based on the mount location; The directory structure is a tree structure. The directory structure data includes the root node data and the number of the levels below the root node. The mounting rule data includes the mountable data types corresponding to each level and the mounting matching conditions corresponding to each level except the lowest level. Determining the mount location of the data to be mounted in the directory based on the directory structure data and mount rule data includes: Match the mountable data types corresponding to each level with the data type. If the match is successful, the level corresponding to the successfully matched mountable data type is determined as the target level to which the data to be mounted is mounted. Determine whether the target level is the next level of the root node. If so, determine that the root node is the parent node for mounting the data to be mounted. Otherwise, determine the parent node for mounting the data to be mounted in the directory based on the mounting matching conditions of each level above the target level.
2. The method according to claim 1, characterized in that, The step of determining the parent node for mounting the data to be mounted in the directory based on the mounting matching conditions corresponding to each level above the target level includes: The next level of the root node is taken as the current level, and the set of nodes in the current level is taken as the current node set. Based on the mounting matching conditions corresponding to the current level, the data to be mounted is matched with each node in the current node set to obtain the node in the current level that matches the data to be mounted. If the current level is the level above the target level, then the node that matches the data to be mounted is determined as the parent node for mounting the data in the directory; otherwise, the level below the current level is taken as the new current level, the set of child nodes of the node that matches the data to be mounted is taken as the new current child node set, and the operation of matching the data to be mounted with each node in the current node set according to the mounting matching conditions corresponding to the current level is returned.
3. The method according to claim 2, characterized in that, Mounting the data to be mounted to the directory based on the mount location includes: The mount path of the data to be mounted in the directory is generated based on the parent node; Save the mount path to the directory node information table.
4. The method according to claim 3, characterized in that, The step of generating the mount path of the data to be mounted in the directory based on the parent node includes: The parent node and the node corresponding to the data to be mounted are paired together, and the nodes in the adjacent levels that match the data to be mounted are paired together. For each node pair, the node identifier of the upper-level node in the current node pair is used as the source identifier, and the node identifier of the lower-level node in the current node pair is used as the target identifier. The source identifier and the target identifier are associated and stored in a preset temporary table. Based on the root node data and the data in the preset temporary table, the mount path of the data to be mounted in the directory is generated.
5. The method according to claim 3, characterized in that, The method further includes: In response to detecting a trigger operation on any node in the displayed directory, the mount path of the triggered node is read from the directory node information table; Based on the mounting path of the triggered node, obtain the mounted data corresponding to the triggered node, and display the mounted data.
6. The method according to claim 1, characterized in that, The data type of the data to be mounted is a database table. The root node is a database table. The root node includes three levels, and the data types that can be mounted at each level are: database, data model and database table. The mounting matching conditions for all levels except the lowest level are as follows: the value of the database identifier field in the database table to be mounted is consistent with the database identifier of the node, and the value of the data model identifier field in the database table to be mounted is consistent with the data model identifier of the node.
7. The method according to claim 1, characterized in that, The data type of the data to be mounted is a data interface. The root node is the data interface. The root node includes three levels. The data types that can be mounted at each level are: organization, system and data interface. The mounting matching conditions for all levels except the lowest level are as follows: the organization identifier corresponding to the data interface to be mounted is consistent with the organization identifier of the node, and the system identifier corresponding to the data interface to be mounted is consistent with the system identifier of the node.
8. The method according to any one of claims 1-7, characterized in that, The method further includes: In response to the detection of a directory configuration instruction, the data type identifier to be configured and the mount configuration data input through the visual interface are obtained based on the directory configuration instruction. Write the data type identifier and the mounting configuration data into the configuration file.
9. A data mounting device, characterized in that, The device includes: A data type determination module is used to respond to the detection of a data mounting instruction, obtain the data to be mounted based on the data mounting instruction, and determine the data type of the data to be mounted. The mount configuration data reading module is used to read mount configuration data corresponding to the data type from the configuration file. The mount configuration data includes: directory structure data and mount rule data. The mount location determination module is used to determine the mount location of the data to be mounted in the directory based on the directory structure data and mount rule data. A data mounting module is used to mount the data to be mounted to a directory based on the mounting location; The directory structure is a tree structure. The directory structure data includes the root node data and the number of the levels below the root node. The mounting rule data includes the mountable data types corresponding to each level and the mounting matching conditions corresponding to each level except the lowest level. The mounting location determination module is specifically used for: Match the mountable data types corresponding to each level with the data type. If the match is successful, the level corresponding to the successfully matched mountable data type is determined as the target level to which the data to be mounted is mounted. Determine whether the target level is the next level of the root node. If so, determine that the root node is the parent node for mounting the data to be mounted. Otherwise, determine the parent node for mounting the data to be mounted in the directory based on the mounting matching conditions of each level above the target level.
10. The apparatus according to claim 9, characterized in that, The device further includes: The mount configuration data acquisition module is used to respond to the detection of a directory configuration command, and to acquire the data type identifier to be configured and the mount configuration data input through the visual interface based on the directory configuration command. The data writing module is used to write the data type identifier and the mounting configuration data into the configuration file.
11. An electronic device, characterized in that, include: At least one processor; as well as 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 mounting method according to any one of claims 1-8.
12. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the data mounting method as described in any one of claims 1-8.
13. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the data mounting method as described in any one of claims 1-8.
Citation Information
Patent Citations
File structure conversion method and device, equipment and storage medium
CN111447268A
Data processing method, data processing device, electronic equipment and storage medium
CN114201508A
