CN110990337A - File transfer method and device, computer equipment and storage medium - Google Patents
File transfer method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN110990337A CN110990337A CN201911361201.3A CN201911361201A CN110990337A CN 110990337 A CN110990337 A CN 110990337A CN 201911361201 A CN201911361201 A CN 201911361201A CN 110990337 A CN110990337 A CN 110990337A
- Authority
- CN
- China
- Prior art keywords
- receiver
- file
- target file
- target
- storage
- 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 44
- 230000004907 flux Effects 0.000 claims description 8
- 230000000717 retained effect Effects 0.000 claims description 7
- 238000004590 computer program Methods 0.000 claims description 6
- 230000002776 aggregation Effects 0.000 abstract description 4
- 238000004220 aggregation Methods 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 10
- 230000005540 biological transmission Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- YNAVUWVOSKDBBP-UHFFFAOYSA-N Morpholine Chemical compound C1COCCN1 YNAVUWVOSKDBBP-UHFFFAOYSA-N 0.000 description 3
- 230000014759 maintenance of location Effects 0.000 description 2
- 230000004931 aggregating effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001052 transient effect Effects 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/119—Details of migration of file systems
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 embodiment of the invention discloses a file carrying method, a file carrying device, computer equipment and a storage medium, wherein the method comprises the following steps: acquiring content information of a target file through a channel of a receiver; acquiring a storage path of a target file, wherein the storage path is a pre-configured path for storing the target file by a receiver; and storing the target file according to the storage path. The scheme of the embodiment of the invention realizes the file transportation among subsystems in a large-scale software system through the Flume structure, and can also improve the stability of the file transportation of the subsystems in the software system on the premise of realizing the capabilities of file aggregation and load balancing.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a file carrying method and device, computer equipment and a storage medium.
Background
In a large software system, each subsystem is deployed in different equipment nodes so as to ensure that the subsystems are not influenced with each other, and data transfer is performed between the subsystems in a file mode under a common condition.
At present, the file data transfer of each subsystem in the software system is mainly realized through an Application Programming Interface (API).
In the prior art, the method for realizing file data transmission through the API interface is only suitable for a single deployed software system, and for a large-scale software system, different subsystems may be deployed in different application scenarios, so that file data transmission among the subsystems is realized through the API interface, and the API interface among the subsystems needs to be configured continuously, so that the file transmission efficiency is greatly reduced, and the stability of file data transfer of the subsystems in the software system is poor.
Disclosure of Invention
Embodiments of the present invention provide a file handling method, an apparatus, a computer device, and a storage medium, so as to implement file handling between subsystems in a large-scale software system through a Flume structure, and improve stability of file handling of subsystems in the software system on the premise of implementing file aggregation and load balancing capabilities.
In a first aspect, an embodiment of the present invention provides a file handling method, where the method includes:
acquiring content information of a target file through a channel (channel) of a receiver;
acquiring a storage path of the target file, wherein the storage path is a path which is configured in advance and used for storing the target file by a receiver;
and storing the target file according to the storage path.
In a second aspect, an embodiment of the present invention further provides a document transporting apparatus, where the apparatus includes:
the content information acquisition module is used for acquiring the content information of the target file through a channel of the receiver;
a storage path obtaining module, configured to obtain a storage path of the target file, where the storage path is a path for storing the target file by a pre-configured receiver;
and the target file storage module stores the target file according to the storage path.
In a third aspect, an embodiment of the present invention further provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the computer program to implement the file handling method according to any embodiment of the present invention.
In a fourth aspect, the embodiments of the present invention further provide a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the file handling method according to any embodiment of the present invention.
The embodiment of the invention obtains the content information of the target file through the channel of the receiver; acquiring a storage path of a target file, wherein the storage path is a pre-configured path for storing the target file by a receiver; and storing the target file according to the storage path. The file transportation among the subsystems in the large-scale software system is realized through the Flume structure, and the stability of the file transportation of the subsystems in the software system can be improved on the premise of realizing the capabilities of file aggregation and load balancing.
Drawings
FIG. 1 is a flowchart of a file handling method according to a first embodiment of the present invention;
fig. 2 is a schematic structural diagram of a sender and a receiver applicable to the first embodiment of the present invention;
FIG. 3 is a flowchart of a file handling method according to a second embodiment of the present invention;
FIG. 4 is a diagram of an application scenario applicable to the second embodiment of the present invention;
FIG. 5 is a flowchart of a file handling method according to a third embodiment of the present invention;
FIG. 6 is a diagram of an application scenario applicable to a third embodiment of the present invention;
FIG. 7 is a schematic structural diagram of a document transportation apparatus according to a fourth embodiment of the present invention;
fig. 8 is a schematic structural diagram of a computer device in the fifth embodiment of the present invention.
Detailed Description
The embodiments of the present invention will be described in further detail with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of and not restrictive on the broad invention. It should be further noted that, for convenience of description, only some structures, not all structures, relating to the embodiments of the present invention are shown in the drawings.
Example one
Fig. 1 is a flowchart of a file handling method in an embodiment of the present invention, where the embodiment is applicable to a case where file handling among subsystems is implemented in a large software system, and the method may be implemented by a file handling apparatus, which may be implemented by software and/or hardware and integrated in a computer device that executes the method. Specifically, referring to fig. 1, the method mainly includes the following steps:
and S110, acquiring the content information of the target file through the channel of the receiver.
It should be noted that, the sending party and the receiving party involved in the embodiment of the present invention both adopt a log collection system (Flume) structure, and Flume is a highly available, highly reliable, and distributed system for collecting, aggregating and transmitting mass logs. Specifically, the sender and the receiver mainly comprise a source, a channel and a sink, wherein the source mainly receives a data file from a data generator and transmits the received data file to the channel in a Flume event (event) format; a channel is a transient storage container that caches data files in the event format received from a source; and the sink reads the data cached in the channel and stores the data in and out.
Specifically, in the embodiment of the present invention, content information of a target file may be acquired from a channel of a receiving party; for example, one event may be obtained from a channel of the receiving side, and specific content may be obtained from the event as content information of the target file. It should be noted that the target file related in the embodiment of the present invention may be any file that needs to be carried in a software system, and the embodiment of the present invention is only named as the target file for convenience of description, and is not limited to the embodiment of the present invention.
Optionally, before the content information of the target file is acquired through the channel of the receiver, the target file may also be sent to the receiver through the sender.
Optionally, before sending the target file to the receiver through the sender, the method may further include: configuring an Internet Protocol (IP) and a port (port) in a sink of a sender; so that the IP and port of the sender and receiver are consistent.
Specifically, before sending the target file to the receiver through the sender, the sender and the receiver need to be configured; specifically, the IP of the sender may be configured according to the IP of the receiver, and the port of the sender may be modified to the port of the receiver; for example, if the receiver can receive the object file through the port 4, the sender modifies the attribute of the port to 4, and then the sender can send the object file to the port 4 of the receiver. This is because the IP and port of the sender and receiver are made identical, and preparation is made for transporting the object file from the sender to the receiver.
Furthermore, attribute information of each parameter in the source of the sender needs to be configured; wherein the attribute of the deserializer parameter is configured as org.apache.flux.sink.solr.morphhlene.BlobDesrializer $ Builder; configuring the attribute of the baserameheader parameter as true; the attribute of the basenameHeaderKey parameter is retained to a default value.
Specifically, attribute information of each parameter in the source of the sender needs to be configured. Specifically, the attribute of the deserializer parameter in the source of the sender may be configured as org.apache.flux.sink.solr.morphline.blobdeserializer $ Builder; it should be noted that configuring the attribute of the deserializer parameter as org, apache, flux, sink, solr, morphhline, blob deserializer $ Builder realizes that one target file is treated as one event, and the target file is cached in the channel of the sender in the form of the event.
Further, the attribute of the baseameheader parameter in the sender source may be configured to true. The reason for this is that the sender source can be made to add the file name of the target file to the header of the event corresponding to the target file; it should be noted that the header is a Key-Value (Key-Value) data structure.
Further, the attribute of the basenameHeaderKey parameter in the sender source may be retained to a default value. It should be noted that the default value is basename. Specifically, the significance of the basename header key is to designate the file name of the target file, that is, the default basename is the file name of the target file.
It should be noted that, in the embodiment of the present invention, the attribute of each parameter in the receiver source may be specifically set according to a specific situation, and is not limited in the embodiment of the present invention.
S120, obtaining a storage path of the target file, wherein the storage path is a path which is configured in advance and used for storing the target file by a receiver.
Specifically, after the content information of the target file is acquired through the channel of the receiver, the storage path of the target file may be further acquired, and it should be noted that the storage path related in the embodiment of the present invention is a path that is configured in advance and used by the receiver to store the target file.
In a specific example of the embodiment of the present invention, a parameter whose attribute value is a directory may be customized in advance, where the attribute value is a storage path of the target file.
And S130, storing the target file according to the storage path.
Specifically, the content information of the target file is acquired through the channel of the receiver, and after the storage path of the target file is acquired, the target file can be stored according to the storage path of the target file.
For example, if the target file is file a, the content information of file a may be acquired from the channel of the receiver, and before acquiring the content information of file a, the IP and the port in the sink of the sender may be configured so that the IP of the sender and the IP of the receiver corresponding to file a are consistent, and the sender may send file a to the specified port of the receiver. Further, configuring attribute information of each parameter in the source of the sender (for example, the source of the sender may be named as a spooldiretoreysource); specifically, the attribute of the deserializer parameter is configured as org.apache.flux.sink.solr.morphline.BlobDesrializer $ Builder; configuring the attribute of the baserameheader parameter as true; the attribute of the basenameHeaderKey parameter is retained to a default value. The attribute retention default value of the baseneameHeaderKey parameter is baseneme, and the baseneme is the file name of the file A. For example, the content information of the file a obtained from the channel of the receiving side may be an event corresponding to the file a cached from the channel of the sending side, and the content information corresponding to the file a is obtained from the event.
Further, after the content information and the file name of the file a are acquired, the storage path of the file a is acquired, and the file a is saved in the storage path of the file a.
According to the scheme of the embodiment, the content information of the target file is acquired through the channel of the receiver; acquiring a storage path of a target file, wherein the storage path is a pre-configured path for storing the target file by a receiver; and storing the target file according to the storage path, thereby realizing the file transportation among subsystems in the large-scale software system.
For better understanding of the embodiment of the present invention, fig. 2 is a schematic structural diagram of a sender and a receiver involved in the embodiment of the present invention. Specifically, the sender 210 includes a flood source211, a channel212, and an avrosink 213; the receiver 220 includes an avro source221, a channel222, and an OenEventOneFile Sink 223.
Specifically, the OenEventOneFile Sink223 may acquire content information of the object file from the channel222 of the receiver 220, and before acquiring the content information of the object file, configure the IP and the port in the avro Sink213 of the sender 210 and the avro source221 of the receiver 220, so that the IP of the sender 210 and the IP of the receiver 220 corresponding to the object file are consistent, and the sender 210 may send the object file to the designated port of the receiver 220. Further, configuring attribute information of each parameter in the shooter 210's flood source 211; specifically, the attribute of the deserializer parameter is configured as org.apache.flux.sink.solr.morphline.BlobDesrializer $ Builder; configuring the attribute of the baserameheader parameter as true; the attribute of the basenameHeaderKey parameter is retained to a default value. The attribute retention default value of the basenameHeaderKey parameter is basename, and the basename is the file name of the target file. For example, the content information of the target file acquired from the channel222 of the receiver 220 may be an event corresponding to the target file cached from the channel222 of the receiver 220, and the content information corresponding to the target file may be acquired from the event.
Further, after the content information and the file name of the target file are acquired, a storage path of the target file is acquired, and the content information of the target file is sent to the receiver 220, and after the receiver 220 receives the target file through a set port, the target file is stored in the storage path of the target file.
In the above example, the content information of the target file is acquired through the channel of the receiving side; acquiring a storage path of a target file, wherein the storage path is a pre-configured path for storing the target file by a receiver; and storing the target file according to the storage path, thereby realizing the file transportation among subsystems in the large-scale software system.
Example two
Fig. 3 is a flowchart of a file handling method in a second embodiment of the present invention, and this embodiment refines the embodiment of the present invention on the basis of the above embodiment, so as to implement aggregation of files; specifically, referring to fig. 3, the method mainly includes the following steps:
s310, acquiring content information of at least two target files through a channel of a receiver.
Specifically, in this embodiment, at least two senders may be included, for example, the number of senders may be two, three, or more, and the specific number of senders is not limited in the embodiment of the present invention.
Correspondingly, in this embodiment, the content information of the two target files can be acquired from the channel of the receiver; the content information of the plurality of target files may also be acquired from the channel of the receiving side.
Optionally, before the content information of the at least two destination files is acquired through the channel of the receiver, the IP and the port in the sink of the at least two senders may be configured, so that the IP and the port of the at least two senders are consistent with those of the receiver. It should be noted that, by configuring ports in the sink of at least two senders, a port of a receiver can be specified to receive at least two object files. For example, a port of the receiving party may be configured to receive at least two object files sent by at least two sending parties; at least two ports of the receiving party can also be configured to receive at least two object files sent by at least two sending parties.
Optionally, before acquiring content information of at least two target files through a channel of a receiver, attribute information of each parameter in sources of at least two senders needs to be configured; wherein the attribute of the deserializer parameter is configured as org.apache.flux.sink.solr.morphhlene.BlobDesrializer $ Builder; configuring the attribute of the baserameheader parameter as true; the attribute of the basenameHeaderKey parameter is retained to a default value. It should be noted that the default value of the attribute of the basenameHeaderKey parameter is basename, which is the file name of at least two target files.
S320, obtaining storage paths of at least two target files, wherein the storage paths are paths for storing the at least two target files by a pre-configured receiver.
Specifically, after the content information of at least two target files is acquired through the channel of the receiving party, the storage paths of the at least two target files may be acquired respectively. It should be noted that, in the embodiment of the present invention, the storage paths of at least two target files may be one storage path, that is, all target files are stored in one path; or at least two storage paths can be acquired, and at least two target files are stored respectively.
The method has the advantages that the files sent by a plurality of senders can be stored in the same storage path or different storage paths, and therefore the files are gathered.
S330, storing at least two target files according to the storage path.
Specifically, after the content information of at least two target files is acquired through the channel of the receiving party and the storage paths of the at least two target files are acquired, the at least two target files can be stored according to the storage paths.
According to the scheme of the embodiment, the content information of at least two target files is obtained through a channel of a receiver; acquiring storage paths of at least two target files, wherein the storage paths are paths for storing the at least two target files by a pre-configured receiver; and storing the target file according to the storage path. The method and the system realize file transport among subsystems in a large software system, can converge file contents of a plurality of senders to one receiver, and realize a convergence function.
For better understanding of the embodiment of the present invention, fig. 4 is a diagram of an application scenario applicable to the second embodiment. Specifically, as can be seen from fig. 4, the present example includes three senders 410, 420, 430 and one receiver 440.
Specifically, the content information of the three target files can be acquired through the channels of the receiver 440; acquiring storage paths of the three target files, wherein the storage paths are paths for storing the three target files by a pre-configured receiver; and storing the three target files according to the storage path.
In the above example, three senders and one receiver are included, and the file transmission of the three senders to the one receiver can be realized. The method and the system realize file transport among subsystems in a large software system, can converge file contents of three senders to one receiver, and realize a file convergence function.
EXAMPLE III
Fig. 5 is a flowchart of a file handling method in a third embodiment of the present invention, and in this embodiment, on the basis of the foregoing embodiment, the embodiment of the present invention is refined, so that load balancing of files can be achieved; specifically, referring to fig. 5, the method mainly includes the following steps:
and S510, acquiring content information of the target file through channels of at least two receivers.
S520, at least two storage paths of the at least two target files are respectively obtained, and the storage paths are paths which are configured in advance and used for storing the at least two target files by a receiver.
And S530, storing at least two target files according to the storage paths respectively.
For better understanding of the embodiment of the present invention, fig. 6 is an application scenario diagram of the third embodiment. Specifically, as can be seen from fig. 6, the receiver 610 in the application scenario includes a flood source611, a channel612, and a sink group 613; the recipients include recipient 621, recipient 622, and recipient 623.
Specifically, the OenEventOneFile Sink223 in the receiver 621, the receiver 622, and the receiver 623 may obtain the content information of the target file from the channels of the receiver 621, the receiver 622, and the receiver 623, respectively, and configure the parameters in the Sink group613 of the sender 610, the avro source of the receiver 621, the receiver 622, and the receiver 623 before obtaining the content information of the target file; illustratively, the values of the sink attributes of the sink group613 may be configured as avrosink1, avrosink2 and avrosink3, and the value of the processor type attribute of the sink group613 may be configured as load _ balance. Further, the receiver 621, the receiver 622, and the receiver 623 are configured according to the above-described embodiment. Finally, the files cached in the channel by the receiver are respectively sent to different receivers, file carrying among subsystems in a large software system is realized, and the capacity of system load balancing is enhanced.
Example four
Fig. 7 is a schematic structural diagram of a document handling apparatus according to a fourth embodiment of the present invention, which is capable of executing the document handling method according to any embodiment of the present invention; the apparatus may be implemented by means of software and/or hardware. Specifically, the device includes: a content information acquisition module 710, a storage path acquisition module 720, and a content information transmission module 730.
The content information acquiring module 710 is configured to acquire content information of a target file through a channel of a receiver;
a storage path obtaining module 720, configured to obtain a storage path of the target file, where the storage path is a path for storing the target file by a pre-configured receiver;
and an object file storage module 730 for storing the object file according to the storage path.
According to the scheme of the embodiment, the content information of the target file is acquired from the channel of the receiver through the content information acquisition module; acquiring a storage path of the target file through a storage path acquisition module, wherein the storage path is a path which is configured in advance and used for storing the target file by a receiver; and storing the target file according to the storage path, thereby realizing the file transportation among subsystems in the large-scale software system.
Optionally, the document carrying device related in this embodiment may further include: and the file transmission module is used for transmitting the target file to the receiver through the sender. Optionally, the sender and the receiver related in this embodiment both use a flow structure of a log collection system, where the sender and the receiver both include a source, a channel, and a sink.
Optionally, the document carrying device related in this embodiment may further include: and the configuration module is used for configuring the Internet protocol IP and the port in the sink of the sender so as to enable the IP and the port of the sender to be consistent with those of the receiver.
Optionally, the document carrying device related in this embodiment may further include: the attribute information configuration module is used for configuring the attribute information of each parameter in the source of the sender; wherein the attribute of the deserializer parameter is configured as org.apache.flux.sink.solr.morphhlene.BlobDesrializer $ Builder; configuring the attribute of the baserameheader parameter as true; the attribute of the basenameHeaderKey parameter is retained to a default value. The default value of the attribute of the basenameHeaderKey parameter is the basename, and the basename is the file name of the target file.
Optionally, the content information obtaining module 710 is specifically configured to obtain content information of at least two target files through a channel of the receiver; the storage path obtaining module 720 is specifically configured to obtain storage paths of at least two target files, where the storage paths are paths for storing the at least two target files on a pre-configured receiver.
Optionally, the content information obtaining module 710 is further specifically configured to obtain content information of the target file through channels of at least two receivers; the storage path obtaining module 720 is further specifically configured to obtain storage paths of the at least two target files, where the storage paths are paths for storing the at least two target files by a pre-configured receiver; the content information sending module 730 is further specifically configured to store at least two target files according to the storage paths, respectively.
The file carrying device provided by the embodiment of the invention can execute the file carrying method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
EXAMPLE five
Fig. 8 is a schematic structural diagram of a computer apparatus according to a fifth embodiment of the present invention, as shown in fig. 8, the computer apparatus includes a processor 80, a memory 81, an input device 82, and an output device 83; the number of the processors 80 in the computer device may be one or more, and one processor 80 is taken as an example in fig. 8; the processor 80, the memory 81, the input device 82 and the output device 83 in the computer apparatus may be connected by a bus or other means, and the connection by the bus is exemplified in fig. 8.
The memory 81 is a computer-readable storage medium, and can be used for storing software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the file handling method in the embodiment of the present invention (for example, the content information acquiring module 710, the storage path acquiring module 720, and the target file storing module 730 in the file handling apparatus). The processor 80 executes various functional applications and data processing of the computer device by executing software programs, instructions, and modules stored in the memory 81, thereby implementing the above-described file transfer method.
The memory 81 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Further, the memory 81 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, memory 81 may further include memory located remotely from processor 80, which may be connected to a computer device through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 82 may be used to receive input numeric or character information and generate key signal inputs relating to user settings and function controls of the computer apparatus. The output device 83 may include a display device such as a display screen.
EXAMPLE six
An embodiment of the present invention further provides a storage medium containing computer-executable instructions, which when executed by a computer processor, perform a file handling method, including:
acquiring content information of a target file through a channel of a receiver;
acquiring a storage path of a target file, wherein the storage path is a pre-configured path for storing the target file by a receiver;
and storing the target file according to the storage path.
Of course, the storage medium provided by the embodiment of the present invention contains computer-executable instructions, and the computer-executable instructions are not limited to the operations of the method described above, and may also perform related operations in the file transportation method provided by any embodiment of the present invention.
From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly, can also be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which may be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention.
It should be noted that, in the embodiment of the document transportation device, the included units and modules are only divided according to the functional logic, but are not limited to the above division as long as the corresponding functions can be realized; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (10)
1. A document handling method, comprising: acquiring content information of a target file through a channel of a receiver;
acquiring a storage path of the target file, wherein the storage path is a path which is configured in advance and used for storing the target file by a receiver;
and storing the target file according to the storage path.
2. The method according to claim 1, further comprising, before acquiring the content information of the target file through the channel of the receiving side: and transmitting the target file to a receiver through a sender.
3. The method of claim 2, further comprising, before transmitting the target file to a receiver via a sender:
configuring an Internet Protocol (IP) and a port in the sink of the sender so as to enable the IP and the port of the sender and the IP and the port of the receiver to be consistent;
configuring attribute information of each parameter in the source of the sender; wherein the attribute of the deserializer parameter is configured as org.apache.flux.sink.solr.morphhlene.BlobDesrializer $ Builder; configuring the attribute of the baserameheader parameter as true; the attribute of the basenameHeaderKey parameter is retained to a default value.
4. The method of claim 3, wherein said retaining an attribute of the basenameHeaderKey parameter to a default value comprises:
the default value of the attribute of the basenameHeaderKey parameter is the basename, and the basename is the file name of the target file.
5. The method according to any one of claims 1-4, wherein the sender and the receiver both employ a Flume structure, and wherein the receiver includes source, channel, and sink.
6. The method of claim 1, further comprising:
acquiring content information of at least two target files through the channel of the receiver;
acquiring storage paths of at least two target files, wherein the storage paths are paths for storing the at least two target files by a pre-configured receiver;
and storing at least two target files according to the storage path.
7. The method of claim 1, further comprising:
acquiring content information of at least two target files through channels of at least two receivers;
respectively obtaining storage paths of at least two target files, wherein the storage paths are paths for storing the at least two target files by a pre-configured receiver;
and storing at least two target files according to each storage path respectively.
8. A document handling apparatus, comprising:
the content information acquisition module is used for acquiring the content information of the target file through a channel of the receiver;
a storage path obtaining module, configured to obtain a storage path of the target file, where the storage path is a path for storing the target file by a pre-configured receiver;
and the target file storage module stores the target file according to the storage path.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the file handling method of any of claims 1-7 when executing the program.
10. A computer-readable storage medium on which a computer program is stored, the program, when being executed by a processor, implementing a document handling method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911361201.3A CN110990337A (en) | 2019-12-25 | 2019-12-25 | File transfer method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911361201.3A CN110990337A (en) | 2019-12-25 | 2019-12-25 | File transfer method and device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110990337A true CN110990337A (en) | 2020-04-10 |
Family
ID=70076954
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911361201.3A Pending CN110990337A (en) | 2019-12-25 | 2019-12-25 | File transfer method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110990337A (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5229850A (en) * | 1990-07-30 | 1993-07-20 | Kabushiki Kaisha Toshiba | Video monitoring system including a memory for storing and transmitting a video signal immediately following the occurrence of an event |
| JP2005078595A (en) * | 2003-09-03 | 2005-03-24 | Hitachi Ltd | Program and information processor |
| CN101262447A (en) * | 2008-04-21 | 2008-09-10 | 中国科学院计算技术研究所 | A method for system terminal to establish NAT channel penetration |
| US20110283037A1 (en) * | 2010-05-13 | 2011-11-17 | Hitachi, Ltd. | Information processing apparatus and data transfer method |
| US20130185616A1 (en) * | 2010-09-15 | 2013-07-18 | Wei Yuan | Method and device for implementing viterbi decoding |
| CN105991629A (en) * | 2015-03-26 | 2016-10-05 | 杭州迪普科技有限公司 | TCP (transmission control protocol) connection establishment method and device |
| CN106776715A (en) * | 2016-11-16 | 2017-05-31 | 北京集奥聚合科技有限公司 | A kind of method and system of collector journal |
| CN106888498A (en) * | 2017-01-25 | 2017-06-23 | 北京奇虎科技有限公司 | A kind of inter-terminal data transmission method, device and mobile terminal |
| CN108509297A (en) * | 2018-03-21 | 2018-09-07 | 四川斐讯信息技术有限公司 | A kind of data back up method and system |
| CN110457256A (en) * | 2019-08-01 | 2019-11-15 | 大众问问(北京)信息科技有限公司 | Date storage method, device, computer equipment and storage medium |
-
2019
- 2019-12-25 CN CN201911361201.3A patent/CN110990337A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5229850A (en) * | 1990-07-30 | 1993-07-20 | Kabushiki Kaisha Toshiba | Video monitoring system including a memory for storing and transmitting a video signal immediately following the occurrence of an event |
| JP2005078595A (en) * | 2003-09-03 | 2005-03-24 | Hitachi Ltd | Program and information processor |
| CN101262447A (en) * | 2008-04-21 | 2008-09-10 | 中国科学院计算技术研究所 | A method for system terminal to establish NAT channel penetration |
| US20110283037A1 (en) * | 2010-05-13 | 2011-11-17 | Hitachi, Ltd. | Information processing apparatus and data transfer method |
| US20130185616A1 (en) * | 2010-09-15 | 2013-07-18 | Wei Yuan | Method and device for implementing viterbi decoding |
| CN105991629A (en) * | 2015-03-26 | 2016-10-05 | 杭州迪普科技有限公司 | TCP (transmission control protocol) connection establishment method and device |
| CN106776715A (en) * | 2016-11-16 | 2017-05-31 | 北京集奥聚合科技有限公司 | A kind of method and system of collector journal |
| CN106888498A (en) * | 2017-01-25 | 2017-06-23 | 北京奇虎科技有限公司 | A kind of inter-terminal data transmission method, device and mobile terminal |
| CN108509297A (en) * | 2018-03-21 | 2018-09-07 | 四川斐讯信息技术有限公司 | A kind of data back up method and system |
| CN110457256A (en) * | 2019-08-01 | 2019-11-15 | 大众问问(北京)信息科技有限公司 | Date storage method, device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9110884B2 (en) | Message publishing and subscribing method and apparatus | |
| KR101886291B1 (en) | Flow entry configuration method, apparatus, and system | |
| KR101717000B1 (en) | Method and device for packet handling | |
| CN107948324B (en) | Request Transmission system, method, apparatus and storage medium | |
| US10148565B2 (en) | OPENFLOW communication method and system, controller, and service gateway | |
| CN107347062A (en) | A kind of method, electronic equipment and the readable storage medium storing program for executing of daily record data processing | |
| WO2014067311A1 (en) | Resource subscription method and device | |
| RU2012105911A (en) | METHOD AND DEVICE FOR IMPLEMENTING A HOST-UNIT CONTROL PROTOCOL WITH A LOW LOAD ON THE ROUTER WITH THE MULTI-ADDRESS FUNCTION | |
| CN108322467A (en) | Virtual firewall configuration method, electronic equipment and storage medium based on OVS | |
| CN104486327B (en) | Communication means and client between the page and long connection server | |
| CN102707696B (en) | Multi-serial-port data transmission method and transmission center system | |
| CN112527530B (en) | Message processing method, device, apparatus, storage medium and computer program product | |
| WO2020078381A1 (en) | Data aggregation method, device, equipment, storage medium and system | |
| CN113810349B (en) | Data transmission method, device, computer equipment and storage medium | |
| CN102281204B (en) | Method and routing equipment for implementing rendezvous point (RP) load sharing of multicast group and routing equipment | |
| CN112055078A (en) | Data transmission method and device, computer equipment and storage medium | |
| CN114025000B (en) | Method, device, equipment and storage medium for establishing network access relationship | |
| CN110278156B (en) | Multicast routing processing method, network equipment and route reflector | |
| CN103716244A (en) | Method and device enabling extra-VPN forwarding of multicasts to be achieved | |
| CN110990337A (en) | File transfer method and device, computer equipment and storage medium | |
| CN103297455B (en) | Connection sharing method between browser and device | |
| JP2013126219A (en) | Transfer server and transfer program | |
| CN101860544A (en) | Transmitting system and method of session initiation protocol message | |
| CN114900455B (en) | Message transmission method, system, equipment and storage medium | |
| CN113595912B (en) | One-to-many communication method and device based on IPv6 extension header in 5GLAN |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200410 |
|
| RJ01 | Rejection of invention patent application after publication |