CN106484820B

CN106484820B - Renaming method, access method and device

Info

Publication number: CN106484820B
Application number: CN201610852820.2A
Authority: CN
Inventors: 章鹏
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2016-09-26
Filing date: 2016-09-26
Publication date: 2020-01-17
Anticipated expiration: 2036-09-26
Also published as: CN106484820A

Abstract

A renaming method, an access method and a device relate to the technical field of computers, reduce IO times and improve renaming efficiency. The method is applied to a server in an object storage system and comprises the following steps: receiving a renaming request sent by client equipment, wherein the renaming request carries first information, second information and a renaming identifier, and the renaming identifier is used for indicating that the first information is replaced by the second information; after detecting the renaming identifier, the server acquires a target object name comprising first information from a mapping relation table, wherein the mapping relation table comprises a corresponding relation between the target object name and the characteristics of the target object, the characteristics of the target object comprise a Universal Unique Identifier (UUID) of the target object, and the UUID of the target object is used for indicating metadata of the target object and a storage address of the data; the server replaces the first information in the target object name with the second information.

Description

Renaming method, access method and device

Technical Field

The invention relates to the technical field of computers, in particular to a renaming method, an access method and a device.

Background

The Simple Storage Service (S3) protocol stores data using a two-layer data model of buckets (buckets) -objects (objects), wherein the buckets can be regarded as directories and the objects can be regarded as files. The protocol discards a directory tree structure, simplifies read-write semantics, and is suitable for storing massive, unstructured and more-than-write data. Based on the S3 protocol, the user can use Uniform Resource Identifier (URI) to search the related data, i.e. the user searches the related files according to the directory.

At present, the renaming method of the directory in the S3 protocol is as follows: (1) creating a new directory, wherein the directory name of the new directory is different from the original directory name; (2) copying the metadata and data of all the objects in the original directory into a new directory (also called deep copy metadata and data of all the objects in the original directory); (3) and deleting the original directory and all objects included in the original directory. In a simple manner, the renaming method for a directory mainly includes a backup process and a deletion process. The renaming method of the files in the S3 protocol is similar to the renaming method of the directories, and also comprises a backup process and a deletion process.

The aim of renaming the directory or the file can be achieved by executing the backup process and the deletion process, but the backup process and the deletion process cause the problems of excessive operation times and low renaming efficiency of system Input/Output (Input/Output, IO for short).

Disclosure of Invention

The embodiment of the invention provides a renaming method, an access method and a device, which effectively solve the problems of excessive IO times and low renaming efficiency caused by the conventional renaming method.

In a first aspect, a renaming method is provided, which is applied to a server in an object storage system, and includes that after receiving a renaming request carrying first information, second information, and a renaming identifier sent by a client device, the server obtains a target object name including the first information from a mapping relation table, the renaming identifier is used for indicating to replace the first information with the second information, the mapping relation table includes a correspondence between the target object name and characteristics of a target object, the characteristics of the target object include a universally unique identifier UUID of the target object, the UUID of the target object is used for indicating a storage address of metadata and data of the target object, and then the server replaces the first information in the target object name with the second information.

The server in the embodiment of the present invention stores the mapping relationship table, and the mapping relationship table includes a corresponding relationship between a name of the target object and a feature of the target object, and the feature of the target object includes a UUID for indicating a storage address of metadata and data of the target object, so the server may obtain the storage address of the metadata and the data of the target object from the mapping relationship table, and obtain the data of the target object according to the storage address. Because the storage addresses of the metadata and the data of the target object in the server are unchanged, after the server receives the renaming request, the server can directly replace the first information of the target object name in the mapping relation table with the second information without executing a backup process and a deleting process, so that the IO operation frequency of the system is effectively reduced, and the renaming efficiency is improved.

Optionally, in a possible implementation manner of the embodiment of the present invention, a method for replacing, by a server, first information in a target object name with second information includes: the server replaces the first directory name in the target object name with a second directory name; alternatively, the server replaces the target object name with the first object name.

For a server, the object may be a file or a directory. If the object is a file, the object name comprises a path (directory name) to which the file belongs and a file name; if the object is a father directory, the object name is a father directory name; if the object is a child directory of the parent directory, the object name comprises the name of the parent directory and the name of the child directory. When a client device opposite to the server displays a certain level of directory, only the directory name of the level of directory is displayed, and similarly, when the client device displays a certain file, only the file name of the file is displayed. Thus, what the user sees is the directory name of the current directory or the file name of the current file. After receiving the instruction input by the user, the client device may send a renaming request to the server according to the instruction input by the user, where the renaming request includes a directory name or includes a directory name and a file name. Accordingly, the server renames the directory name satisfying the condition or the object name satisfying the condition according to the renaming request.

Thus, the first information in the embodiment of the present invention is an original object name of a certain object, and the second information is a new object name of the certain object; or the first information is an original directory name in a certain object name, and the second information is a new directory name in the object name.

According to the renaming method provided by the embodiment of the invention, the server can directly modify the directory name in the object name meeting the condition after detecting the renaming identifier, and also can directly modify the object name meeting the condition without executing a copying process and a deleting process, so that the IO operation frequency of the system is reduced.

Optionally, in another possible implementation manner of the embodiment of the present invention, after replacing the first information in the target object name with the second information, the server further sends a response message to the client device, where the response message is used to indicate that the replacement of the first information with the second information is successful.

The server sends a response message to the client device for indicating that the first information is successfully renamed to the second information, so that the client device can conveniently display the second information, and a user can access the object according to the second information.

In a second aspect, an access method is provided, which is applied to a server in an object storage system, after receiving an access request carrying an object name and an access identifier of an object to be accessed, sent by a client device, obtaining a UUID (universally unique identifier) of an object to be accessed corresponding to an object name from a mapping relation table, wherein the access identifier is used for indicating and reading data of the object to be accessed, the mapping relation table comprises the corresponding relation between the object name of the object to be accessed and the characteristics of the object to be accessed, the characteristics of the object to be accessed comprise the UUID of the object to be accessed, and the UUID of the object to be accessed is used for indicating metadata of the object to be accessed and a storage address of the data, and then, the server reads the data of the object to be accessed according to the UUID of the object to be accessed, and sends an access response to the client device to inform the client device that the data of the object to be accessed is successfully read.

Because the server in the embodiment of the present invention stores the mapping relationship table, and the mapping relationship table includes the corresponding relationship between the object name of the object to be accessed and the characteristics of the object to be accessed, and the characteristics of the object to be accessed include the UUID for indicating the storage address of the metadata and the data of the object to be accessed, after detecting the access identifier, the server can obtain the storage address of the metadata and the data of the object to be accessed corresponding to the object name of the object to be accessed from the mapping relationship table, and obtain the data of the object to be accessed according to the storage address. Since the metadata and the storage address of the data of the object to be accessed in the server are kept unchanged, even if the object name of the object to be accessed in the mapping relation table is changed, the server can acquire the storage address of the data and the metadata of the object to be accessed, and further read the data of the object to be accessed.

In a third aspect, a server is provided that is applied to an object storage system. Specifically, the server includes a receiving unit, an obtaining unit, and a replacing unit.

The functions realized by each unit module provided by the embodiment of the invention are specifically as follows:

the receiving unit is configured to receive a renaming request sent by a client device, where the renaming request carries first information, second information, and a renaming identifier, and the renaming identifier is used to indicate that the first information is replaced by the second information; the acquiring unit is configured to acquire a target object name including the first information from a mapping relation table after the receiving unit receives the rename identifier, where the mapping relation table includes a correspondence between the target object name and a feature of the target object, and the feature of the target object includes a universally unique identifier UUID of the target object; the replacing unit is configured to replace the first information in the target object name acquired by the acquiring unit with the second information.

Further, in an implementation manner of the embodiment of the present invention, the replacing unit is specifically configured to: replacing the first directory name in the target object name with a second directory name; alternatively, the target object name is replaced with the first object name.

Further, in an implementation manner of the embodiment of the present invention, the server will further include a sending unit, where the sending unit is configured to send a response message to the client device after the replacing unit replaces the first information in the target object name with the second information, and the response message is used to indicate that the replacement of the first information with the second information is successful.

For a detailed description of the third aspect and various implementations of the third aspect of the embodiments of the present invention, reference may be made to the detailed description of the first aspect and various implementations of the first aspect; in addition, for the beneficial effects of the third aspect and various implementation manners thereof, reference may be made to beneficial effect analysis in the first aspect and various implementation manners thereof, and details are not described here.

In a fourth aspect, a server is provided that is applied to an object storage system. Specifically, the server comprises a receiving unit, an obtaining unit, a reading unit and a sending unit.

the device comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving an access request sent by client equipment, the access request carries an object name and an access identifier of an object to be accessed, and the access identifier is used for indicating to read data of the object to be accessed; an obtaining unit, configured to obtain, after the receiving unit receives the access identifier, a universally unique identifier UUID of the object to be accessed, which corresponds to the object name received by the receiving unit, from a mapping relationship table, where the mapping relationship table includes a correspondence relationship between the object name of the object to be accessed and a feature of the object to be accessed, and the feature of the object to be accessed includes the UUID of the object to be accessed; the reading unit is used for reading the data of the object to be accessed according to the UUID of the object to be accessed acquired by the acquiring unit; and the sending unit is used for sending an access response to the client device after the reading unit reads the data of the object to be accessed so as to inform the client device that the data of the object to be accessed is successfully read.

Further, in an implementation manner of the embodiment of the present invention, the characteristics of the object to be accessed further include at least one of a last modification time of the object to be accessed, an information summarization algorithm MD5 value of the object to be accessed, and a size of a storage space occupied by the object to be accessed.

For a detailed description of the fourth aspect and various implementations of the fourth aspect of the embodiments of the present invention, reference may be made to the detailed description of the second aspect and various implementations of the second aspect; moreover, for the beneficial effects of the fourth aspect and various implementation manners thereof, reference may be made to beneficial effect analysis in the second aspect and various implementation manners thereof, and details are not described here.

In a fifth aspect, a server is provided, the server comprising a communication interface, a processor, and a memory; the communication interface, the processor and the memory are connected through a system bus; the memory is configured to store computer instructions and the processor is configured to execute the computer instructions stored by the memory to cause the server to perform the renaming method as described in the first aspect and its various implementations or to perform the access method as described in the second aspect and its various implementations.

In a sixth aspect, a computer-readable storage medium is provided that includes one or more program codes; when the processor of the server is executing the program code, the server performs the renaming method as described in the first aspect and its various implementations or performs the access method as described in the second aspect and its various implementations.

Optionally, in any one of the above aspects and various implementations thereof, the mapping relation table stores a corresponding relation between an object name and a feature of an object indicated by the object name, where the feature of the object includes a universally unique identifier UUID of the object, and may further include at least one of a last modification time of the object, an information digest algorithm MD5 value of the object, and a size of a storage space occupied by the object.

If the characteristics of the object further include at least one of the latest modification time of the object, the information summary algorithm MD5 value of the object, and the size of the storage space occupied by the object, the server can more conveniently search the object name satisfying a certain condition from the mapping relation table, thereby improving the efficiency and accuracy of obtaining the data of the object.

In the embodiment of the present invention, the name of the server does not limit the device or the functional module itself, and in an actual implementation, the device or the functional module may appear by other names. As long as the functions of the respective devices or functional blocks are similar to those of the embodiments of the present invention, they are within the scope of the claims of the embodiments of the present invention and the equivalent techniques thereof.

For specific descriptions of the fifth aspect, the sixth aspect, and various implementations of the embodiments of the present invention, reference may be made to the detailed description of the first aspect and various implementations of the first aspect, or to the detailed description of the second aspect and various implementations of the second aspect; moreover, the beneficial effects of the fifth aspect, the sixth aspect and various implementation manners thereof may refer to the beneficial effect analysis in the first aspect and various implementation manners thereof or refer to the beneficial effect analysis in the second aspect and various implementation manners thereof, and details are not repeated here.

These and other aspects of embodiments of the invention will be more readily apparent from the following description.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention.

Fig. 1 is a schematic structural diagram of a directory simulated by a client device according to object names in the prior art;

FIG. 2 is a diagram illustrating a renaming structure of a file in the prior art;

FIG. 3 is a diagram illustrating a directory renaming structure in the prior art;

fig. 4 is a schematic structural diagram of a communication system according to an embodiment of the present invention;

fig. 5 is a schematic diagram illustrating an interaction and cooperation among devices in a communication system according to an embodiment of the present invention;

fig. 6 is a schematic flowchart of a renaming method according to an embodiment of the present invention;

FIG. 7 is a diagram illustrating a structure of file renaming according to an embodiment of the present invention;

FIG. 8 is a diagram illustrating the structure of directory renaming according to an embodiment of the present invention;

fig. 9 is a schematic flowchart of an access method according to an embodiment of the present invention;

fig. 10 is a first schematic structural diagram of a server according to an embodiment of the present invention;

fig. 11 is a schematic structural diagram of a server according to an embodiment of the present invention;

fig. 12 is a schematic structural diagram of a server according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be described in detail below with reference to the accompanying drawings in the embodiments of the present invention.

In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular system architecture, interfaces, techniques, etc., in order to provide a thorough understanding of the embodiments of the invention. It will be apparent, however, to one skilled in the art that the embodiments of the invention may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the embodiments of the present invention with unnecessary detail.

In this embodiment of the present invention, the term "and/or" is only one kind of association relationship describing an associated object, and means that three relationships may exist, for example, a and/or B may represent: a exists alone, A and B exist simultaneously, and B exists alone.

The terms "first" and "second," and the like in the description and claims of the present invention and the above-described drawings are used for distinguishing between different objects and not for limiting a particular order.

For a server, the object may be a file or a directory.

The directory is used to implement directory hierarchy and rights management of an Object-Based Storage System (English). If the object stored in the server is a directory, the object name of the object is a directory name, and the directory name generally ends with "/", for example: the object name corresponding to the directory dir-1 is: dir-1/, the object name corresponding to the subdirectory dir-2 is dir-1/dir-2/(plus the directory name of the parent directory), and the object name corresponding to the subdirectory dir-3 of the subdirectory dir-2 is dir-1/dir-2/dir-3/.

If an object stored in the server is a file, the object name of the object includes a path (directory name) to which the file belongs and a file name, and cannot end with "/". For example, the object name of the directory to which the file obj-1 belongs is dir-1/dir-2/dir-3/, and the object name corresponding to the file obj-1 is dir-1/dir-2/dir-3/obj-1.

The object Storage system has the characteristics of high-speed direct access of a Storage Area Network (SAN) and data sharing of Network Attached Storage (NAS), and provides a Storage system structure with high reliability, cross-platform performance and safety in data sharing. The object storage system also has the characteristics of mass expansion capability, safety, reliability and high-efficiency fusion, is suitable for mass data storage and centralized backup application scenes, and can bring high-capacity, high-reliability, easy maintenance and easy expansion values to clients.

The S3 protocol is an object storage protocol that omits the directory tree structure, uses a two-level data model of bucket-object (which can be understood as directory-object) to store data, and simplifies the read-write semantics, and is suitable for storing massive, unstructured, more read-write data. However, the current S3 protocol has no direct object renaming feature, and object renaming can only be performed through a series of operations, such as creating a new object, copying an old object into the new object, and deleting the old object.

In addition, the current S3 protocol also has no direct function of managing multilevel directories, and the implementation of multilevel directories is usually simulated by special separators in object names, and the renaming of directories is more complicated and less efficient than the renaming of objects.

Fig. 1 shows a directory modeled by a special delimiter "/" in the object name. In combination with the above explained object names, the directory name/end, the directory name of the child directory needs to be added to the directory name of the parent directory, the file name needs to be added to the directory name of the directory where the file name is located, and the end cannot be "/". Thus, the object name dir-1/corresponds to directory dir-1, the object name dir-1/dir-2/corresponds to the subdirectory dir-2 of directory dir-1, the object name dir-1/dir-2/dir-3/corresponds to the subdirectory dir-3 of directory dir-2, the object name dir-1/dir-2/dir-3/obj-1 corresponds to the file obj-1 under the dir-3 directory, the object name dir-1/dir-2/dir-3/obj-2 corresponds to the file obj-2 under the dir-3 directory, and the object name dir-1/dir-2/dir-3/obj-3 corresponds to the file obj-3 under the dir-3 directory.

The existing renaming process of the directory and the file comprises a backup process and a deletion process, but the backup process and the deletion process cause the problems of excessive IO operation times and low renaming efficiency of the system.

Illustratively, as shown in FIG. 2, the method for renaming the file-2 under the dir-3 directory to be new-file-2 is as follows: deeply copying the metadata and data of the dir-1/file-2 into a newly named object dir-1/new-file-2; and deleting the metadata and data of the dir-1/file-2. Wherein the metadata is used to record the storage location and access control information of the object.

As shown in FIG. 3, the method for renaming directory dir-1 as new-dir-1 is as follows: copying dir-1 and all objects under all subdirectories thereof to a new directory new-dir-1, wherein the metadata and data of the objects are deeply copied; deleting the metadata and data of all old objects under dir-1 and all subdirectories thereof, for example, if an object size is 1 Terabyte (TB), then there is 1TB of data to delete.

It can be seen that the backup process and the delete process in the existing renaming method can cause the problems of too many IO operation times and low renaming efficiency of the system. In a scene with a deep directory hierarchy or a very large number of files, the renaming difficulty of the existing renaming method is high.

Aiming at the problems of excessive IO times and low efficiency caused by the existing renaming method, the embodiment of the invention provides the renaming method, wherein a mapping relation table storing the corresponding relation between object names and object characteristics is created in a server in an object storage system, and the object characteristics comprise Universal Unique Identifiers (UUID) of objects for indicating metadata of the objects and storage addresses of the data, so that the server can accurately acquire the data of a certain object according to the UUID of the object, and after receiving a renaming request, the server can directly rename the object names meeting the conditions in the mapping relation table without executing a backup process and a deletion process, thereby effectively reducing the IO times of the system and improving the renaming efficiency.

Correspondingly, the embodiment of the invention also provides an access method, the server acquires the UUID of the object corresponding to a certain object name from the mapping relation table, and the UUID of the object is used for indicating the metadata of the object and the storage address of the data, so the server can read the data of the object according to the acquired UUID of the object.

The renaming method or the access method provided by the embodiment of the invention are applied to a communication system. Fig. 4 is a schematic structural diagram of a communication system according to an embodiment of the present invention. Referring to fig. 4, the communication system includes a server 40 and at least one client device 41, each client device 41 and the server 40 being connected via a network.

The server 40 stores at least one object, each object having a respective object name. The client device 41 displays an object required for the client device by communicating with the server 40.

The server 40 in the embodiment of the present invention may be a physical machine, a virtual machine, or any other device that provides an object storage service, which is not specifically limited in the embodiment of the present invention.

Referring to fig. 4, fig. 5 is a schematic diagram of the interactive cooperation between the server 40 and the client device 41 in the communication system. The communication process of each client device 41 and the server 40 in the communication system is the same. For simplicity, fig. 5 shows only the communication between one of the client devices 41 and the server 40.

Referring to fig. 5, the server 40 in the communication system includes a mapping table 400, where the mapping table 400 holds a correspondence between object names and characteristics of objects, where the characteristics of the objects include UUIDs of the objects, and the UUIDs are used to indicate metadata of the objects and storage addresses of data, where the metadata of the objects includes creation time of the objects, last modification time, sizes of storage spaces occupied by the objects, and the like.

Specifically, at least one object name in the mapping relationship table 400 may be arranged from small to large or from large to small in a lexicographic order, and each object name uniquely corresponds to one UUID.

The mapping relation table 400 may be stored in the server 40 in a table form. Illustratively, the format of the mapping relationship table 400 including object names and UUIDs of objects is shown in table 1.

It should be noted that table 1 only shows a storage form of the correspondence between the object name and the UUID of the object in the server 40 in a table form, and is not limited to the storage form of the correspondence between the object name and the UUID of the object in the server 40, and of course, the storage form of the correspondence between the object name and the UUID of the object in the server 40 may also be stored in other forms, which is not limited in the embodiment of the present invention.

TABLE 1

Name of object	UUID of object
		dir‐1/file‐1	obj‐uuid‐1
dir‐1/dir‐2/	obj‐uuid‐2
		dir‐1/dir‐2/file‐2	obj‐uuid‐3
……	……
		dir‐1/dir‐2/dir‐3/	obj‐uuid‐4

Optionally, the characteristics of the object in the mapping relation table 400 may further include at least one of a last modification time of the object, an information summarization Algorithm (MD 5) value of the object, and a size of a storage space occupied by the object. In this way, the server 40 can more conveniently and rapidly search the object to be searched by the client device according to the mapping relation table 400, thereby improving the efficiency and accuracy of obtaining the object.

Illustratively, in conjunction with table 1, if the characteristics of the object further include the last modification time of the object, the MD5 value of the object, and the size of the storage space occupied by the object, the format of the mapping relation table 400 is shown in table 2. In Table 2, the unit of the occupied storage space is Kilobytes (KB).

TABLE 2

