CN117714539A - Metadata migration method and device, electronic equipment and readable storage medium - Google Patents
Metadata migration method and device, electronic equipment and readable storage medium Download PDFInfo
- Publication number
- CN117714539A CN117714539A CN202311575641.5A CN202311575641A CN117714539A CN 117714539 A CN117714539 A CN 117714539A CN 202311575641 A CN202311575641 A CN 202311575641A CN 117714539 A CN117714539 A CN 117714539A
- Authority
- CN
- China
- Prior art keywords
- request
- metadata
- client
- bucket
- resource bucket
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 230000005012 migration Effects 0.000 title claims abstract description 78
- 238000013508 migration Methods 0.000 title claims abstract description 78
- 238000000034 method Methods 0.000 title claims abstract description 52
- 230000004044 response Effects 0.000 claims abstract description 52
- 238000005538 encapsulation Methods 0.000 claims abstract description 9
- 238000004590 computer program Methods 0.000 claims description 6
- 238000004806 packaging method and process Methods 0.000 claims description 6
- 230000004048 modification Effects 0.000 claims description 3
- 238000012986 modification Methods 0.000 claims description 3
- 230000008569 process Effects 0.000 description 7
- 230000000694 effects Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The application discloses a metadata migration method, a metadata migration device, electronic equipment and a readable storage medium, and belongs to the technical field of computers. The method comprises the steps that a client sends an object obtaining request to a source resource barrel, the client receives a first response message from the source resource barrel, the first response message comprises a second object and a return request header, the return request header comprises a target byte stream, and the target byte stream is obtained based on metadata encapsulation corresponding to the second object; the client sends an uploading object request to the target resource bucket based on the first response message, wherein the uploading object request is a request obtained based on the second object and the target byte stream, and the uploading object request comprises a setting request header, and the setting request header is used for setting metadata of the second object in the target resource bucket. In this way, the request logic for migrating the metadata is added in the request logic for migrating the data, so that metadata of the object does not need to be acquired and set independently, and migration efficiency is improved.
Description
Technical Field
The application belongs to the technical field of computers, and particularly relates to a metadata migration method, a metadata migration device, electronic equipment and a readable storage medium.
Background
The prior art can migrate an object to be acquired from a source resource bucket to a target resource bucket, but cannot migrate metadata of the object to be acquired from the source resource bucket to the target resource bucket.
In the prior art, metadata of an object to be acquired is manually configured in a target resource bucket after the object to be acquired is migrated, and the metadata cannot be directly migrated.
Therefore, the prior art has a problem of low migration efficiency when migrating metadata.
Disclosure of Invention
An object of the embodiments of the present application is to provide a metadata migration method, apparatus, electronic device, and readable storage medium, which can solve the problem of low migration efficiency in metadata migration in the prior art.
In a first aspect, an embodiment of the present application provides a metadata migration method, applied to a client, where the client includes a configuration interface for bucket metadata, the method includes:
the client sends an acquisition object request to a source resource bucket, wherein the acquisition object request comprises a first object and a custom request header configured at the client through a configuration interface of the bucket metadata, the custom request header comprises migration configuration of acquisition metadata configured by a user, the acquisition object request is used for requesting acquisition of metadata of a second object and the second object in the source resource bucket, and the first object and the second object have the same prefix and/or suffix;
the client receives a first response message from the source resource bucket, wherein the first response message comprises the second object and a return request header, the return request header comprises a target byte stream, and the target byte stream is obtained based on metadata encapsulation corresponding to the second object;
the client sends an uploading object request to a target resource bucket based on the first response message, wherein the uploading object request is a request obtained based on the second object and the target byte stream, and the uploading object request comprises a setting request header, and the setting request header is used for setting metadata of the second object in the target resource bucket.
Optionally, the migration configuration includes at least one of:
first configuration information, wherein the first configuration information is used for indicating modification time for acquiring the second object;
the second configuration information is used for indicating the storage category of the second object;
third configuration information, wherein the third configuration information is used for indicating to acquire the access right of the second object;
fourth configuration information, wherein the fourth configuration information is used for indicating to acquire multi-version information of the second object;
fifth configuration information, the fifth configuration information is used for indicating to obtain soft link information of the second object;
sixth configuration information, wherein the sixth configuration information is used for indicating to acquire a custom request metadata header of the second object;
seventh configuration information, where the seventh configuration information is used to indicate an additional upload type for obtaining the second object;
eighth configuration information, where the eighth configuration information is used to indicate a storage manner of the second object;
and ninth configuration information, wherein the ninth configuration information is used for indicating to acquire the limited save time of the second object.
Optionally, after the client sends the request for uploading the object to the target resource bucket, the method further includes:
the client receives a second response message from the target resource bucket, wherein the second response message is obtained based on the setting request head;
and the client generates a metadata migration success notification according to the second response message.
In a second aspect, an embodiment of the present application provides a metadata migration method, applied to a source resource bucket, where the method includes:
the source resource bucket receives an object acquisition request from a client;
under the condition that the source resource bucket meets a first preset condition and the acquisition object request comprises a custom request header, acquiring metadata corresponding to an object to be acquired according to the custom request header and packaging the metadata into a target byte stream, wherein the custom request header comprises migration configuration of acquired metadata configured by a user;
sending a first response message to the client, wherein the first response message comprises a second object and a return request header, and the return request header comprises a target byte stream;
the first preset condition is that the source resource bucket comprises a pre-configured metadata migration rule and is provided with a second object, and the second object is identical to the prefix and/or the suffix of the first object.
In a third aspect, an embodiment of the present application provides a metadata migration method, applied to a target resource bucket, where the method includes:
the target resource bucket receives an uploading object request from a client, wherein the uploading object request comprises a setting request header, and the setting request header comprises the target byte stream;
and under the condition that the target resource bucket meets the preset metadata migration rule of the target resource bucket and the uploading object request comprises a set request head, the target resource bucket analyzes the target byte stream and sets metadata corresponding to an object to be acquired.
In a fourth aspect, an embodiment of the present application provides a metadata migration apparatus, applied to a client, where the client includes a configuration interface of bucket metadata, the apparatus includes:
a first sending module, configured to send, by the client, an acquisition object request to a source resource bucket, where the acquisition object request includes a first object and a custom request header configured at the client through a configuration interface of the bucket metadata, where the custom request header includes a migration configuration of acquisition metadata configured by a user, where the acquisition object request is used to request acquisition of metadata of a second object in the source resource bucket and of the second object, where the first object and the second object have the same prefix and/or suffix;
the first receiving module is used for receiving a first response message from the source resource bucket by the client, wherein the first response message comprises the second object and a return request header, the return request header comprises a target byte stream, and the target byte stream is obtained based on metadata encapsulation corresponding to the second object;
the second sending module is configured to send, by the client, an upload object request to a target resource bucket based on the first response message, where the upload object request is a request obtained based on the second object and the target byte stream, and the upload object request includes a setting request header, where the setting request header is used to set metadata of the second object in the target resource bucket.
In a fifth aspect, an embodiment of the present application provides a metadata migration apparatus, applied to a source resource bucket, where the apparatus includes:
the second receiving module is used for receiving an object obtaining request from the client by the source resource bucket;
the first acquisition module is used for acquiring metadata corresponding to an object to be acquired according to the self-defined request header and packaging the metadata into a target byte stream under the condition that the source resource bucket meets a first preset condition and the acquired object request comprises the self-defined request header, wherein the self-defined request header comprises migration configuration of acquired metadata configured by a user;
a third sending module, configured to send a first response message to the client, where the first response message includes a second object and a return request header, and the return request header includes a target byte stream;
the first preset condition is that the source resource bucket comprises a pre-configured metadata migration rule and is provided with a second object, and the second object is identical to the prefix and/or the suffix of the first object.
In a sixth aspect, an embodiment of the present application provides a metadata migration apparatus, applied to a target source resource bucket, where the apparatus includes:
a third receiving module, configured to receive, by the target resource bucket, an upload object request from a client, where the upload object request includes a setting request header, and the setting request header includes the target byte stream;
the analyzing module is configured to, when the target resource bucket meets the target resource bucket preconfiguration metadata migration rule and the uploading object request includes a setting request header, analyze the target byte stream and set metadata corresponding to an object to be acquired by the target resource bucket.
In a seventh aspect, an embodiment of the present application provides an electronic device, where the electronic device includes a processor, a memory, and a program stored on the memory and executable on the processor, where the program is executed by the processor to implement the steps of the methods according to the first aspect, the second aspect, and the third aspect.
In an eighth aspect, embodiments of the present application provide a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the methods according to the first, second and third aspects.
In this embodiment of the present application, an acquiring object request is sent to a source resource bucket by the client, where the acquiring object request includes a first object and a custom request header configured at the client through a configuration interface of the bucket metadata, the custom request header includes a migration configuration of acquiring metadata configured by a user, and the acquiring object request is used to request to acquire metadata of a second object and a second object in the source resource bucket, where the first object and the second object have the same prefix and/or suffix; the client receives a first response message from the source resource bucket, wherein the first response message comprises the second object and a return request header, the return request header comprises a target byte stream, and the target byte stream is obtained based on metadata encapsulation corresponding to the second object; the client sends an uploading object request to a target resource bucket based on the first response message, wherein the uploading object request is a request obtained based on the second object and the target byte stream, and the uploading object request comprises a setting request header, and the setting request header is used for setting metadata of the second object in the target resource bucket. In this way, the request logic for migrating the metadata is added in the request logic for migrating the data, so that metadata of the object does not need to be acquired and set independently, and migration efficiency is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments of the present application will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flow chart of a metadata migration method provided in an embodiment of the present application;
FIG. 2 is a schematic diagram illustrating migration of bucket object data and metadata according to an embodiment of the present disclosure;
fig. 3 is a schematic flow chart of a source resource bucket processing an object obtaining request according to an embodiment of the present application;
fig. 4 is a schematic flow chart of a target resource bucket processing an object obtaining request according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a metadata migration apparatus according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
Technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application are within the scope of the protection of the present application.
The terms first, second and the like in the description and in the claims, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged, as appropriate, such that embodiments of the present application may be implemented in sequences other than those illustrated or described herein, and that the objects identified by "first," "second," etc. are generally of a type and not limited to the number of objects, e.g., the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/", generally means that the associated object is an "or" relationship.
The method provided by the embodiment of the application is described in detail below through specific embodiments and application scenes thereof with reference to the accompanying drawings.
As shown in fig. 1, in order to illustrate a flow chart of a metadata migration method provided in an embodiment of the present application, an execution body of the metadata migration method in this embodiment may be a client, and specifically includes the following steps:
step 101, the client sends an acquisition object request to a source resource bucket, wherein the acquisition object request comprises a first object and a custom request header configured at the client through a configuration interface of the bucket metadata, the custom request header comprises migration configuration of acquisition metadata configured by a user, the acquisition object request is used for requesting acquisition of a second object in the source resource bucket and metadata of the second object, and the first object and the second object have the same prefix and/or suffix;
the above client may be understood as a mobile phone application and may also be understood as a web application, which is not further limited herein.
The source resource bucket can be understood as a server, and can also be understood as a cloud server. It should be understood that the triggering condition of the client sending the request for obtaining the object to the source resource bucket may be a control input from an operator, or may be a voice input from an operator, which is not limited herein.
Wherein the first object and the second object can be understood as data such as video, audio, text, etc.
Further, the first object and the second object have the same prefix and/or suffix, which is to be understood that when the first object is video data, the second object should also be video data; when the first object is audio data, the second object should also be audio data.
The custom request header may be located in a header of the get object request.
102, the client receives a first response message from the source resource bucket, wherein the first response message comprises the second object and a return request header, the return request header comprises a target byte stream, and the target byte stream is obtained based on metadata encapsulation corresponding to the second object;
wherein the return request header may be located in a header of the first response message.
Step 103, the client sends an uploading object request to a target resource bucket based on the first response message, wherein the uploading object request is a request obtained based on the second object and the target byte stream, and the uploading object request comprises a setting request header, and the setting request header is used for setting metadata of the second object in the target resource bucket.
The target resource bucket can be understood as a server except for the server corresponding to the source resource bucket. It may also be understood as a cloud server other than the server to which the source resource bucket corresponds.
In this embodiment of the present application, an acquiring object request is sent to a source resource bucket by the client, where the acquiring object request includes a first object and a custom request header configured at the client through a configuration interface of the bucket metadata, the custom request header includes a migration configuration of acquiring metadata configured by a user, and the acquiring object request is used to request to acquire metadata of a second object and a second object in the source resource bucket, where the first object and the second object have the same prefix and/or suffix; the client receives a first response message from the source resource bucket, wherein the first response message comprises the second object and a return request header, the return request header comprises a target byte stream, and the target byte stream is obtained based on metadata encapsulation corresponding to the second object; the client sends an uploading object request to a target resource bucket based on the first response message, wherein the uploading object request is a request obtained based on the second object and the target byte stream, and the uploading object request comprises a setting request header, and the setting request header is used for setting metadata of the second object in the target resource bucket. In this way, the request logic for migrating the metadata is added in the request logic for migrating the data, so that metadata of the object does not need to be acquired and set independently, and migration efficiency is improved.
Optionally, in some embodiments, the migration configuration includes at least one of:
first configuration information, wherein the first configuration information is used for indicating modification time for acquiring the second object;
the second configuration information is used for indicating the storage category of the second object;
third configuration information, wherein the third configuration information is used for indicating to acquire the access right of the second object;
fourth configuration information, wherein the fourth configuration information is used for indicating to acquire multi-version information of the second object;
fifth configuration information, the fifth configuration information is used for indicating to obtain soft link information of the second object;
sixth configuration information, wherein the sixth configuration information is used for indicating to acquire a custom request metadata header of the second object;
seventh configuration information, where the seventh configuration information is used to indicate an additional upload type for obtaining the second object;
eighth configuration information, where the eighth configuration information is used to indicate a storage manner of the second object;
and ninth configuration information, wherein the ninth configuration information is used for indicating to acquire the limited save time of the second object.
In the embodiment of the application, by adopting the mode, a user can flexibly configure the required metadata according to own requirements, so that the adaptability of the metadata migration method is improved.
Optionally, in some embodiments, after the client sends the upload object request to the target resource bucket, the method further comprises:
the client receives a second response message from the target resource bucket, wherein the second response message is obtained based on the setting request head;
and the client generates a metadata migration success notification according to the second response message.
In the embodiment of the application, the user can be prompted more clearly that the migration is successful through the mode.
As shown in fig. 3, an embodiment of the present application provides a metadata migration method, applied to a source resource bucket, including:
the source resource bucket receives an object acquisition request from a client;
under the condition that the source resource bucket meets a first preset condition and the acquisition object request comprises a custom request header, acquiring metadata corresponding to an object to be acquired according to the custom request header and packaging the metadata into a target byte stream, wherein the custom request header comprises migration configuration of acquired metadata configured by a user;
sending a first response message to the client, wherein the first response message comprises a second object and a return request header, and the return request header comprises a target byte stream;
the first preset condition is that the source resource bucket comprises a pre-configured metadata migration rule and is provided with a second object, and the second object is identical to the prefix and/or the suffix of the first object.
As shown in fig. 4, an embodiment of the present application provides a metadata migration method, applied to a target resource bucket, including:
the target resource bucket receives an uploading object request from a client, wherein the uploading object request comprises a setting request header, and the setting request header comprises the target byte stream;
and under the condition that the target resource bucket meets the preset metadata migration rule of the target resource bucket and the uploading object request comprises a set request head, the target resource bucket analyzes the target byte stream and sets metadata corresponding to an object to be acquired.
In the embodiment of the application, the metadata can be configured in the target resource bucket through the mode.
As shown in fig. 5, in an embodiment of the present application, a metadata migration apparatus is provided, which is applied to a client, where the client includes a configuration interface of bucket metadata, and the apparatus includes:
a first sending module 501, configured to send, by the client, an acquire object request to a source resource bucket, where the acquire object request includes a first object and a custom request header configured at the client through a configuration interface of the bucket metadata, where the custom request header includes a migration configuration of acquire metadata configured by a user, where the acquire object request is used to request to acquire metadata of a second object in the source resource bucket and metadata of the second object, where the first object and the second object have the same prefix and/or suffix;
a first receiving module 502, configured to receive, by the client, a first response message from the source resource bucket, where the first response message includes the second object and a return request header, where the return request header includes a target byte stream, where the target byte stream is obtained based on metadata encapsulation corresponding to the second object;
a second sending module 503, configured to send, by the client, an upload object request to a target resource bucket based on the first response message, where the upload object request is a request obtained based on the second object and the target byte stream, and the upload object request includes a setting request header, where the setting request header is used to set metadata of the second object in the target resource bucket.
Optionally, in some embodiments, the apparatus further comprises:
a fourth receiving module, configured to receive, by the client, a second response message from the target resource bucket, where the second response message is a message obtained based on the setting request header;
and the generation module is used for generating a metadata migration success notification according to the second response message by the client.
It should be noted that, the metadata migration apparatus provided in the embodiment of the present application can implement all technical processes of the metadata migration method shown in the embodiment of fig. 1, and achieve the same technical effects, and in order to avoid repetition, a description is omitted here.
The embodiment of the application provides a metadata migration method, which is applied to a source resource bucket, and comprises the following steps:
the second receiving module is used for receiving an object obtaining request from the client by the source resource bucket;
the first acquisition module is used for acquiring metadata corresponding to an object to be acquired according to the self-defined request header and packaging the metadata into a target byte stream under the condition that the source resource bucket meets a first preset condition and the acquired object request comprises the self-defined request header, wherein the self-defined request header comprises migration configuration of acquired metadata configured by a user;
a third sending module, configured to send a first response message to the client, where the first response message includes a second object and a return request header, and the return request header includes a target byte stream;
the first preset condition is that the source resource bucket comprises a pre-configured metadata migration rule and is provided with a second object, and the second object is identical to the prefix and/or the suffix of the first object.
The embodiment of the application provides a metadata migration method, which is applied to a target resource bucket, and comprises the following steps:
a third receiving module, configured to receive, by the target resource bucket, an upload object request from a client, where the upload object request includes a setting request header, and the setting request header includes the target byte stream;
the analyzing module is configured to, when the target resource bucket meets the target resource bucket preconfiguration metadata migration rule and the uploading object request includes a setting request header, analyze the target byte stream and set metadata corresponding to an object to be acquired by the target resource bucket.
The embodiment of the application also provides electronic equipment, which comprises: the program is executed by the processor to implement each process of the method embodiment shown in fig. 1 and achieve the same technical effects, and is not repeated here.
Specifically, referring to fig. 6, the embodiment of the present application further provides an electronic device, including a bus 601, a transceiver 602, an antenna 603, a bus interface 604, a processor 605, and a memory 606.
In this embodiment, the electronic device further includes: a computer program stored on the memory 606 and executable on the processor 605. In the case where the electronic device is a server, the computer program may implement each process of the metadata migration method as shown in the embodiment of fig. 1 when executed by the processor 605, and may achieve the same technical effects, so that repetition is avoided and detailed description is omitted here.
In fig. 6, a bus architecture (represented by bus 601), the bus 601 may include any number of interconnected buses and bridges, with the bus 601 linking together various circuits, including one or more processors, represented by processor 605, and memory, represented by memory 606. The bus 601 may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. Bus interface 604 provides an interface between bus 601 and transceiver 602. The transceiver 602 may be one element or may be multiple elements, such as multiple receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by the processor 605 is transmitted over a wireless medium via an antenna 603, and further, the antenna 603 also receives data and transmits the data to the processor 605.
The processor 605 is responsible for managing the bus 601 and general processing, and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And memory 606 may be used to store data used by processor 605 in performing operations.
Alternatively, the processor 605 may be CPU, ASIC, FPGA or a CPLD.
The embodiment of the present application further provides a computer readable storage medium, on which a computer program is stored, where the computer program when executed by a processor implements each process of the foregoing metadata migration method embodiment, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here. Wherein the computer readable storage medium is such as ROM, RAM, magnetic or optical disk.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), including several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.
The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.
Claims (10)
1. A metadata migration method, applied to a client, the client including a configuration interface for bucket metadata, the method comprising:
the client sends an acquisition object request to a source resource bucket, wherein the acquisition object request comprises a first object and a custom request header configured at the client through a configuration interface of the bucket metadata, the custom request header comprises migration configuration of acquisition metadata configured by a user, the acquisition object request is used for requesting acquisition of metadata of a second object and the second object in the source resource bucket, and the first object and the second object have the same prefix and/or suffix;
the client receives a first response message from the source resource bucket, wherein the first response message comprises the second object and a return request header, the return request header comprises a target byte stream, and the target byte stream is obtained based on metadata encapsulation corresponding to the second object;
the client sends an uploading object request to a target resource bucket based on the first response message, wherein the uploading object request is a request obtained based on the second object and the target byte stream, and the uploading object request comprises a setting request header, and the setting request header is used for setting metadata of the second object in the target resource bucket.
2. The metadata migration method of claim 1, wherein the migration configuration comprises at least one of:
first configuration information, wherein the first configuration information is used for indicating modification time for acquiring the second object;
the second configuration information is used for indicating the storage category of the second object;
third configuration information, wherein the third configuration information is used for indicating to acquire the access right of the second object;
fourth configuration information, wherein the fourth configuration information is used for indicating to acquire multi-version information of the second object;
fifth configuration information, the fifth configuration information is used for indicating to obtain soft link information of the second object;
sixth configuration information, wherein the sixth configuration information is used for indicating to acquire a custom request metadata header of the second object;
seventh configuration information, where the seventh configuration information is used to indicate an additional upload type for obtaining the second object;
eighth configuration information, where the eighth configuration information is used to indicate a storage manner of the second object;
and ninth configuration information, wherein the ninth configuration information is used for indicating to acquire the limited save time of the second object.
3. The metadata migration method of claim 1, wherein after the client sends an upload object request to a target resource bucket, the method further comprises:
the client receives a second response message from the target resource bucket, wherein the second response message is obtained based on the setting request head;
and the client generates a metadata migration success notification according to the second response message.
4. A method of metadata migration, applied to a source resource bucket, the method comprising:
the source resource bucket receives an object acquisition request from a client;
under the condition that the source resource bucket meets a first preset condition and the acquisition object request comprises a custom request header, acquiring metadata corresponding to an object to be acquired according to the custom request header and packaging the metadata into a target byte stream, wherein the custom request header comprises migration configuration of acquired metadata configured by a user;
sending a first response message to the client, wherein the first response message comprises a second object and a return request header, and the return request header comprises a target byte stream;
the first preset condition is that the source resource bucket comprises a pre-configured metadata migration rule and is provided with a second object, and the second object is identical to the prefix and/or the suffix of the first object.
5. A method of metadata migration, applied to a target resource bucket, the method comprising:
the target resource bucket receives an uploading object request from a client, wherein the uploading object request comprises a setting request header, and the setting request header comprises the target byte stream;
and under the condition that the target resource bucket meets the preset metadata migration rule of the target resource bucket and the uploading object request comprises a set request head, the target resource bucket analyzes the target byte stream and sets metadata corresponding to an object to be acquired.
6. A metadata migration apparatus, for application to a client, the client comprising a configuration interface for bucket metadata, the apparatus comprising:
a first sending module, configured to send, by the client, an acquisition object request to a source resource bucket, where the acquisition object request includes a first object and a custom request header configured at the client through a configuration interface of the bucket metadata, where the custom request header includes a migration configuration of acquisition metadata configured by a user, where the acquisition object request is used to request acquisition of metadata of a second object in the source resource bucket and of the second object, where the first object and the second object have the same prefix and/or suffix;
the first receiving module is used for receiving a first response message from the source resource bucket by the client, wherein the first response message comprises the second object and a return request header, the return request header comprises a target byte stream, and the target byte stream is obtained based on metadata encapsulation corresponding to the second object;
the second sending module is configured to send, by the client, an upload object request to a target resource bucket based on the first response message, where the upload object request is a request obtained based on the second object and the target byte stream, and the upload object request includes a setting request header, where the setting request header is used to set metadata of the second object in the target resource bucket.
7. A metadata migration apparatus for use with a source resource bucket, the apparatus comprising:
the second receiving module is used for receiving an object obtaining request from the client by the source resource bucket;
the first acquisition module is used for acquiring metadata corresponding to an object to be acquired according to the self-defined request header and packaging the metadata into a target byte stream under the condition that the source resource bucket meets a first preset condition and the acquired object request comprises the self-defined request header, wherein the self-defined request header comprises migration configuration of acquired metadata configured by a user;
a third sending module, configured to send a first response message to the client, where the first response message includes a second object and a return request header, and the return request header includes a target byte stream;
the first preset condition is that the source resource bucket comprises a pre-configured metadata migration rule and is provided with a second object, and the second object is identical to the prefix and/or the suffix of the first object.
8. A metadata migration apparatus for application to a target resource bucket, the apparatus comprising:
a third receiving module, configured to receive, by the target resource bucket, an upload object request from a client, where the upload object request includes a setting request header, and the setting request header includes the target byte stream;
the analyzing module is configured to, when the target resource bucket meets the target resource bucket preconfiguration metadata migration rule and the uploading object request includes a setting request header, analyze the target byte stream and set metadata corresponding to an object to be acquired by the target resource bucket.
9. An electronic device, comprising: a processor, a memory and a program stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the metadata migration method of any one of claims 1 to 5.
10. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the metadata migration method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311575641.5A CN117714539A (en) | 2023-11-23 | 2023-11-23 | Metadata migration method and device, electronic equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311575641.5A CN117714539A (en) | 2023-11-23 | 2023-11-23 | Metadata migration method and device, electronic equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117714539A true CN117714539A (en) | 2024-03-15 |
Family
ID=90152388
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311575641.5A Pending CN117714539A (en) | 2023-11-23 | 2023-11-23 | Metadata migration method and device, electronic equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117714539A (en) |
-
2023
- 2023-11-23 CN CN202311575641.5A patent/CN117714539A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108021710B (en) | Dynamic interface conversion method, device, terminal equipment and storage medium | |
| US11025724B2 (en) | Transport of control data in proxy-based network communications | |
| CN108712320B (en) | Message pushing method and device | |
| CN109241009B (en) | Method for preventing file from being repeatedly uploaded and control method and device thereof | |
| CN112416396B (en) | Application program updating method and system | |
| CN111124861A (en) | Recording method of webpage data, recording device of webpage data and readable storage medium | |
| CN111369237B (en) | Data processing method and device and computer storage medium | |
| CN110225510A (en) | Method and apparatus for burning embedded SIM card | |
| CN112507005B (en) | Method and device for processing message | |
| CN112422450A (en) | Computer equipment, and flow control method and device for service request | |
| CN106357713A (en) | Remote procedure call realizing method, client side device and server device | |
| CN109542963B (en) | Hospital data processing method and related device based on big data | |
| CN109194706B (en) | Network resource dial testing method and terminal | |
| CN113779422A (en) | Method and device for realizing relation chain label, electronic equipment and storage medium | |
| CN112153146A (en) | Operation notification method and apparatus, storage medium, and electronic apparatus | |
| CN117714539A (en) | Metadata migration method and device, electronic equipment and readable storage medium | |
| CN111278085A (en) | Method and device for acquiring target network | |
| CN113885753A (en) | Information input method and device, terminal equipment and storage medium | |
| CN112000313A (en) | Request response method, device, equipment and storage medium | |
| CN113779122A (en) | Method and apparatus for exporting data | |
| CN112698948A (en) | Method and device for acquiring product resources, storage medium and electronic device | |
| CN112714148A (en) | Interface configuration method, device, equipment and medium | |
| CN113760487A (en) | Service processing method and device | |
| CN110830584A (en) | Access control device, control method, court trial host and readable storage medium | |
| CN110647546A (en) | Third-party rule engine generation method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |