These capabilities are currently in beta. Please contact founders@tryneum.com with any questions or asks.
Overview
Pipeline collections are a higher level abstraction that joins multiple pipelines as a single entity. This means that you can configure pipelines individually for different data source, pre-processing steps, etc. but still treat them as a group when it comes to triggering them to run as well as when searching them. When it comes to search, pipeline collections support three search options:- Unified search where results from the pipelines are collected and re-ranked into a single response.
- Separate search where results for each pipeline are returned raw with an assignment to what pipeline they came from.
- (Coming soon) Routed search where the system uses the pipeline description to decide what pipelines to search given a query and re-rank the results.
Example
For example, there are three pipelines that I have:- The first connects to S3 where I have files from customers
- The second connects to Postgres where I am querying real-time metrics
- The third connects to some static websites with content