Since the last modification time of the object, the MD5 value of the object, and the size of the storage space occupied by the object in the mapping relationship table 400 are optional, they are indicated by the dashed boxes in fig. 5.

Specifically, if the mapping relationship table 400 stored in the server 40 is embodied in a table form, at least one table may be stored in the server 40, and the format of each table may be the format shown in table 1.

The server 40 further comprises a communication interface 401, a processor 402 and a memory 403.

The communication interface 401 is used for communication with the client device 41 connected to the server 40. The memory 403 is used for storing the mapping relation table 400, and may also be used for storing software programs and application modules. Processor 402 is operative to run or execute software programs and application modules stored in memory 403 in order to perform various functions of server 40.

The client device 41 in the communication system comprises a communication interface 411, a processor 412, a memory 413 and a display 414.

The communication interface 410 is used for communicating with the server 40 connected to the client device 41. The memory 413 is used for storing software programs and application modules. Processor 412 is operative to run or execute software programs and application modules stored in memory 413 to facilitate various functions of client device 41. Display 414 is used to enable user interaction with client device 41.

The renaming method provided by the embodiment of the invention is suitable for an object storage system, and the object storage system adopts an object storage protocol, such as an S3 protocol and a swift (object storage component in OpenStack project) protocol.

Fig. 6 is a flowchart illustrating a renaming method according to an embodiment of the present invention, where the renaming method may be applied to the communication system shown in fig. 4 or fig. 5.

Referring to fig. 6, the renaming method includes:

s600, the client device sends a renaming request carrying the first information, the second information and the renaming identifier to the server.

The renaming identifier is used for indicating that the first information is replaced by the second information.

S601, after detecting the renaming identifier, the server acquires a target object name including the first information from the mapping relation table.

The mapping relation table comprises a corresponding relation between a target object name and the characteristics of the target object, the characteristics of the target object comprise a UUID of the target object, and the UUID of the target object is used for indicating the metadata of the target object and the storage address of the data.

S602, the server replaces the first information in the target object name with the second information.

S603, the server sends a response message to the client device, indicating that the first information has been successfully replaced with the second information.

In the renaming method provided by the embodiment of the present invention, the client device first sends a renaming request carrying the first information, the second information, and the renaming identifier to the server, that is, executes S600.

As can be seen from the foregoing description, the object may be a file or a directory for the server. If the object is a file, the object name of the object comprises the directory name and the file name of the directory to which the file belongs; if the object is a parent directory, the object name of the object is the name of the parent directory; if the object is a child directory of the parent directory, the object name of the object comprises the name of the parent directory and the name of the child directory. When a client device opposite to the server displays a certain level of directory, the directory name of the level of directory is displayed, and similarly, when the client device displays a certain file, the file name of the file is displayed. Thus, what the user sees is the directory name of the current directory or the file name of the current file.

In this scenario, the instruction input by the user may be used to instruct renaming a file, or to rename a directory and a file in the directory. In this way, after receiving the instruction input by the user, the client device can send a renaming request to the server according to the instruction input by the user. The renaming request carries first information which is an original directory name in a certain object name and second information which is a new directory name in the object name, or the first information is the original object name of a certain object and the second information is the new object name of the object. That is, the first information in the embodiment of the present invention may be a certain object name before renaming, or may be partial content in a certain object name before renaming.

The interface for the client device to send the renaming request in the embodiment of the present invention is the same as an interface used in the interaction between the client device and the server in the prior art, and the interface may be a Copy interface or an upload interface. In contrast, the renaming request in the embodiment of the present invention carries a renaming identifier.

It should be noted that, in the embodiment of the present invention, the format of the renaming request message is not specifically limited.

Illustratively, the renaming request sent by the client device to the server is a Hypertext transfer protocol (HTTP) request, where the HTTP request is used to indicate that the client device requests to rename the file-1 in the directory dir-1 to new-file-1, and then the first information in the HTTP request is dir-1/file-1, and the second information is dir-1/new-file-1. Specifically, the HTTP request carries an operation code PUT, the content corresponding to the operation code is dir-1/new-file-1 HTTP/1.1, and also carries an x-amz-copy-source header field and an x-obs-file-rename header field, the x-amz-copy-source header field indicates that the original object name is dir-1/file-1, and the content of the x-obs-file-rename header field is true (english: true), and indicates that the renaming request is used for indicating that dir-1/file-1 is replaced by dir-1/new-file-1. Specifically, the HTTP request may be expressed as:

PUT dir‐1/new‐file‐1HTTP/1.1

x‐amz‐copy‐source dir‐1/file‐1

x‐obs‐file‐rename true

illustratively, the HTTP request sent by the client device to the server is used to indicate that the client device requests to rename the directory dir-1 to new-dir-1, and then the first information in the HTTP request is dir-1/, and the second information is new-dir-1/. Specifically, the HTTP request carries an operation code PUT, the content corresponding to the operation code is new-dir-1/HTTP/1.1, the HTTP request also carries an x-amz-copy-source header field and an x-obs-dir-rename header field, and the x-amz-copy-source header field indicates that the original directory name dir-1/, and the content of the x-obs-dir-rename header field is true, and indicates that the renaming request is used for indicating renaming dir-1/to be new-dir-1/. Specifically, the HTTP request may be expressed as:

PUT new‐dir‐1/HTTP/1.1

x‐amz‐copy‐source dir‐1/

x‐obs‐dir‐rename true

