CN113312179A

CN113312179A - Data component management method, device and system, electronic equipment and storage medium

Info

Publication number: CN113312179A
Application number: CN202110610191.3A
Authority: CN
Inventors: 张俊杰; 李晓歌; 门玉森; 王文颖; 杨元; 吕旖旎; 李勃昊; 赵震; 邓罡
Original assignee: China Travelsky Holding Co
Current assignee: China Travelsky Technology Co Ltd; China Travelsky Holding Co
Priority date: 2021-06-01
Filing date: 2021-06-01
Publication date: 2021-08-27

Abstract

The application provides a data component management method, a device, a system, electronic equipment and a storage medium, and the method comprises the steps of receiving a data operation request sent by a service party when the service party logs in a big data platform based on authentication information, wherein the authentication information is generated when the service party applies for a target data acquisition component on a cloud management platform; the target data acquisition component is adopted for data acquisition, and the target data transmission component is utilized for transmitting data to the target data processing component, so that the target data processing component processes the data; backing up target resource information of a target data assembly corresponding to a data assembly offline request sent by a business party, deleting the target resource information, and sending generated offline information to a cloud management platform, wherein the target resource information is generated when the business party applies for the target data assembly on the cloud management platform. The invention can enable a business party to quickly and conveniently apply for and use the data component and achieve the aim of logout and logout of the outdated data component.

Description

Data component management method, device and system, electronic equipment and storage medium

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a method, an apparatus, a system, an electronic device, and a storage medium for managing data components.

Background

With the continuous development of information technology, the world has entered the "big data age" nowadays. Data in each industry field is exponentially increased, and the traditional database cannot meet the requirements of storage, analysis and retrieval of large data quantity at present, so that a plurality of large data assemblies are promoted, and a hadoop ecology is formed.

Therefore, under the conditions of increasing current business requirements and developing the big data field, how to provide a method for a business party to apply for and use big data component resources quickly and conveniently, and to implement logout and logout operations on expired big data component resources is a problem that needs to be solved urgently.

Disclosure of Invention

In view of the above, the present invention provides a method, an apparatus, a system, an electronic device and a storage medium for managing data component resources, so as to achieve the purposes of enabling a business party to quickly and conveniently apply for and use a data component, and logout of an expired data component.

The invention discloses a data component management method in a first aspect, which is applied to a big data platform and comprises the following steps:

receiving a data operation request sent by a service party when the service party logs in the big data platform based on authentication information, wherein the data operation request comprises a target data acquisition component selected by the service party, and the authentication information is generated when the service party applies for the target data acquisition component on a cloud management platform;

acquiring data by using the target data acquisition component, transmitting the data to a target data processing component by using a target data transmission component, and processing the data by using the target data processing component, wherein the target data transmission component is a data transmission component bound with the target data acquisition component, and the target data processing component is a data processing component bound with the target data transmission component;

when a data component offline request sent by the business party is received, backing up target resource information of a target data component corresponding to the data component offline request, deleting the target resource information, and sending generated offline information to the cloud management platform, wherein the target resource information is generated when the business party applies for the target data component on the cloud management platform.

The second aspect of the invention discloses a data component management method, which is applied to a cloud management platform and comprises the following steps:

receiving a project application request sent by a service party to apply for a corresponding data component, wherein the project application request at least comprises a project name, the project name is applied by the service party when applying for the service name, and the data component is a data acquisition component, a data transmission component or a data processing component;

applying for a corresponding data component based on the project name, binding the data component with other data components, and generating authentication information and resource information related to the data component, wherein if the data component is the data acquisition component, the other data components are the data transmission components related to the data acquisition component under the authority of the business party; if the data assembly is the data transmission assembly, the other data assemblies are the data acquisition assembly or the data processing assembly related to the data transmission assembly under the authority of the service party; if the data assembly is the data processing assembly, the other data assemblies are the data transmission assemblies related to the data processing assembly under the authority of the service party;

and sending the authentication information and the resource information to a big data platform, and returning the authentication information and the resource information to the service party, so that the service party logs in the big data platform based on the authentication information to perform data operation on the data component.

The third aspect of the present invention discloses a data component management device, which is applied to a big data platform, and the device comprises:

the system comprises a first receiving unit, a second receiving unit and a data processing unit, wherein the first receiving unit is used for receiving a data operation request sent by a service party when the service party logs in the big data platform based on authentication information, the data operation request comprises a target data acquisition component selected by the service party, and the authentication information is generated when the service party applies for the data acquisition component on a cloud management platform;

the processing unit is used for acquiring data by adopting the target data acquisition component, transmitting the data to a target data processing component by utilizing a target data transmission component and processing the data by the target data processing component, wherein the target data transmission component is a data transmission component bound with the target data acquisition component, and the target data processing component is a data processing component bound with the target data transmission component;

the first offline unit is used for backing up target resource information of a target data assembly corresponding to the data assembly offline request, deleting the target resource information and sending generated offline information to the cloud management platform when the data assembly offline request sent by the business party is received, wherein the target resource information is generated when the business party applies for the target data assembly on the cloud management platform.

The fourth aspect of the present invention discloses a data component management apparatus, which is applied to a cloud management platform, and the apparatus includes:

the second receiving unit is used for receiving a project application request sent by a service party and applying for a corresponding data component, wherein the project application request at least comprises a project name, the project name is applied by the service party when applying for the service name, and the data component is a data acquisition component, a data transmission component or a data processing component;

an application unit, configured to apply for a corresponding data component based on the project name, bind the data component with other data components, and generate authentication information and resource information related to the data component, where if the data component is the data acquisition component, the other data components are the data transmission components related to the data acquisition component under the authority of the service provider; if the data assembly is the data transmission assembly, the other data assemblies are the data acquisition assembly or the data processing assembly related to the data transmission assembly under the authority of the service party; if the data assembly is the data processing assembly, the other data assemblies are the data transmission assemblies related to the data processing assembly under the authority of the service party;

and the sending unit is used for sending the authentication information and the resource information to a big data platform, returning the authentication information and the resource information to the service party, and enabling the service party to log in the big data platform based on the authentication information to perform data operation on the data assembly.

A fifth aspect of the present invention discloses a data component management system, the system comprising:

the cloud management platform is used for receiving a project application request sent by a service party and applying for a corresponding data component; applying for a corresponding data component based on the project name, binding the data component with other data components, and generating authentication information and resource information related to the data component; sending the authentication information and the resource information to a big data platform, and returning the authentication information and the resource information to the service party, so that the service party logs in the big data platform based on the authentication information to perform data operation on the data component;

