Patent application EP18168871A (EP), filed 2018-04-24
Publication number: EP3401788A2
Title: EVENT STREAM PROCESSING SYSTEM
Abstract: In one embodiment, a stream processing system ingests data from one or more data sources and converts the data into an unbounded stream for an event stream processor. The stream processing system may include a first coordinating spout instance that is deployed at a first time, the first coordinating spout instance to instantiate one or more second spout instances and deploy said one more second spout instances at a second time that is later than the first time; the one or more second spout instances to: connect to the one or more data sources, respectively, and ingest a respective portion of the data from its respective one of the one or more data sources; and output messages based on the ingested portions of the data; wherein the unbounded stream for the event stream processor is based on the messages. Other embodiments may be disclosed and/or claimed.
IPC codes: G06F   9/    54            A I
G06F  17/    30            A I
G06F   9/    48            A I
G06F  16/  2455            A I
G06F  16/   958            A I
H04L  65/    60            A I
H04L  67/    10            A I
H04L  67/    55            A I
Claims: number: 1
text: A stream processing system to ingest data from one or more data sources and convert the data into an unbounded stream for an event stream processor, the stream processing system comprising:
number: 2
text: The stream processing system of claim 1, further comprising a message buffer to receive the output messages, wherein the unbounded stream is output from the buffer.
number: 3
text: The stream processing system of claim 1, further comprising:
number: 4
text: The stream processing system of claim 1, wherein the data sources comprise time ordered series event logs.
number: 5
text: The stream processing system of claim 3, wherein the data sources comprise time ordered series event logs, and wherein the additional data sources comprise additional time ordered series event logs.
number: 6
text: The stream processing system of claim 5, wherein the additional time ordered series event logs begin after a start time of the time ordered series event logs.
number: 7
text: The stream processing system of claim 3, wherein the first coordinating spout instance is further to receive messages from the event stream processor, to distribute the messages amongst the one or more second spout instances and the one or more third spout instances based on content of the messages.
number: 8
text: The stream processing system of claim 7, wherein the messages comprise message completion notifications and message failure notifications generated by the event stream processor responsive to processing the unbounded stream.
number: 9
text: The stream processing system of claim 8, wherein the messages are received over a single output interface of the event stream processor.
number: 10
text: The stream processing system of claim 1, the first coordinating spout instance to select an individual one of the one more second spout instances, to notify the individual one of the one or more second spout instances to deactivate, to close the selected spout instance the individual one of the one or more second spout instances.
number: 11
text: The stream processing system of claim 1, wherein the one or more second spout instances comprises a plurality of spout instances, wherein:
number: 12
text: The stream processing system of claim 11, wherein the selected time period corresponds to a period of unavailability of a storage device to store data generated by the event stream processor.
number: 13
text: A stream processing system to ingest data from one or more data sources and convert the data into an unbounded stream for an event stream processor, the stream processing system comprising:
number: 14
text: The stream processing system of claim 13, wherein the second spout instance is configured to apply a first filtering criterion to the portion of the data from the one or more data sources, and wherein the third spout instance is configured to apply a second filtering criterion that is different than the first filtering criterion to the portion of the data from the one or more data sources, wherein the second filtering criterion comprises a negation of the first filtering criterion.
number: 15
text: A method of ingesting data from one or more data sources and convert the data into an unbounded stream for an event stream processor, the method comprising:
Office action: search_report, dated 2018-11-14
Rejection reasons: novelty_epc_54
inventive_step_epc_56
Prior art cited: ref_id: US7730478B2
ref_type: patent
severity: background
ref_id: US7779039B2
ref_type: patent
severity: background
ref_id: - Anonymous, "Storm Sidelining Kafka Spout", (20170419), pages 1 - 9, URL: https://github.com/salesforce/storm-dynamic-spout/tree/12a8d0f6346d53b6f949d580ba5dde9e3b8ab883, (20181026), XP055519331 [X] 1-3,7,8,11-15 * the whole document * [I] 4-6,9,10
ref_type: npl
severity: novelty_destroying
ref_id: - Anonymous, "Time Travel Mementos for https://github.com/salesforce/storm-dynamic-spout", (20181026), pages 1 - 2, URL: http://timetravel.mementoweb.org/list/20170502000001/https://github.com/salesforce/storm-dynamic-spout, (20181026), XP055519321 [L] * the whole document *
ref_type: npl
severity: background
ref_id: - CE-KUEN SHIEH ET AL, "A topology-based scaling mechanism for Apache Storm", INTERNATIONAL JOURNAL OF NETWORK MANAGEMENT, GB, (20160113), vol. 27, no. 3, doi:10.1002/nem.1933, ISSN 1055-7148, pages 1 - 12, XP055518697 [I] 1-6,9,10,15 * page  3, line  12  - page  5, line  33; figures 1,2 * [A] 7,8 [Y] 11-14
ref_type: npl
severity: obviousness
ref_id: - Lukasz Kyc, "Retrying consumer architecture in the Apache Kafka", (20170324), pages 1 - 9, URL: https://blog.pragmatists.com/retrying-consumer-architecture-in-the-apache-kafka-939ac4cb851a, (20181029), XP055519579 [Y] 11-14 * the whole document * [A] 1-10,15
ref_type: npl
severity: obviousness
Final disposition: pending (2018-11-14)