Stream browser for data streams
AssigneeEMC IP Holding Company LLC
InventorsMikhail Danilov, Igor Medvedev
Life of this patent
Estimating the term…
Loading patent…
AssigneeEMC IP Holding Company LLC
InventorsMikhail Danilov, Igor Medvedev
Estimating the term…
The described technology is generally directed towards a stream browser that provides a human-readable (e.g., hierarchical) view of event data for a data stream of a data streaming storage service. A stream browser associated with a data stream maintains routing key and event data for the data stream, e.g., in a primary index. The routing keys can correspond to container structures, e.g., folders and subfolders, with the events associated with each routing key corresponding to hierarchical children of the routing key parent container structures (e.g., like files). A secondary index can be used to evict the oldest events from the primary index to limit the number of data stream events returnable by the stream browser to a practical number.
A system, comprising:
A method comprising:
A non-transitory machine-readable storage medium, comprising executable instructions that, when executed by a processor of a streaming data storage system, facilitate performance of operations, the operations comprising:
Dependencies are inferred from the claim text.
Drawings are temporarily unavailable. Open the PDF at USPTO
From the US filing history. Foreign family members aren’t listed.
File systems; File servers: file access structures, e.g. distributed indices
Query execution: data stream processing; Continuous queries
Details of further file system functions: details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
File system types: distributed file systems
About 14 years 1 month of term left · ends 24 Nov 2040 (estimated)
The subject application relates generally to data storage, and, for example, to a technology that provides a hierarchical view on stream data in storage systems that implement data streams for storing and serving continuous and unbounded data, and related embodiments.
Contemporary data storage systems, such as DELL EMC's PRAVEGA system/data storage service, store data in a storage abstraction referred to as a stream. A stream is identified with a name, and can store continuous and potentially unbounded data; more particularly, a stream comprises a durable, elastic, append-only, sequence of stored events.
New events are added to a tail (front) of a stream. As can be readily appreciated, PRAVEGA is thus ideal for IoT (Internet of Things) data, where devices/sensors may generate thousands of data points per second. One stream may be divided into one or more segments, such as based on routing keys associated with the events, such as derived from data naturally occurring in the event, e.g. “machine-id.”
The technology described herein is illustrated by way of example and not limited in the accompanying figures in which like reference numerals indicate similar elements and in which:
FIG. 1 is a block diagram representation of example writer components and data—related operations in a streaming data storage system that provides a hierarchical view of streamed data via a stream browser, in accordance with various aspects and implementations of the subject disclosure
FIG. 2 is a block diagram representation of example reader components and data—related operations in a streaming data storage system that provides a hierarchical view of streamed data via a stream browser, in accordance with various aspects and implementations of the subject disclosure
Various aspects of the technology described herein are generally directed towards a stream browser that facilitates human interaction with stream data, in particular for a human to observe and navigate through the data (events) in a stream-based data storage system. In one aspect, a hierarchical view on streams is provided by maintaining event container structures (e.g., folders) within a single stream. In this way, content of a stream may be seen and navigated through via a hierarchical view, similar to viewing a file system of folders and files.
It should be understood that any of the examples herein are non-limiting. For instance, some of the examples are based on PRAVEGA data storage technology; however virtually any stream-based data storage system may benefit from the technology described herein. Indeed, the technology described herein can be applied to any stream-based data storage mechanism. As such, any of the embodiments, aspects, concepts, structures, functionalities or examples described herein are non-limiting, and the technology may be used in various ways that provide benefits and advantages in computing and data storage in general.
Reference throughout this specification to “one embodiment,” “an embodiment,” “one implementation,” “an implementation,” etc. means that a particular feature, structure, or characteristic described in connection with the embodiment/implementation is included in at least one embodiment/implementation. Thus, the appearances of such a phrase “in one embodiment,” “in an implementation,” etc. in various places throughout this specification are not necessarily all referring to the same embodiment/implementation. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments/implementations.