specifically, after receiving the renaming request, the server obtains the target object name including the first information from the mapping relationship table, i.e., executes S601.

The server in the embodiment of the invention stores a mapping relation table, and the mapping relation table comprises a corresponding relation between object names and characteristics of objects. The specific format of the mapping relationship table can refer to table 1 or table 2, which is not described in detail herein.

It should be noted that, for convenience of distinction, the file names of the files belonging to the same directory in the mapping relation table in the embodiment of the present invention are different from each other, that is, the file names in the same directory are unique. Since the file names in the same directory are unique, the object names stored in the server are different from each other. When the mapping relation table is expressed in a table format, the object names can be directly used as main keys, the object names are sequentially arranged from small to large or from large to small according to the lexicographic order, and the index of the data column is established, so that the rapid query performance of the data table can be improved.

It is understood that, since the object name is only the name of a certain object, the object name in the mapping relationship table can be changed at any time, and since the characteristics of the object include the UUID of the object and the UUID of the object is used to indicate the storage address of the metadata and data of the object, the storage address of the metadata and data of the object is kept unchanged, and therefore, the UUID of the object corresponding to a certain object name in the mapping relationship table should be kept unchanged.

Specifically, after receiving the renaming request, the server obtains a target object name including the first information from at least one object name in the mapping relationship table, where the number of the target object names is at least one.

For example, if the mapping relationship table in the server is as shown in table 1 above, the first information is dir-1/dir-2/, and the second information is dir-1/new-dir-2/, the server obtains the target object name including dir-1/dir-2/, such as dir-1/dir-2/, dir-1/new-dir-2/and dir-1/dir-2/file-2 and dir-1/dir-2/dir-3/, from table 1 after receiving the renaming request carrying dir-1/dir-2/, dir-1/new-dir-2/, and the renaming identifier.

In addition, the server, upon receiving the renaming request, also identifies the first information and the second information.

Further, after acquiring the target object name, the server replaces the first information in the target object name with the second information, i.e., executes S602.

Specifically, after the server obtains the target object name, the first information in the target object name is updated in batches, so that the operating system of system IO is effectively reduced, the time waste of renaming is reduced, and the renaming efficiency is improved.

Optionally, if the server uses the database to store the mapping relationship table, the server may perform batch update through the related program code.

Illustratively, if the server performs renaming of the filename through a Structured Query Language (SQL) statement, and the client device requests renaming of the file-2 in the dir-1 directory to be new-file-2, the SQL statement is expressed as: the update table set object name is 'dir-1/new-file-2' where object name is 'dir-1/file-2', and the SQL statement indicates that dir-1/file-2 is replaced with dir-1/new-file-2.

As shown in fig. 7, if the mapping relationship table stored in the server includes object names dir-1/file-1, dir-1/file-2, and dir-1/file-3, the server acquires the target object name dir-1/file-2 from the mapping relationship table according to the update table set object name ═ dir-1/new-file-2 'where the object name is ═ dir-1/file-2', and replaces the target object name dir-1/file-2 with dir-1/new-file-2.

Illustratively, if the server performs the renaming of the directory name by an SQL statement and the client device requests to rename the directory dir-1 to new-dir-1, the SQL statement is expressed as: the update table set object name is left _ place (object names, 'dir-1/', 'new-dir-1/') where the left _ place (a, B) function indicates that a is looked up from the left side of the string and replaced with B, and is matched only once). The SQL statement represents the replacement of dir-1/in the object name including dir-1/with new-dir-1/.

