CN113238994A - Report file management and publishing method - Google Patents
Report file management and publishing method Download PDFInfo
- Publication number
- CN113238994A CN113238994A CN202110533536.XA CN202110533536A CN113238994A CN 113238994 A CN113238994 A CN 113238994A CN 202110533536 A CN202110533536 A CN 202110533536A CN 113238994 A CN113238994 A CN 113238994A
- Authority
- CN
- China
- Prior art keywords
- report
- file
- preset
- issued
- published
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 40
- 238000012550 audit Methods 0.000 claims abstract description 28
- 238000007726 management method Methods 0.000 claims abstract description 15
- 238000013500 data storage Methods 0.000 claims description 5
- 238000012795 verification Methods 0.000 claims description 5
- 238000012217 deletion Methods 0.000 abstract description 3
- 230000037430 deletion Effects 0.000 abstract description 3
- 238000011161 development Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 3
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012800 visualization Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
- G06F16/122—File system administration, e.g. details of archiving or snapshots using management policies
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/172—Caching, prefetching or hoarding of files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/1734—Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application relates to a report file management and publishing method, firstly receiving report files to be published and publishing requests uploaded by developers, but not uploading the report files to be published to a report cluster, but storing the report files to be published to a preset file storage server; then, auditing the release request and the report file to be released; the auditing comprises system auditing through a preset system, or sending a release request to an administrator through preset message pushing software, so that the administrator can manually audit the release request and the report file to be released; and finally, after the audit is passed, the file to be issued is issued to each node of the preset report cluster. Therefore, the report file can be audited before being issued by the developer, and the report file is only allowed to be issued after the audit is passed, so that the report file is managed, and misoperation such as file deletion by mistake, uploading by mistake, coverage by mistake and the like when the developer uploads by oneself is avoided.
Description
Technical Field
The application relates to the technical field of internet, in particular to a report file management and publishing method.
Background
With the advent of the big data era, the visualization demand of enterprises on data is increasing day by day, and report development tools come. The report development tool accelerates the report development speed, but lacks the maintenance and the release of the report file. When the developer completes the report development according to the business requirements, the report file after the development is required to be uploaded to the report cluster. And during uploading, developers enter the server to operate by themselves. In the process of releasing the report files to the report clusters, corresponding releasing tools are not available, and the report files can be uploaded to the report clusters only manually. In the process, the report files are not managed in a unified mode, an auditing link is lacked, developers upload the report files by themselves, and misoperation risks exist, such as: server account and password leakage, file deletion by mistake, file uploading by mistake, error coverage and the like.
Disclosure of Invention
The report file management and release method is used for solving the problems that in the prior art, in the process of uploading the report files by developers, the report files are lack of the audit link, unified management cannot be carried out on the report files, and misoperation easily occurs.
The above object of the present application is achieved by the following technical solutions:
the embodiment of the application provides a report file management and release method, which comprises the following steps:
receiving report files to be published and publishing requests uploaded by developers, and storing the report files to be published into a preset file storage server;
auditing the issuing request and the file to be issued; the auditing comprises system auditing through a preset system, or the issuing request is sent to a manager through preset message pushing software, so that the manager can manually audit the issuing request and the report file to be issued;
and after the verification is passed, the file to be issued is issued to each node of a preset report cluster.
Optionally, the number of times of receiving the report file to be published and the publishing request uploaded by the developer may be multiple times.
Optionally, the method further includes:
and recording all report files to be published uploaded by the developers and the uploaded information to generate version record data of the same file to be published.
Optionally, the performing system audit through the preset system includes:
judging whether developers sending report files to be issued and issuing requests are non-audit developers or not through a preset system based on a preset white list;
and when the developers sending the report files to be issued and the issuing requests are the developers without auditing, the system automatically passes the auditing.
Optionally, after the file to be published is published to each node of a preset report cluster, the method further includes:
and uploading the issued file to a big data storage service for backup.
The technical scheme provided by the embodiment of the application can have the following beneficial effects:
according to the technical scheme provided by the embodiment of the application, firstly, a report file to be published and a publishing request uploaded by a developer are received, the report file to be published is not uploaded to a report cluster, and the report file to be published is stored in a preset file storage server; then, the issuing request and the file to be issued are checked; the auditing comprises system auditing through a preset system, or sending a release request to a manager through preset message push software, so that the manager can manually audit the release request and a report file to be released; and finally, after the audit is passed, the file to be issued is issued to each node of the preset report cluster. Therefore, the report file can be audited before the report file is issued by the developer, and the report file is only allowed to be issued after the audit is passed, so that the report file is managed, and misoperation, such as file deletion by mistake, uploading by mistake, coverage by mistake and the like, is avoided when the developer uploads by oneself.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
Fig. 1 is a schematic flowchart illustrating a method for managing and publishing a report file according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a method for managing and publishing a report file according to another embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
Fig. 1 is a schematic flowchart of a method for managing and publishing a report file according to an embodiment of the present application, where as shown in fig. 1, the method for managing and publishing a report file according to the embodiment of the present application includes:
s101, receiving a report file to be published and a publishing request uploaded by a developer, and storing the report file to be published into a preset file storage server;
specifically, after completing the development of the report file, a developer enters a preset independently-developed software tool or a third-party software tool, uploads the file through the independently-developed software or the third-party software, and uploads the report file to be published to a file storage server (fastDFS) in a preset system for storage. After the developer finishes uploading the file, the uploaded report file is applied and published, namely a publishing application is sent.
It should be noted that, in the process of uploading the report file to be published to the file export server by the developer, the developer may upload the same file many times, and the preset system performs statistical recording on the file uploaded each time and information uploaded, such as uploading time and other information, to generate a corresponding version record, so that the developer can conveniently trace back the file.
S102, auditing the release request and the file to be released;
in practical application, the auditing comprises system auditing through a preset system, or the issuing request is sent to a manager through preset message pushing software, so that the manager can manually audit the issuing request and the report file to be issued;
specifically, after receiving a file to be published and a publishing request uploaded by a developer, entering a publishing flow for circulation, and first performing auditing. The audit comprises system audit or manual audit. The system auditing process comprises the following steps: firstly, configuring audit-free developer information in a white list in a preset system, acquiring the information of a developer when a release application is received, and judging whether the developer who sends the release application is an audit-free developer or not; when the developer is not free from auditing the developer, the system performs self-defined auditing or directly passes the auditing, so that the flow circulation is accelerated. The process of manual review comprises the following steps: and sending the release request to a corresponding manager through preset message pushing software for the manager to perform quick verification.
In practical application, after receiving the release application, the system can be audited first, that is, whether the corresponding developer is an audit-free developer is judged, and when the corresponding developer is the audit-free developer, the audit can be passed directly, and the system-defined audit can be performed; and when the corresponding developer is judged not to be an audit-free developer, carrying out manual audit, namely sending the release request to a corresponding manager through preset message pushing software for the manager to carry out rapid audit.
S103, after the auditing is passed, the file to be issued is issued to each node of a preset report cluster.
Specifically, after the verification is passed, the system can automatically release the file to be released uploaded by the developer to each node of the report cluster. Or a developer performs file publishing operation, deploys the report file to each node of the report cluster by using self-developed deployment service, and completes synchronization.
Further, the report file management and publishing method provided by the embodiment of the application further comprises backing up the published file to a big data storage service (HDFS) to prevent the server file from being lost. And after the report is released, the latest report can be checked in the report development tool.
A specific implementation process is described below to describe the report file management and publishing method provided by the present application, and fig. 2 is a schematic flow chart of a report file management and publishing method shown in another embodiment of the present application, and as shown in fig. 2, the report file management and publishing method provided by the present application includes:
firstly, uploading a report file by a developer, and applying and issuing after the file is uploaded successfully, namely sending an issuing application; auditing the published application through a preset system, and automatically passing the auditing if the developer publishing the application is an auditing-free developer on a preset white list in the system; if the developer who issues the application is not an audit-free developer, informing the software to inform an administrator through a preset message for the administrator to perform manual audit; whether the audit is the automatic audit of the system or the manual audit of the administrator, if the audit is not passed, the developer needs to upload again, namely, after the report file and the like are modified, the file is uploaded again, and the application and the release are carried out again; if the file passes the verification, the file is automatically issued by a system or a developer, the file is uploaded to a report cluster, and the file is uploaded to a big data storage service (HDFS) for backup to complete the issue.
According to the report file management and publishing method, in the process of publishing the report file by a developer, the file is firstly stored in the file storage server, an auditing flow is added, the report file to be published is audited, the developer is allowed to upload again when the audit is not passed, and the report file is deployed into a report cluster through the automatically researched and developed deployment service only after the audit is passed. In the process, files uploaded for multiple times and uploading information are recorded for a servicer to trace the files, so that version control is facilitated; and after uploading the file to the report cluster, uploading the file to a big data storage service for backup. Therefore, unified management of the uploaded report files is achieved, and the risk of misoperation of developers is avoided. And moreover, the report file is backed up to a file storage service, version control and file backup are carried out on the report file, and a report development tool is endowed with file tracing and damage recovery capabilities.
It is understood that the same or similar parts in the above embodiments may be mutually referred to, and the same or similar parts in other embodiments may be referred to for the content which is not described in detail in some embodiments.
It should be noted that, in the description of the present application, the terms "first", "second", etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Further, in the description of the present application, the meaning of "a plurality" means at least two unless otherwise specified.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and the scope of the preferred embodiments of the present application includes other implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.
In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Although embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.
Claims (5)
1. A report file management and release method is characterized by comprising the following steps:
receiving report files to be published and publishing requests uploaded by developers, and storing the report files to be published into a preset file storage server;
auditing the issuing request and the file to be issued; the auditing comprises system auditing through a preset system, or the issuing request is sent to a manager through preset message pushing software, so that the manager can manually audit the issuing request and the report file to be issued;
and after the verification is passed, the file to be issued is issued to each node of a preset report cluster.
2. The report file managing and publishing method according to claim 1, wherein the number of receiving report files to be published and publishing requests uploaded by developers can be multiple times.
3. The report file management and release method according to claim 2, further comprising:
and recording all report files to be published uploaded by the developers and the uploaded information to generate version record data of the same file to be published.
4. The report file management and release method according to claim 1, wherein the system audit by the preset system comprises:
judging whether developers sending report files to be issued and issuing requests are non-audit developers or not through a preset system based on a preset white list;
and when the developers sending the report files to be issued and the issuing requests are the developers without auditing, the system automatically passes the auditing.
5. The report file managing and publishing method according to claim 1, wherein after the publishing the file to be published to each node of a preset report cluster, the method further comprises:
and uploading the issued file to a big data storage service for backup.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110533536.XA CN113238994A (en) | 2021-05-17 | 2021-05-17 | Report file management and publishing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110533536.XA CN113238994A (en) | 2021-05-17 | 2021-05-17 | Report file management and publishing method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113238994A true CN113238994A (en) | 2021-08-10 |
Family
ID=77134566
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110533536.XA Pending CN113238994A (en) | 2021-05-17 | 2021-05-17 | Report file management and publishing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113238994A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103440168A (en) * | 2013-09-09 | 2013-12-11 | 中国农业银行股份有限公司 | Method and system for program change |
| CN107656742A (en) * | 2017-09-27 | 2018-02-02 | 北京奇虎科技有限公司 | A kind of software product dissemination method and device |
| WO2020253347A1 (en) * | 2019-06-17 | 2020-12-24 | 深圳前海微众银行股份有限公司 | Container cluster management method, device and system |
| CN112561370A (en) * | 2020-12-23 | 2021-03-26 | 平安银行股份有限公司 | Software version management method and device, computer equipment and storage medium |
-
2021
- 2021-05-17 CN CN202110533536.XA patent/CN113238994A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103440168A (en) * | 2013-09-09 | 2013-12-11 | 中国农业银行股份有限公司 | Method and system for program change |
| CN107656742A (en) * | 2017-09-27 | 2018-02-02 | 北京奇虎科技有限公司 | A kind of software product dissemination method and device |
| WO2020253347A1 (en) * | 2019-06-17 | 2020-12-24 | 深圳前海微众银行股份有限公司 | Container cluster management method, device and system |
| CN112561370A (en) * | 2020-12-23 | 2021-03-26 | 平安银行股份有限公司 | Software version management method and device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11314499B2 (en) | Simulating end-to-end upgrade process in production environment | |
| US11593302B2 (en) | Methods, systems, and computer readable mediums for implementing a data protection policy for a transferred enterprise application | |
| US8918783B2 (en) | Managing virtual computers simultaneously with static and dynamic dependencies | |
| US8352916B2 (en) | Facilitating the automated testing of daily builds of software | |
| JP6050342B2 (en) | Managing replicated virtual storage at the recovery site | |
| US8972963B2 (en) | End-to-end patch automation and integration | |
| US10019250B2 (en) | Forcibly completing upgrade of distributed software in presence of failures | |
| US20110296398A1 (en) | Systems and methods for determining when to update a package manager software | |
| JP6788178B2 (en) | Setting support program, setting support method and setting support device | |
| CN110750584B (en) | Data management method and system | |
| CN103034563A (en) | Method and system for managing back up operations for data | |
| US20090006493A1 (en) | Method For Enabling Traceability And Recovery From Errors During Migration Of Software Applications | |
| CN114443332B (en) | Storage pool detection method and device, electronic equipment and storage medium | |
| CN105022678A (en) | Data backup method and apparatus for virtual machine | |
| US9262290B2 (en) | Flash copy for disaster recovery (DR) testing | |
| CN113254326A (en) | Method and system for releasing firmware codes of solid state disk by utilizing Jenkins | |
| CN103186353B (en) | The system that data set copies, method and apparatus | |
| CN113238994A (en) | Report file management and publishing method | |
| US11836046B1 (en) | Tagging writers for incremental backups of system objects | |
| US20190065168A1 (en) | Apparatus and method to shorten software installation time based on a history of file installation | |
| CN110716737A (en) | System application version management system and system application version management method | |
| CN115080309A (en) | Data backup system, method, storage medium, and electronic device | |
| CN114461957A (en) | Method, device and equipment for issuing road tools and storage medium | |
| CN112256481A (en) | Data recovery method and system in agile development | |
| CN113485766A (en) | Reverse proxy cluster management method and system based on salt and nginx |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |