-
Notifications
You must be signed in to change notification settings - Fork 270
RC: Cloud Search and Query changes #694
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -68,6 +68,8 @@ Use the **Database list** to check the status of your databases. | |||||||||
|
|
||||||||||
| ## Create database with Custom settings {#custom-settings} | ||||||||||
|
|
||||||||||
| {{<image filename="images/rc/create-pro-db-settings-custom.png" alt="The database settings section, with custom settings selected.">}} | ||||||||||
|
|
||||||||||
| If you choose to create your database with custom settings, you need to: | ||||||||||
|
|
||||||||||
| 1. Set up the deployment options, including cloud vendor details, high availability settings, and advanced options. | ||||||||||
|
|
@@ -149,10 +151,10 @@ By default, you're shown basic settings, which include: | |||||||||
| | Database setting | Description | | ||||||||||
| |:---------|:-----------| | ||||||||||
| | **Name** | A custom name for your database (_required_) | | ||||||||||
| | **Advanced Capabilities** | Advanced data types used by the database. Choose from [Search and query]({{< relref "/operate/oss_and_stack/stack-with-enterprise/search" >}}), [JSON]({{< relref "/operate/oss_and_stack/stack-with-enterprise/json" >}}), [Time series]({{< relref "/operate/oss_and_stack/stack-with-enterprise/timeseries" >}}), [Probabilistic]({{< relref "/operate/oss_and_stack/stack-with-enterprise/bloom" >}}), or [Graph (EOL)]({{< relref "/operate/oss_and_stack/stack-with-enterprise/deprecated-features/graph" >}}). <br/> Databases with Search and query have specific sizing requirements, see [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. | | ||||||||||
| | **Query performance factor** | *(Search and query databases only)* Adds additional compute power to process your Search and Query workloads and boost your queries per second. See [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. | | ||||||||||
| | **Throughput** | Identifies maximum throughput for the database, which is specified in terms of operations per second (**Ops/sec**). See [Throughput]({{< relref "/operate/rc/databases/configuration/clustering#throughput" >}}) for more information. | | ||||||||||
| | **Dataset size (GB)** | The amount of data for your dataset. Specify small sizes as decimals of 1.0 GB; example: `0.1` GB (minimum). We calculate the total memory limit for you based on the other settings you choose for your database. | | ||||||||||
| | **Advanced Capabilities** | [Advanced data types]({{< relref "/operate/rc/databases/configuration/advanced-capabilities" >}}) used by the database. Choose from [Search and query]({{< relref "/operate/oss_and_stack/stack-with-enterprise/search" >}}), [JSON]({{< relref "/operate/oss_and_stack/stack-with-enterprise/json" >}}), [Time series]({{< relref "/operate/oss_and_stack/stack-with-enterprise/timeseries" >}}), [Probabilistic]({{< relref "/operate/oss_and_stack/stack-with-enterprise/bloom" >}}), or [Graph (EOL)]({{< relref "/operate/oss_and_stack/stack-with-enterprise/deprecated-features/graph" >}}). <br/> Databases with Search and query have specific sizing requirements, see [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. | | ||||||||||
| | **Query performance factor** | *(Search and query databases only)* Adds additional compute power to process your query search and vector search workloads and boost your queries per second. See [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. | | ||||||||||
cmilesb marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||||||
| | **Query performance factor** | *(Search and query databases only)* Adds additional compute power to process your query search and vector search workloads and boost your queries per second. See [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. | | |
| | **Query performance factor** | *(Search and query databases only)* Adds additional compute power to process your search workloads and boost your queries per second. See [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
here is a tricky thing that we want to be clear about it. Search is different than query. Search means in general, full-text search capabilities, query entail aggregations and robust query language, and finally, vector search it's to clearly position ourselves in these segments (helping also on SEO, eventually). Likewise, documents aren't completely true since we have some document capabilities but we aren't a full-fledged documentDB.
Simplifying, search and query covers it all (but we miss the vector that we want to promote)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, then maybe spell it all out:
"...to process your search, both full-text and vector, and aggregation workloads..."
or something similar.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| | **Query performance factor** | *(Search and query databases only)* Adds additional compute power to process your query search and vector search workloads and boost your queries per second. See [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. | | |
| | **Query performance factor** | *(Search and query databases only)* Adds additional compute power to process your query and vector search workloads and boost your queries per second. See [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. | |
Uh oh!
There was an error while loading. Please reload this page.