the project application request at least comprises a project name, the project name is applied by the service party when applying for the service name, the data component is a data acquisition component, a data transmission component or a data processing component, and if the data component is the data acquisition component, the other data components are the data transmission components related to the data acquisition component under the authority of the service party; if the data assembly is the data transmission assembly, the other data assemblies are the data acquisition assembly or the data processing assembly related to the data transmission assembly under the authority of the service party; if the data assembly is the data processing assembly, the other data assemblies are the data transmission assemblies related to the data processing assembly under the authority of the service party;

the big data platform is used for receiving a data operation request sent by the service party when logging in the big data platform based on the authentication information; acquiring data by using the target data acquisition component, and transmitting the data to a target data processing component by using a target data transmission component so that the target data processing component processes the data; when a data component offline request sent by the service party is received, backing up target resource information of a target data component corresponding to the data component downloading request, deleting the target resource information, and sending the generated offline information to the cloud management platform, wherein the data operation request comprises the authentication information of the target data acquisition component selected by the service party, the authentication information is generated when the service party applies for the target data acquisition component on the cloud management platform, the target data transmission component is a data transmission component bound with the target data acquisition component, the target data processing component is a data processing component bound to the target data transmission component, the target resource information is generated when the business party applies for the target data component on the cloud management platform.

A sixth aspect of the present invention discloses an electronic apparatus, comprising: the system comprises a processor and a memory, wherein the processor and the memory are connected through a communication bus; the processor is used for calling and executing the program stored in the memory; the memory is configured to store a program for implementing the data component management method disclosed in the first aspect of the present invention or implementing the data component management method disclosed in the second aspect of the present invention.

A seventh aspect of the present invention discloses a computer-readable storage medium, in which computer-executable instructions are stored, the computer-executable instructions being configured to execute the data component management method disclosed in the first aspect of the present invention or execute the data component management method disclosed in the second aspect of the present invention.

The invention provides a data component management method, a device, a system, electronic equipment and a storage medium, wherein when a cloud management platform receives a project application request sent by a business party, the cloud management platform applies for a corresponding data component for the business party based on the project application request, binds the applied data component with other data components related to the data component under the authority of the business party, and generates authentication information and resource information related to the data component so as to send the authentication information and the resource information related to the data component to the business party and a big data platform; when the big data platform receives a data operation request sent by a service party when logging in the big data platform based on authentication information, a target data acquisition component corresponding to the data operation request is adopted for data acquisition, a target data transmission component bound with the target data acquisition component is adopted for transmitting acquired data to a target data processing component bound with the target data transmission component, and the target data processing component processes the data; when a data assembly offline request sent by a service party is received, backing up target resource information of a target data assembly corresponding to the data assembly offline request, deleting the target resource information, sending the generated offline information to a cloud management platform, and informing the cloud management platform that the target data assembly is offline. Based on the technical scheme provided by the invention, a business party can apply for the corresponding data component through the cloud management platform, and after the application is successful, the business party logs in the big data platform based on the authentication information which is fed back by the cloud management platform and is related to the applied data component, so that the applied data component or the offline corresponding data component can be used on the big data platform.

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, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.

The above and other features, advantages and aspects of the disclosed embodiments will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale.

Fig. 1 is a schematic flowchart of a data component management method according to an embodiment of the present invention;

FIG. 2 is a flowchart illustrating another data component management method according to an embodiment of the present invention;

FIG. 3 is a flowchart illustrating another data component management method according to an embodiment of the present invention;

fig. 4 is a schematic structural diagram of a data component management apparatus according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of another data component management apparatus according to an embodiment of the present invention

FIG. 6 is a schematic structural diagram of a data component management system according to an embodiment of the present invention;

fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.

Detailed Description

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure.

The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.

It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules, or units, and are not used for limiting the order or interdependence of the functions performed by the devices, modules, or units.

It is noted that references to "a", "an", and "the" modifications in the disclosure are exemplary rather than limiting, and that those skilled in the art will understand that "one or more" unless the context clearly dictates otherwise.

Referring to fig. 1, a schematic flow chart of a data component management method provided in an embodiment of the present invention is shown, where the data component management method specifically includes the following steps:

s101: and the business party sends a project application request to the cloud management platform, wherein the project application request at least comprises a project name, and the project name is applied by the business party when applying for the business name.

In the specific process of executing step S101, before the service party sends the project application request to the cloud management platform, the service party may send a service application to the cloud management platform, and after receiving the service application sent by the service party, the cloud management platform may apply for a corresponding service according to the service name of the received service application. After applying for the service, the service party can send a project application request to the cloud management platform under the applied service.

It should be noted that the project application request includes a project requested by the service party, one project corresponds to one data component, and the data component may be a data acquisition component, a data transmission component, a data processing component, a data storage component, or a data presentation component.

The data acquisition component can be a flash data acquisition component, a filebed data acquisition component, a logstash data acquisition component and the like, and the flash data acquisition component mainly realizes data acquisition, aggregation, movement and the like of a service scene; the Filebeat data acquisition component mainly monitors a log directory or a specified directory, tracks and reads a specified directory file; the logstack data acquisition component mainly realizes data acquisition and conversion from multiple sources.

The data transmission component can be a Kafka (SCRAM) data transmission component, a Kafka (PLAN) data transmission component, a Kafka (KERBEROS) data transmission component and the like, the Kafka (SCRAM) data transmission component does not support the transmission of data acquired by the Filebeat data acquisition component and supports the transmission of data acquired by the Flume data acquisition component and the logstack data acquisition component; kafka (PLAN) data transmission component only supports the transmission of data collected by the Filebeat data collection component; the Kafka (KERBEROS) data transmission component supports the transmission of data collected by any data collection component, but the configuration is complex.

The data processing component can be a Storm data processing component, a Spark data processing component and a Flink data processing component, and all the three data processing components can process data transmitted by any data transmission book.

The data storage component can be a Hadoop data storage component, an HBase data storage component, a Hive data storage component, and the like, and the three data storage components can store data transmitted by any data transmission component. The Hadoop data storage assembly comprises a Yarn data storage assembly and an HDFS data storage assembly.

The data display component can be a Kibana data display component, a Kibana data display component and the like, and the two data display components can display data transmitted by any data transmission component.

It should be further noted that, the service party may further add a project principal, a maintenance principal, a resource type corresponding to the requested project, a resource id corresponding to the requested project, a user name, and a corresponding password to the project application request, so that after applying for the corresponding data component, authentication information related to the data component is generated according to the user name and the password, and the generated authentication information is sent to the project principal and the big data platform.

S102: the cloud management platform applies for a corresponding data component based on a project name in a project application request sent by a service party, binds the data component with other data components, and generates authentication information and resource information related to the data component.

In the specific execution process of step S102, after receiving a project application request sent by a service party, the cloud management platform applies for a corresponding data component based on a project name in the project application request, binds the applied data component with other data components related to the data component under the authority of the service party in a code form, and generates authentication information and resource information related to the data component.

In the embodiment of the application, the cloud management platform may generate authentication information according to a user name and a password in the project application request, and generate corresponding resource information according to a resource type and a resource id corresponding to a data component corresponding to the requested project and a work order number of the cloud management platform.

In the application embodiment, if the item application request sent by the service party requests the Flink data processing component, before the Flink data processing component is applied, the Yarn data storage component needs to be applied first, and after the Yarn data storage component is successfully applied, the Flink data processing component needs to be applied. The application process of the Yarn data storage component and the Flink data processing component can be referred to the data component application process, and is not described herein again.

It should be noted that, if the data component is a data acquisition component, the other data components are data transmission components related to the data acquisition component under the authority of the service party; if the data assembly is a data transmission assembly, other data assemblies are a data acquisition assembly, a data processing assembly, a data storage assembly or a data display assembly which are related to the data transmission assembly under the authority of the service party; if the data assembly is a data processing assembly, other data assemblies are data transmission assemblies related to the data processing assembly under the authority of the service party; if the data component is a data storage component, the other data components are data transmission components related to the data storage component under the authority of the service party; and if the data assembly is the data display assembly, the other data assemblies are data transmission assemblies related to the data display assembly under the authority of the business party.

For example, the data component requested by the project application request sent by the service party is a kafka (plan) data transmission component, and the data components under the authority of the service party are a Filebeat data collection component, a logstack data collection component and a Flink data processing component. When receiving a project application request sent by a service party, applying a Kafka (PLAN) data transmission component for the service party based on the project application request, binding the Kafka (PLAN) data transmission component with a Filebeat data acquisition component and a Flink data processing component respectively in a code form, and generating authentication information and resource information related to the Kafka (PLAN) data transmission component based on the received project application request so as to send the generated authentication information and resource information to a project principal and the service party indicated in the project application request.

S103: and the cloud management platform returns the authentication information and the resource information to the service party.

In the specific execution process of S103, after the cloud management platform applies for a corresponding data component based on a project name in a project application request sent by a service party and generates authentication information and resource information related to the data component, the cloud management platform may send a big data platform website, the authentication information, and the resource information to the service party or a project principal in the project application request by calling a big data platform interface, so that the service party or the project principal logs in the big data platform through the big data platform website and the authentication information and uses the corresponding data component or a corresponding data component that is offline.

S104: and the cloud management platform sends the authentication information and the resource information to the big data platform.

In the specific execution process of S104, after the cloud management platform applies for the corresponding data component based on the project name in the project application request sent by the service party and generates the authentication information and the resource information related to the data component, the cloud management platform may synchronize the authentication information and the resource information to the big data platform by calling the big data platform interface, so that the big data platform stores the authentication information and the resource information related to the data component in the master library.

S105: and the service party logs in the big data platform based on the authentication information and then sends a data operation request to the big data platform, wherein the data operation request comprises a target data acquisition component selected by the service party.

In the process of specifically executing step S105, the service party may log in the big data platform through the user name and the password in the authentication information corresponding to the data acquisition component that is desired to be used, may select the data acquisition component corresponding to the authentication information to perform data acquisition after logging in the big data platform successfully, and may send the data operation request by clicking the selected data acquisition component after the service party determines the selected data acquisition component.

It should be noted that, after the service party successfully logs in the big data platform based on the authentication information, the service party may select a data transmission component, a data storage component or a data display component corresponding to the authentication information, which the service party wants to use.

S106: the big data platform adopts the target data acquisition assembly to acquire data and utilizes the target data transmission assembly to transmit the data to the target data processing assembly, so that the target data processing assembly processes the data, wherein the target data transmission assembly is a data transmission assembly bound with the target data acquisition assembly, and the target data processing assembly is a data processing assembly bound with the target data transmission assembly.

In the specific process of executing step S106, after receiving the data operation request sent by the service party, the big data platform may use a data acquisition component corresponding to the data operation request (for convenience of distinguishing, the data acquisition component corresponding to the data operation request is referred to as a target data acquisition component) to acquire corresponding data.

After the corresponding data is collected, the data transmission component bound with the target data collection component (for distinguishing at the same time, the data transmission component bound with the target data collection component is called a target data transmission component) is further utilized to transmit the collected data to the data processing component bound with the target data transmission component (for distinguishing at the same time, the data processing component bound with the target data transmission component is called a target data processing component), so that the target data processing component processes the received data.

In this embodiment of the application, after the target data processing component processes the received data, the processed data may be further transmitted to a data storage component bound to the target data transmission component for data storage through the target data transmission component, or transmitted to a data presentation component bound to the target data transmission component for data presentation.

S107: and the business side sends a data component offline request to the big data platform, wherein the data component offline request comprises a target data component requesting offline.

In the specific process of executing step S107, when the business direction offline the previously applied data component, it may log in the big data platform through the corresponding authentication information, and click the data component that wants to be offline on the big data platform (for convenience of distinguishing, the data component that wants to be offline that is clicked on the big data platform is referred to as a target data component).

S108: and backing up the target resource information of the target data assembly corresponding to the data assembly offline request by the big data platform, and deleting the target resource information.

In the specific process of executing the step S108, a preset data table is preset, and the preset data table is preset in a standby database of the big data platform; when the big data platform receives a data assembly offline request sent by a service party, backing up target resource information related to a target data assembly into a preset data table, setting the request type of the target data assembly in the preset data table as an offline type, and deleting the target resource information corresponding to the target data assembly in the master library.

In the embodiment of the application, after the target resource information related to the target data component is backed up to the preset data table, the preset data table in the standby library is locked, so that before the locking time reaches the preset time, if a business party wants to recover the resource information of the target data component, the target resource information in the standby library can be recovered to the main library, the request type of the target data component in the preset data table of the standby library is modified into the offline type, and the automatic scanning program is cancelled. When the locking time reaches the preset time, if a user recovery request is not received, automatically scanning the preset data table, modifying the request type of the target data assembly into offline, acquiring the work order number of the cloud management platform corresponding to the target data assembly from the target resource management information of the target data assembly, generating offline information corresponding to the target data assembly, and sending the generated offline information to the cloud management platform corresponding to the work order number of the cloud management platform so as to inform the cloud management platform that the target data assembly is offline.

It should be noted that the preset time may be 7 days. The method can be set according to practical application, and the embodiment of the application is not limited.

It should be noted that, if the target resource information includes the service generation data, the locking time of the service generation data in the target resource information in the preset data table in the backup repository may be further set to 3 months. The method can be set according to practical application, and the embodiment of the application is not limited.

In this embodiment of the application, if the target data component corresponding to the data component offline request is a Flink data processing component, the way for the big data platform to backup the target resource information of the target data component corresponding to the data component offline request may be: judging whether the big data platform has running operation currently; if the large data platform does not have the operation currently, backing up the target resource information of the Flink data processing assembly into a preset data table, and deleting the target resource information of the Flink data processing assembly in the main library; if the large data platform has the currently running operation, after the currently running operation is deleted, backing up the target resource information of the Flink data processing assembly into a preset data table, and deleting the target resource information of the Flink data processing assembly in the main library.

And locking the preset data table in the standby database, so that if the service party wants to recover the resource information of the Flink data processing assembly before the locking time reaches the preset time, the resource information of the Flink data processing assembly in the standby database can be recovered to the main database. When the locking time reaches the preset time, if a user recovery request is not received, scanning a preset data table, modifying the request type of the Flink data processing assembly into offline, acquiring the work order number of the cloud management platform corresponding to the target data assembly from the target resource management information of the Flink data processing assembly, generating offline information corresponding to the Flink data processing assembly, and sending the generated offline information to the cloud management platform corresponding to the work order number of the cloud management platform so as to inform the cloud management platform that the Flink data processing assembly is offline.

In this embodiment of the application, if the target data component corresponding to the data component offline request is a Hadoop data processing component, the way for the big data platform to backup the target resource information of the target data component corresponding to the data component offline request may be: judging whether a business party applies for a Flink data processing component or not; if the business side applies for the Flink data processing assembly, after offline processing is carried out on the Flink data processing assembly, adding a preset field in a directory name corresponding to the Hadoop data storage assembly; deleting the Yarn data storage assembly in the Hadoop data storage assembly, backing up the resource information of the Hadoop data storage assembly with the Yarn data storage assembly deleted to a preset data table, and deleting the resource information of the Hadoop data storage assembly with the Yarn data storage assembly deleted in the main library.

If the business side does not apply for the Flank data processing assembly, a preset field can be directly added to the directory name corresponding to the Hadoop data storage assembly, the Yarn data storage assembly in the Hadoop data storage assembly is deleted, the resource information of the Hadoop data storage assembly with the Yarn data storage assembly deleted is backed up to a preset data table, and the resource information of the Hadoop data storage assembly with the Yarn data storage assembly deleted in the main library is deleted.

And locking the preset data table in the standby library, so that if the service party wants to recover the resource information of the Hadoop data storage component before the locking time reaches the preset time, the resource information of the Hadoop data storage component in the standby library can be recovered to the main library. When the locking time reaches the preset time, if a user recovery request is not received, scanning a preset data table, modifying the request type of the Hadoop data storage assembly into offline, acquiring a work order number of a cloud management platform corresponding to the target data assembly from target resource management information of the Hadoop data storage assembly, generating offline information corresponding to the Hadoop data storage assembly, and sending the generated offline information to the cloud management platform corresponding to the work order number of the cloud management platform so as to inform the cloud management platform that the Hadoop data storage assembly is offline.

It should be noted that the default field may be "_ DEL". The method can be set according to practical application, and the embodiment of the application is not limited.

In this embodiment of the present application, if the target data component corresponding to the data component offline request is an HBase data storage component, the way for the big data platform to backup the target resource information of the target data component corresponding to the data component offline request may be: recovering the namespace authority of the HBase data storage component and recovering the namespace authority of the service party to the HBase data storage component; and backing up the resource information of the HBase data storage assembly to a preset data table, and deleting the resource information of the HBase data storage assembly in the main library.

And locking the preset data table in the standby library, so that if the service party wants to recover the resource information of the HBase data storage component before the locking time reaches the preset time, the resource information of the HBase data storage component in the standby library can be recovered to the main library. When the locking time reaches the preset time, if a user recovery request is not received, scanning a preset data table, modifying the request type of the HBase data storage assembly into offline, acquiring a work order number of a cloud management platform corresponding to the target data assembly from target resource management information of the HBase data storage assembly, generating offline information corresponding to the HBase data storage assembly, and sending the generated offline information to the cloud management platform corresponding to the work order number of the cloud management platform so as to inform the cloud management platform that the HBase data storage assembly is offline.

S109: and sending the generated offline information to the cloud management platform.

In the specific process of executing step S109, the big data platform backs up the target resource information of the target data component corresponding to the data component offline request, deletes the target resource information, obtains the work order number of the cloud management platform corresponding to the target data component from the target resource management information of the target data component in the preset data table of the backup library, generates offline information corresponding to the target data component, and sends the generated offline information to the cloud management platform corresponding to the work order number of the cloud management platform, so as to notify the cloud management platform that the target data component has been offline.

The invention provides a data component management method, when a cloud management platform receives a project application request sent by a service party, a corresponding data component is applied for the service party based on the project application request, the applied data component is bound with other data components related to the data component under the authority of the service party, and authentication information and resource information related to the data component are generated so as to send the authentication information and the resource information related to the data component to the service party and a big data platform; when the big data platform receives a data operation request sent by a service party when logging in the big data platform based on authentication information, a target data acquisition component corresponding to the data operation request is adopted for data acquisition, a target data transmission component bound with the target data acquisition component is adopted for transmitting acquired data to a target data processing component bound with the target data transmission component, and the target data processing component processes the data; when a data assembly offline request sent by a service party is received, backing up target resource information of a target data assembly corresponding to the data assembly offline request, deleting the target resource information, sending the generated offline information to a cloud management platform, and informing the cloud management platform that the target data assembly is offline. Based on the technical scheme provided by the invention, a business party can apply for the corresponding data component through the cloud management platform, and after the application is successful, the business party logs in the big data platform based on the authentication information which is fed back by the cloud management platform and is related to the applied data component, so that the applied data component or the offline corresponding data component can be used on the big data platform.

The data component management method provided by the embodiment of the invention is introduced from the perspective of a big data platform and a cloud management platform respectively.

Referring to fig. 2, a schematic flow chart of another data component management method provided in the embodiment of the present invention is shown, where the information transmission method is applied to a cloud management platform, and specifically includes the following steps:

s201: receiving a project application request sent by a service party to apply for a corresponding data component, wherein the project application request at least comprises a project name, the project name is applied by the service party when applying for the service name, and the data component is a data acquisition component, a data transmission component or a data processing component.

In the specific process of executing step S201, before the service party sends the project application request to the cloud management platform, the service party may send a service application to the cloud management platform, and after receiving the service application sent by the service party, the cloud management platform may apply for a corresponding service according to the service name of the received service application. After applying for the service, the service party can send a project application request to the cloud management platform under the applied service.

S202: and applying for a corresponding data assembly based on the project name, binding the data assembly with other data assemblies, and generating authentication information and resource information related to the data assembly.

In the specific execution process of step S202, after receiving a project application request sent by a service party, the cloud management platform applies for a corresponding data component based on a project name in the project application request, binds the applied data component with other data components related to the data component under the authority of the service party in a code form, and generates authentication information and resource information related to the data component.

S203: and sending the authentication information and the resource information to the big data platform, and returning the authentication information and the resource information to the service party, so that the service party logs in the big data platform based on the authentication information to perform data operation on the data assembly.

In the specific process of step S203, after the cloud management platform applies for a corresponding data component based on a project name in a project application request sent by a service party and generates authentication information and resource information related to the data component, the cloud management platform may send a big data platform website, authentication information, and resource information to a service party or a project principal, a service party, and a big data platform in the project application request by calling a big data platform interface, so that the service party or the project principal logs in the big data platform through the big data platform website and the authentication information, uses the corresponding data component or the offline corresponding data component, and so that the big data platform stores the authentication information and the resource information related to the data component into a master library.

The specific process of using the corresponding data component or offline corresponding data component may refer to steps S105 to S109 disclosed in fig. 1 of the embodiment of the present invention, and details thereof are not repeated here.

The invention provides a data component management method, when a cloud management platform receives a project application request sent by a service party, a corresponding data component is applied for the service party based on the project application request, the applied data component is bound with other data components related to the data component under the authority of the service party, and authentication information and resource information related to the data component are generated so as to send the authentication information and the resource information related to the data component to the service party and a big data platform; after the data component is successfully applied, the business party can log in the big data platform based on the authentication information which is fed back by the cloud management platform and is related to the applied data component, so that the applied data component or the corresponding offline data component can be used on the big data platform. Based on the technical scheme provided by the invention, a business party can apply for the corresponding data component through the cloud management platform, and after the application is successful, the business party logs in the big data platform based on the authentication information which is fed back by the cloud management platform and is related to the applied data component, so that the applied data component or the offline corresponding data component can be used on the big data platform.

Referring to fig. 3, a schematic flow chart of another data component management method provided in the embodiment of the present invention is shown, where the data component management method is applied to a big data platform, and specifically includes the following steps:

s301: and receiving a data operation request sent by a service party when the service party logs in the big data platform based on authentication information, wherein the data operation request comprises a target data acquisition component selected by the service party, and the authentication information is generated when the service party applies for the target data acquisition component on the cloud management platform.

In the process of specifically executing step S301, the service party may log in the big data platform through the user name and the password in the authentication information corresponding to the data acquisition component that is desired to be used, may select the data acquisition component corresponding to the authentication information to perform data acquisition after logging in the big data platform successfully, and may send the data operation request by clicking the selected data acquisition component after the service party determines the selected data acquisition component.

In this embodiment of the present application, the specific process of the business party generating the corresponding authentication information when the cloud management platform generates the data component corresponding to the application item, and the specific process of the business party generating the corresponding authentication information when the cloud management platform generates the data component corresponding to the application item may be referred to the data component management method disclosed in fig. 3 in the embodiment of the present invention, which is not described herein again.

S302: and the target data acquisition component is adopted for data acquisition, and the target data transmission component is utilized for transmitting the data to the target data processing component, so that the target data processing component processes the data.

In the specific process of performing step S302, after receiving a data operation request sent by a service party based on authentication information, the big data platform may collect corresponding data by using a data collection component corresponding to the data operation request (for convenience of distinguishing, the data collection component corresponding to the data operation request is referred to as a target data collection component).

S303: when a data assembly offline request sent by a business party is received, backing up target resource information of a target data assembly corresponding to the data assembly offline request, deleting the target resource information, and sending the generated offline information to a cloud management platform, wherein the target resource information is generated when the business party applies for the target data assembly on the cloud management platform.

In the specific process of executing the step S303, a preset data table is preset, and the preset data table is preset in a standby database of the big data platform; when the big data platform receives a data assembly offline request sent by a service party, backing up target resource information related to a target data assembly into a preset data table, setting the request type of the target data assembly in the preset data table as an offline type, and deleting the target resource information corresponding to the target data assembly in the master library.

And locking the preset data table in the standby database, so that if the service party wants to recover the resource information of the target data assembly before the locking time reaches the preset time, the target resource information in the standby database can be recovered into the main database, the request type of the target data assembly in the preset data table of the standby database is modified into the offline type, and the automatic scanning program is cancelled. When the locking time reaches the preset time, if a user recovery request is not received, automatically scanning the preset data table, modifying the request type of the target data assembly into offline, acquiring the work order number of the cloud management platform corresponding to the target data assembly from the target resource management information of the target data assembly, generating offline information corresponding to the target data assembly, and sending the generated offline information to the cloud management platform corresponding to the work order number of the cloud management platform so as to inform the cloud management platform that the target data assembly is offline.

In this embodiment of the present application, the target resource information is generated when the service party applies for the target data component on the cloud management platform, and a specific process of generating corresponding resource information when the service party applies for the target data component on the cloud management platform may refer to the data component management method disclosed in fig. 3 in the embodiment of the present invention, which is not described herein again.

The invention provides a data component management method.A service party can log in a big data platform based on authentication information corresponding to a data component fed back by a cloud management platform after the data component application is successfully carried out on the cloud management platform; when the big data platform receives a data operation request sent by a service party when logging in the big data platform based on authentication information, a target data acquisition component corresponding to the data operation request is adopted for data acquisition, a target data transmission component bound with the target data acquisition component is adopted for transmitting acquired data to a target data processing component bound with the target data transmission component, and the target data processing component processes the data; when a data assembly offline request sent by a service party is received, backing up target resource information of a target data assembly corresponding to the data assembly offline request, deleting the target resource information, sending the generated offline information to a cloud management platform, and informing the cloud management platform that the target data assembly is offline. Based on the technical scheme provided by the invention, a business party applies for a corresponding data component on a cloud management platform, and after the application is successful, the business party can log in a big data platform based on authentication information which is fed back by the cloud management platform and is related to the applied data component, so that the applied data component or the offline corresponding data component can be used on the big data platform.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.

The names of messages or information exchanged between devices in the disclosed embodiments are for illustrative purposes only and are not intended to limit the scope of such messages or information.

Although the operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous.

It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.

Computer program code for carrying out operations for the disclosed invention may be written in any combination of one or more programming languages, including but not limited to an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

Corresponding to the data component management method disclosed in the above embodiment of the present invention, referring to fig. 4, an embodiment of the present invention further provides a schematic structural diagram of a data component management apparatus, where the data component management apparatus is applied to a big data platform, and the data component management apparatus includes:

the first receiving unit 41 is configured to receive a data operation request sent by a service party when logging in a big data platform based on authentication information, where the data operation request includes a target data acquisition component selected by the service party, and the authentication information is generated when the service party applies for the target data component on a cloud management platform;

the processing unit 42 is configured to acquire data by using a target data acquisition component, and transmit the data to a target data processing component by using a target data transmission component, so that the target data processing component processes the data, where the target data transmission component is a data transmission component bound to the target data acquisition component, and the target data processing component is a data processing component bound to the target data transmission component;

the first offline unit 43, when receiving a data component offline request sent by a service party, backs up target resource information of a target data component corresponding to the data component offline request, deletes the target resource information, and sends generated offline information to the cloud management platform, where the target resource information is generated when the service party applies for the target data component on the cloud management platform.

The specific principle and the execution process of each unit in the data component management apparatus disclosed in the above embodiment of the present invention are the same as those of the data component management method disclosed in the above embodiment of fig. 3 of the present invention, and reference may be made to corresponding parts in the data component management method disclosed in the above embodiment of fig. 3 of the present invention, and details are not described here again.

The invention provides a data component management device.A service party can log in a big data platform based on authentication information corresponding to a data component fed back by a cloud management platform after the data component application is successfully carried out on the cloud management platform; when the big data platform receives a data operation request sent by a service party when logging in the big data platform based on authentication information, a target data acquisition component corresponding to the data operation request is adopted for data acquisition, a target data transmission component bound with the target data acquisition component is adopted for transmitting acquired data to a target data processing component bound with the target data transmission component, and the target data processing component processes the data; when a data assembly offline request sent by a service party is received, backing up target resource information of a target data assembly corresponding to the data assembly offline request, deleting the target resource information, sending the generated offline information to a cloud management platform, and informing the cloud management platform that the target data assembly is offline. Based on the technical scheme provided by the invention, a business party applies for a corresponding data component on a cloud management platform, and after the application is successful, the business party can log in a big data platform based on authentication information which is fed back by the cloud management platform and is related to the applied data component, so that the applied data component or the offline corresponding data component can be used on the big data platform.

Optionally, the first offline unit includes:

the third receiving unit is used for receiving a data component offline request sent by a service party, wherein the data component offline request comprises a target data component requesting offline;

the first backup unit is used for backing up target resource information of a target data assembly into a preset data table and setting a request type of the target data assembly in the preset data table as an offline type, wherein the preset data table is preset in a standby library of the big data platform;

the locking unit is used for deleting the target resource information and locking the target resource information in the preset data table;

and the offline information sending unit is used for setting the request type of the target data assembly in the preset data table as offline when the locking time reaches the preset time, and sending the generated offline information to the cloud management platform.

Optionally, the first offline unit includes:

the system comprises a first judging unit, a second judging unit and a third judging unit, wherein the first judging unit is used for judging whether the running operation exists in the big data platform at present when receiving a offline request of a Flink data processing assembly sent by a service party;

the second backup unit is used for backing up the target resource information of the Flink data processing assembly into a preset data table and deleting the target resource information of the Flink data processing assembly if the large data platform does not have the operation currently;

the third backup unit is used for deleting the currently running job if the currently running job exists in the big data platform, backing up the target resource information of the Flink data processing assembly into the preset data table, and deleting the target resource information of the Flink data processing assembly;

accordingly, the method can be used for solving the problems that,

the second judgment unit is used for judging whether the business party applies for the Flink data processing component or not when receiving a Hadoop data storage component offline request sent by the business party;

the second offline unit is used for performing offline processing on the Flink data processing assembly if the business party applies for the Flink data processing assembly;

the fourth backup unit is used for adding a preset field to the directory name corresponding to the Hadoop data storage assembly, deleting the Yarn data storage assembly in the Hadoop data storage assembly, backing up the target resource information of the Hadoop data storage assembly with the Yarn data storage assembly deleted to a preset data table and deleting the target resource information;

and the fifth backup unit is used for adding a preset field to the directory name corresponding to the Hadoop data storage assembly if the business party does not apply for the Flank data processing assembly, deleting the Yarn data storage assembly in the Hadoop data storage assembly, backing up the target resource information of the Hadoop data storage assembly with the Yarn data storage assembly deleted to a preset data table and deleting the target resource information.

Optionally, the first offline unit includes:

the recovery unit is used for recovering the namespace authority of the HBase data storage assembly and recovering the namespace authority of the HBase data storage assembly by the service party when receiving an HBase data storage assembly offline request sent by the service party;

and the sixth backup unit is used for backing up the target resource information of the HBase data storage assembly into the preset data table and deleting the target resource information of the HBase data storage assembly.

Corresponding to the data component management method disclosed in the embodiment of the present invention, referring to fig. 5, an embodiment of the present invention further provides a schematic structural diagram of a data component management apparatus, where the data component management apparatus is applied to a cloud management platform, and the data component management apparatus includes:

the second receiving unit 51 is configured to receive a project application request sent by a service party to apply for a corresponding data component, where the project application request at least includes a project name, the project name is applied by the service party when applying for the service name, and the data component is a data acquisition component, a data transmission component, or a data processing component;

the application unit 52 is configured to apply for a corresponding data component based on the project name, bind the data component with other data components, and generate authentication information and resource information related to the data component, where if the data component is a data acquisition component, the other data components are data transmission components related to the data acquisition component under the authority of a service party; if the data assembly is a data transmission assembly, other data assemblies are data acquisition assemblies or data processing assemblies related to the data transmission assembly under the authority of the service party; if the data assembly is a data processing assembly, other data assemblies are data transmission assemblies related to the data processing assembly under the authority of the service party;

and the sending unit 53 is configured to send the authentication information and the resource information to the big data platform, and return the authentication information and the resource information to the service party, so that the service party logs in the big data platform based on the authentication information to perform data operation on the data component.

The specific principle and the execution process of each unit in the data component management apparatus disclosed in the above embodiment of the present invention are the same as those of the data component management method disclosed in the above embodiment of fig. 2 of the present invention, and reference may be made to corresponding parts in the data component management method disclosed in the above embodiment of fig. 2 of the present invention, and details are not described here again.

The invention provides a data component management device, when a cloud management platform receives a project application request sent by a service party, a corresponding data component is applied for the service party based on the project application request, the applied data component is bound with other data components related to the data component under the authority of the service party, and authentication information and resource information related to the data component are generated so as to send the authentication information and the resource information related to the data component to the service party and a big data platform; after the data component is successfully applied, the business party can log in the big data platform based on the authentication information which is fed back by the cloud management platform and is related to the applied data component, so that the applied data component or the corresponding offline data component can be used on the big data platform. Based on the technical scheme provided by the invention, a business party can apply for the corresponding data component through the cloud management platform, and after the application is successful, the business party logs in the big data platform based on the authentication information which is fed back by the cloud management platform and is related to the applied data component, so that the applied data component or the offline corresponding data component can be used on the big data platform.

Corresponding to the data component management method disclosed in the embodiment of the present invention, referring to fig. 6, an embodiment of the present invention further provides a schematic structural diagram of a data component management system, where the data component management system includes:

the cloud management platform 61 is used for receiving a project application request sent by a service party and applying for a corresponding data component; applying for a corresponding data component based on the project name, binding the data component with other data components, and generating authentication information and resource information related to the data component; sending the authentication information and the resource information to the big data platform, and returning the authentication information and the resource information to the service party, so that the service party logs in the big data platform based on the authentication information to perform data operation on the data assembly;

the project application request at least comprises a project name, the project name is applied by a service party when the service name is applied, the data component is a data acquisition component, a data transmission component or a data processing component, and if the data component is the data acquisition component, other data components are data transmission components related to the data acquisition component under the authority of the service party; if the data assembly is a data transmission assembly, other data assemblies are data acquisition assemblies or data processing assemblies related to the data transmission assembly under the authority of the service party; if the data assembly is a data processing assembly, other data assemblies are data transmission assemblies related to the data processing assembly under the authority of the service party;

the big data platform 62 is used for receiving a data operation request sent by a service party when logging in the big data platform based on the authentication information; the target data acquisition component is adopted for data acquisition, and the target data transmission component is utilized for transmitting data to the target data processing component, so that the target data processing component processes the data; when a data component offline request sent by a business party is received, backing up target resource information of a target data component corresponding to the data component downloading request, deleting the target resource information, and sending the generated offline information to a cloud management platform, wherein the data operation request comprises the target data acquisition component selected by the business party, the authentication information is that a target data transmission component generated when the business party applies for the target data acquisition component on the cloud management platform is a data transmission component bound with the target data acquisition component, the target data processing component is a data processing component bound with the target data transmission component, and the target resource information is generated when the business party applies for the target data component on the cloud management platform.

The specific principle and the execution process of each unit in the data component management apparatus disclosed in the above embodiment of the present invention are the same as those of the data component management method disclosed in the above embodiment of the present invention in fig. 1, and reference may be made to corresponding parts in the data component management method disclosed in the above embodiment of the present invention in fig. 1, which are not described herein again.

The invention provides a data component management system, when a cloud management platform receives a project application request sent by a service party, a corresponding data component is applied for the service party based on the project application request, the applied data component is bound with other data components related to the data component under the authority of the service party, and authentication information and resource information related to the data component are generated so as to send the authentication information and the resource information related to the data component to the service party and a big data platform; when the big data platform receives a data operation request sent by a service party when logging in the big data platform based on authentication information, a target data acquisition component corresponding to the data operation request is adopted for data acquisition, a target data transmission component bound with the target data acquisition component is adopted for transmitting acquired data to a target data processing component bound with the target data transmission component, and the target data processing component processes the data; when a data assembly offline request sent by a service party is received, backing up target resource information of a target data assembly corresponding to the data assembly offline request, deleting the target resource information, sending the generated offline information to a cloud management platform, and informing the cloud management platform that the target data assembly is offline. Based on the technical scheme provided by the invention, a business party can apply for the corresponding data component through the cloud management platform, and after the application is successful, the business party logs in the big data platform based on the authentication information which is fed back by the cloud management platform and is related to the applied data component, so that the applied data component or the offline corresponding data component can be used on the big data platform.

The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of a unit does not in some cases constitute a limitation of the unit itself, for example, the first retrieving unit may also be described as a "unit for retrieving at least two internet protocol addresses".

The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.

An embodiment of the present application further provides an electronic device, which includes: the system comprises a processor and a memory, wherein the processor and the memory are connected through a communication bus; the processor is used for calling and executing the program stored in the memory; the memory is used for storing a program for implementing the data component management method.

Referring now to FIG. 7, a block diagram of an electronic device suitable for use in implementing the disclosed embodiments of the invention is shown. The electronic devices in the disclosed embodiments of the present invention may include, but are not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and the like, and fixed terminals such as digital TVs, desktop computers, and the like. The electronic device shown in fig. 7 is only an example, and should not bring any limitation to the functions and the scope of use of the disclosed embodiments of the present invention.

As shown in fig. 7, the electronic device may include a processing device (e.g., central processing unit, graphics processor, etc.) 701, which may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)702 or a program loaded from a storage device 706 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data necessary for the operation of the electronic apparatus are also stored. The processing device 701, the ROM 702, and the RAM 703 are connected to each other by a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.

Generally, the following devices may be connected to the I/O interface 705: input devices 706 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; an output device 707 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 708 including, for example, magnetic tape, hard disk, etc.; and a communication device 709. The communication device 709 may allow the electronic device to communicate wirelessly or by wire with other devices to exchange data. While fig. 7 illustrates an electronic device having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.

In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated by the flowchart. In such embodiments, the computer program may be downloaded and installed from a network via the communication means 709, or may be installed from the storage means 708, or may be installed from the ROM 702. The computer program, when executed by the processing device 701, performs the above-described functions defined in the methods of the disclosed embodiments of the invention.

Furthermore, an embodiment of the present invention further provides a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and the computer-executable instructions are used for executing the data component management method.

The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: receiving a data operation request sent by a service party when the service party logs in the big data platform based on authentication information, wherein the data operation request comprises a target data acquisition component selected by the service party, and the authentication information is generated when the service party applies for the target data acquisition component on a cloud management platform; acquiring data by using the target data acquisition component, transmitting the data to a target data processing component by using a target data transmission component, and processing the data by using the target data processing component, wherein the target data transmission component is a data transmission component bound with the target data acquisition component, and the target data processing component is a data processing component bound with the target data transmission component; when a data component offline request sent by the business party is received, backing up target resource information of a target data component corresponding to the data component offline request, deleting the target resource information, and sending generated offline information to the cloud management platform, wherein the target resource information is generated when the business party applies for the target data component on the cloud management platform.

Alternatively, the first and second electrodes may be,

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

It should be noted that the computer readable medium mentioned above in the present disclosure may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.

The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.

Claims

1. A data component management method is applied to a big data platform, and comprises the following steps:

2. The method according to claim 1, wherein when receiving a data component offline request sent by the service party, backing up target resource information of a target data component corresponding to the data component offline request, deleting the target resource information, and sending the generated offline information to the cloud management platform, includes:

receiving a data component offline request sent by the service party, wherein the data component offline request comprises a target data component requesting offline;

backing up target resource information of the target data assembly into a preset data table, and setting a request type of the target data assembly in the preset data table as an offline type, wherein the preset data table is preset in a standby library of the big data platform;

deleting the target resource information, and locking the target resource information in the preset data table;

and when the locking time reaches preset time, setting the request type of the target data assembly in the preset data table as offline, and sending the generated offline information to the cloud management platform.

3. The method according to claim 1, wherein if the target data component is a Flink data processing component or a Hadoop data storage component, when receiving a data component offline request sent by the service party, backing up target resource information of the target data component corresponding to the data component offline request, deleting the target resource information, and sending the generated offline information to the cloud management platform, includes:

when a Flink data processing assembly offline request sent by the service party is received, judging whether the running operation exists in the big data platform currently;

if the large data platform does not have the operation currently running, backing up the target resource information of the Flink data processing assembly into a preset data table, deleting the target resource information of the Flink data processing assembly, and sending the generated offline information to the cloud management platform;

if the large data platform has a currently running job, deleting the currently running job, backing up target resource information of the Flink data processing assembly into the preset data table, deleting the target resource information of the Flink data processing assembly, and sending the generated offline information to the cloud management platform;

accordingly, the method can be used for solving the problems that,

when a Hadoop data storage component offline request sent by the business party is received, judging whether the business party applies for the Flink data processing component or not;

if the business side applies for the Flink data processing assembly, performing offline processing on the Flink data processing assembly;

adding a preset field to a directory name corresponding to the Hadoop data storage assembly, deleting the yann data storage assembly in the Hadoop data storage assembly, backing up target resource information of the Hadoop data storage assembly with the yann data storage assembly deleted to the preset data table, deleting the target resource information, and sending generated offline information to the cloud management platform;

if the business side does not apply for the Flink data processing assembly, adding a preset field to a directory name corresponding to the Hadoop data storage assembly, deleting a yann data storage assembly in the Hadoop data storage assembly, backing up target resource information of the Hadoop data storage assembly with the yann data storage assembly deleted to the preset data table, deleting the target resource information, and sending generated offline information to the cloud management platform.

4. The method according to claim 1, wherein if the target data component is an HBase data storage component, when receiving a data component offline request sent by the service party, backing up target resource information of the target data component corresponding to the data component offline request, and deleting the target resource information, includes:

when an HBase data storage assembly offline request sent by the service party is received, recovering the namespace authority of the HBase data storage assembly and recovering the namespace authority of the service party to the HBase data storage assembly;

backing up the target resource information of the HBase data storage assembly into a preset data table, deleting the target resource information of the HBase data storage assembly, and sending the generated offline information to the cloud management platform.

5. A data component management method is applied to a cloud management platform, and comprises the following steps:

6. A data component management apparatus, applied to a big data platform, the apparatus comprising:

the system comprises a first receiving unit, a second receiving unit and a third receiving unit, wherein the first receiving unit is used for receiving a data operation request sent by a service party when the service party logs in the big data platform based on authentication information, the data operation request comprises a target data acquisition component selected by the service party, and the authentication information is generated when the service party applies for a project of the target data acquisition component on a cloud management platform;

7. A data component management device is applied to a cloud management platform, and comprises:

8. A data component management system, the system comprising:

the big data platform is used for receiving a data operation request sent by the service party when logging in the big data platform based on the authentication information; acquiring data by using the target data acquisition component, and transmitting the data to a target data processing component by using a target data transmission component so that the target data processing component processes the data; when a data component offline request sent by the service party is received, backing up target resource information of a target data component corresponding to the data component downloading request, deleting the target resource information, and sending the generated offline information to the cloud management platform, wherein the data operation request comprises a target data acquisition component selected by the service party, the authentication information is generated when the service party applies for the target data acquisition component on the cloud management platform, the target data transmission component is a data transmission component bound with the target data acquisition component, the target data processing component is a data processing component bound to the target data transmission component, the target resource information is generated when the business party applies for the target data component on the cloud management platform.

9. An electronic device, comprising: the system comprises a processor and a memory, wherein the processor and the memory are connected through a communication bus; the processor is used for calling and executing the program stored in the memory; the memory for storing a program for implementing the data component management method of any one of claims 1 to 4 or for implementing the data component management method of claim 5.

10. A computer-readable storage medium having stored thereon computer-executable instructions for performing the data component management method of any one of claims 1-4 or for performing the data component management method of claim 5.