As shown in fig. 8, if the mapping relationship table stored in the server includes object names dir-1/file-1, dir-1/dir-2/dir-3/obj-1, dir-1/dir-2/dir-3/obj-2, and dir-1/dir-2/dir-3/obj-3, the server determines that all object names are target object names according to a date table object name of left _ replace (object names dir-1/', ' new-dir-1/') where object name like ' dir-1/% ', and replaces dir-1/new-dir-1/1 in all object names.

The server replaces the first information in the determined target object name with the second information, and then sends a response message to the client device, that is, S603 is executed.

Optionally, the response message in the embodiment of the present invention may include an OK character, and may also include an Acknowledgement (ACK) character, which is not specifically limited in the embodiment of the present invention.

After the server sends the response message to the client device, the client device learns that the first information is replaced by the second information, and in subsequent communication, the client device can directly access the object by using the second information.

It can be seen that by using the renaming method provided by the embodiment of the invention, the renaming of the directory name or the renaming of the file name can be realized only by one-time interaction between the client device and the server, so that the problems of more system IO times and low renaming efficiency caused by the conventional renaming method are effectively solved, the system IO times are reduced, and the renaming efficiency is improved.

Further, after receiving the request sent by the client device, the server in the embodiment of the present invention may first detect whether the received request carries the rename identifier. If the server determines that the received request carries the renaming identifier, the server executes a relevant process according to the renaming method provided by the embodiment of the invention.

Fig. 9 is a flowchart illustrating an access method according to an embodiment of the present invention, where the access method may be applied to the communication system shown in fig. 4 or fig. 5.

Referring to fig. 9, the access method includes:

s900, the client device sends an access request carrying the object name and the access identifier of the object to be accessed to the server.

The access identifier is used for instructing the server to read the data of the object to be accessed.

S901, after detecting the access identifier, the server acquires the UUID of the object to be accessed corresponding to the object name of the object to be accessed from the mapping relation table.

The mapping relation table comprises a corresponding relation between the object name of the object to be accessed and the characteristics of the object to be accessed, the characteristics of the object to be accessed comprise a UUID of the object to be accessed, and the UUID of the object to be accessed is used for indicating the metadata of the object to be accessed and the storage address of the data.

S902, the server reads the data of the object to be accessed according to the UUID of the object to be accessed.

S903, the server sends an access response to the client device to inform the client device that the data of the object to be accessed has been successfully read.

The mapping relationship table in the embodiment of the present invention is the same as the mapping relationship table in the embodiment shown in fig. 6, and both include a correspondence between an object name and a feature of an object. The characteristics of the object in the mapping relation table comprise the UUID of the object, and the UUID of the object is used for indicating the metadata of the object and the storage address of the data.

The object name of the object to be accessed is one of the object names in the mapping relation table, and after receiving the access request, the server can acquire the UUID of the object to be accessed corresponding to the object name of the object to be accessed from the mapping relation table, and further read the data of the object to be accessed according to the UUID of the object to be accessed.

As can be seen from the embodiment shown in fig. 6, each object name in the mapping table can be modified, and even if the object name of an object is modified, the modified object name in the mapping table still corresponds to the UUID of the object. The client device can acquire each modified object name, and thus, the client device can send an access request by using a certain modified object name, so that the server can acquire the UUID of the object corresponding to the modified object name from the mapping relation table, and further read the data of the object.

In the embodiment of the present invention, the access request sent by the client device may refer to an access request sent by the client device in the prior art, and the access response sent by the server may also refer to an access response sent by the server in the prior art, which is not described in detail herein.

Embodiments of the present invention provide a server, which is configured to perform the steps performed by the server in the above renaming method. The server provided by the embodiment of the invention can comprise modules corresponding to the corresponding steps.

In the embodiment of the present invention, the server may be divided into the functional modules according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The division of the modules in the embodiment of the present invention is illustrative, and is only a logic function division, and there may be another division manner in actual implementation.

Fig. 10 shows a possible structure diagram of the server according to the above embodiment, in the case of dividing each functional module according to each function. As shown in fig. 10, the server includes a receiving unit 100, an obtaining unit 101, and a transmitting unit 102. The receiving unit 100 is configured to support the server to perform S600 in fig. 6 and/or perform S900 in fig. 9; the obtaining unit 101 is configured to support the server to execute S601 in fig. 6, and/or execute S901 in fig. 9; the sending unit 102 is configured to support the server to execute S603 in fig. 6 and/or execute S903 in fig. 9. The server further comprises a replacement unit 103 or a reading unit 104. The replacing unit 103 is configured to support the server to execute S602 in fig. 6; the reading unit 104 is used to support the server to execute S902 in fig. 9. All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again. The server further comprises a storage unit 105 for storing a mapping relation table.

Fig. 11 shows a possible schematic diagram of the server involved in the above-described embodiment, in the case of an integrated unit. As shown in fig. 11, the server includes: a processing module 110 and a communication module 111. The processing module 110 is used to control and manage the actions of the server, for example, the processing module 110 is used to support the server to perform S601 and S602 in fig. 6, and/or to perform S901 and S902 in fig. 9, and/or other processes for the techniques described herein. The communication module 111 is used to support the server to communicate with the client device, for example, the communication module 111 is used to support the server to perform S600 and S603 in fig. 6, and/or to perform S900 and S903 in fig. 9. The server may also include a storage module 112 for storing the mapping relationship table and may also be used to store program codes and data for the server.

The Processing module 110 may be a processor or a controller, such as a Central Processing Unit (CPU) or a Digital Signal Processor (DSP). Which may implement or execute the various illustrative logical blocks, modules, and circuits described in connection with the embodiment disclosure. The communication module 111 may be a transceiver, a transceiving circuit or a communication interface, etc. The storage module 112 may be a memory.

When the processing module 110 is a processor, the communication module 111 is a communication interface, and the storage module 112 is a memory, the server according to the embodiment of the present invention may be the server shown in fig. 12.

As shown in fig. 12, the server includes: a communication interface 120, a processor 121, and a memory 122. The communication interface 120, the processor 121 and the memory 122 are connected by a system bus 123, and perform mutual communication.

When the server is running, the server performs the renaming method of the embodiment shown in FIG. 6 and/or performs the access method of the embodiment shown in FIG. 9. For a specific renaming method, reference may be made to the related description in the embodiment shown in fig. 6, and for a specific access method, reference may be made to the related description in the embodiment shown in fig. 9, which is not described herein again.

The server shown in fig. 12 is the same as the server 40 in fig. 5, and the system bus 123 is not shown in fig. 5.

Wherein the communication interface 120 is used for communicating with client devices, such as ethernet, WLAN, etc.

The memory 122 may be used to store the mapping relationship table, or may be used to store a software program and an application module, and the processor 121 executes various functional applications and data processing of the server by running the software program and the application module stored in the memory 122.

The memory 122 may mainly include a storage program area 1220 and a storage data area 1221, wherein the storage program area 1220 may store an operating system, an application program required for at least one function, such as a function of replacing the first information with the second information, and the like; the storage data area 1221 may store a mapping relationship table.

The Memory 122 may be a Read-Only Memory (ROM), or other types of static storage devices that can store static information and instructions, a Random Access Memory (RAM), or other types of dynamic storage devices that can store information and instructions, or an Electrically Erasable Programmable Read-Only Memory (EEPROM), a magnetic disk storage medium, or other magnetic storage devices, or any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a server, but is not limited thereto.

The memory 122 may be separate and coupled to the processor 121 via a system bus 123. The memory 122 may also be integrated with the processor 121.

Processor 121 is the control center for the server. The processor 121 connects various parts of the entire server using various interfaces and lines, performs various functions of the server and processes data by running or executing software programs and/or application modules stored in the memory 122 and calling data stored in the memory 122, thereby monitoring the server as a whole.

In a specific implementation, the processor 121 may include one or more CPUs, for example, the processor 121 in fig. 12 includes a CPU 0 and a CPU 1.

The system bus 123 may be divided into an address bus, a data bus, a control bus, and the like. For clarity of illustration in the embodiments of the present invention, the various buses are illustrated in FIG. 12 as system bus 123.

The embodiment of the invention provides a server, wherein after receiving a renaming request which is sent by client equipment and carries first information, second information and a renaming identifier, the server acquires a target object name comprising the first information from a mapping relation table, the renaming identifier is used for indicating that the first information is replaced by the second information, the mapping relation table comprises a corresponding relation between the target object name and the characteristics of a target object, the characteristics of the target object comprise a Universal Unique Identifier (UUID) of the target object, the UUID of the target object is used for indicating metadata of the target object and a storage address of the data, and then the server replaces the first information in the target object name by the second information.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions. For the specific working processes of the system, the apparatus and the unit described above, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.

In the embodiments provided in the present invention, it should be understood that the disclosed system, apparatus and method may be implemented in other ways.

For example, the above-described apparatus embodiments are merely illustrative, and for example, a module or a unit may be divided into only one logic function, and may be implemented in other ways, for example, a plurality of units or components may be combined or integrated into another system.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium.

Based on such understanding, all or part of the technical solutions of the embodiments of the present invention may be embodied in the form of software products. The computer software product is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) or a processor to execute all or part of the steps of the method according to the embodiments of the present invention. The storage medium is, for example: a Universal serial bus flash disk (usb disk), a removable hard disk, a ROM, a RAM, a magnetic disk or an optical disk, and other various media capable of storing program codes.

It will be apparent to those skilled in the art that various changes and modifications may be made in the embodiments of the present invention without departing from the scope of the invention. Thus, provided that such modifications and variations of the embodiments of the present invention fall within the scope of the claims of the present invention, it is intended that the embodiments of the present invention also encompass such modifications and variations.

Claims

1. A renaming method applied to a server in an object storage system, the renaming method comprising:

the server receives a renaming request sent by client equipment, wherein the renaming request carries first information, second information and a renaming identifier, and the renaming identifier is used for indicating that the first information is replaced by the second information;

after detecting the renaming identifier, the server acquires a target object name comprising the first information from a mapping relation table, wherein the mapping relation table comprises a corresponding relation between the target object name and the characteristics of a target object, the characteristics of the target object comprise a Universal Unique Identifier (UUID) of the target object, and the UUID of the target object is used for indicating metadata of the target object and a storage address of the data;

and the server replaces the first information in the target object name with the second information.

2. The renaming method according to claim 1, wherein the server replaces the first information in the target object name with the second information, including:

the server replaces a first directory name in the target object name with a second directory name;

alternatively, the first and second electrodes may be,

the server replaces the target object name with a first object name.

3. The renaming method according to claim 1 or 2,

the characteristics of the target object further include at least one of a last modification time of the target object, an information digest algorithm MD5 value of the target object, and a size of a storage space occupied by the target object.

4. The renaming method according to any one of claims 1 to 2, wherein after the server replaces the first information in the target object name with the second information, the renaming method further comprises:

and the server sends a response message to the client device, wherein the response message is used for indicating that the first information is successfully replaced by the second information.

5. The renaming method according to claim 3, wherein after the server replaces the first information in the target object name with the second information, the renaming method further comprises:

6. A server, applied to an object storage system, the server comprising:

the client side equipment comprises a receiving unit, a sending unit and a processing unit, wherein the receiving unit is used for receiving a renaming request sent by client side equipment, the renaming request carries first information, second information and a renaming identifier, and the renaming identifier is used for indicating that the first information is replaced by the second information;

an obtaining unit, configured to obtain, after the receiving unit receives the rename identifier, a target object name including the first information from a mapping relation table, where the mapping relation table includes a correspondence between the target object name and a feature of a target object, and the feature of the target object includes a universally unique identifier UUID of the target object;

and a replacing unit, configured to replace the first information in the target object name acquired by the acquiring unit with the second information.

7. The server according to claim 6, wherein the replacing unit is specifically configured to:

replacing a first directory name in the target object name with a second directory name;

alternatively, the first and second electrodes may be,

and replacing the target object name with a first object name.

8. The server according to claim 6 or 7,

9. A server according to any of claims 6-7, characterized in that the server will further comprise a sending unit,

the sending unit is configured to send a response message to the client device after the replacing unit replaces the first information in the target first object name with the second information, where the response message is used to indicate that the first information is successfully replaced with the second information.

10. The server according to claim 8, wherein the server is further to comprise a sending unit,

11. A server, for use in an object storage system, the server comprising a communication interface, a processor and a memory; wherein the communication interface, the processor, and the memory are connected by a system bus;

the memory is configured to store computer instructions and the processor is configured to execute the computer instructions stored by the memory to cause the server to perform the renaming method as claimed in any one of claims 1 to 5.