Seaq is an opinionated wrapper for the first-party Elasticsearch dotnet libraries. It uses those libraries and expands upon them - it sets what are intended to be sensible defaults and provides consistent pathways for querying, indexing, and deleting documents. It provides a set of index management utilities, as well as shortcuts for source filtering, custom query scoring, and more.
Seaq's operation is based on the idea of a Cluster. A seaq Cluster is, at its base, meant to be roughly analogous to the physical Elasticsearch cluster. It supports the obvious actions like CreateIndex and Query, but also has some more idiosyncratic functionality like IncludeIndexInGlobalSearch and SetndexSecondaryFieldLabel. This document is intended to provide an exhaustive list of these options.
Each seaq cluster has a scope - this value should be unique, and should be easily recognizable. This scope value, provided at cluster creation, is used to identify the indices that are tied to the cluster and that the cluster should track. The default value for most seaq index names is {cluster scope}_{fully-qualified dotnet type name}. This default is intended to be descriptive, intuitive, and to reduce code complexity re: consistently tracking and constructing names.
A developer can create a cluster by calling the static seaq.Cluster.Create(ClusterArgs args) method. This method returns a functioning Cluster object with its internal index cache populated with all available server indices that match the provided scope. Ie a cluster created with scope "dev_server" would cache the existence, as well as settings for, indices "dev_server_Namespace.TypeName", but not "test_serer_Namespace.TypeName".
A seaq index is a direct representation of an Elasticsearch index. Each seaq index is mapped to a dotnet type - you'll want fully-qualified Type.FullName values as index names in most circumstances.
FAQs
Unknown package
We found that seaq demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Socket uncovered npm malware campaign mimicking popular Node.js libraries and packages from other ecosystems; packages steal data and execute remote code.
Research
Socket's research uncovers three dangerous Go modules that contain obfuscated disk-wiping malware, threatening complete data loss.
Research
Socket uncovers malicious packages on PyPI using Gmail's SMTP protocol for command and control (C2) to exfiltrate data and execute commands.
