-
Notifications
You must be signed in to change notification settings - Fork 5
Support for alternative storage backend(s) - S3 #395
Copy link
Copy link
Open
Labels
distributedConcerns distributed query capabilities (global-query, etc.)Concerns distributed query capabilities (global-query, etc.)featureNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is neededperformancePerformance / optimization related topicsPerformance / optimization related topics
Description
Metadata
Metadata
Assignees
Labels
distributedConcerns distributed query capabilities (global-query, etc.)Concerns distributed query capabilities (global-query, etc.)featureNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is neededperformancePerformance / optimization related topicsPerformance / optimization related topics
Although goProbe was / is conceived as a distributed capture / storage / query system there may be scenarios where data storage on the capturing device(s) is prohibitive. Currently there is no conceptual support for anything other than the custom GPDir / GPFile concept (with all its optimizations).
This issue tracks the potential introduction of a code path (e.g. via build tags) to support a non-optimized write / read path to handle data and the implementation of e.g. an S3 backed (although technically at that point that path could be as generic / extensible as possible, even / ideally via plugins).