[AV-41998] Couchbase Glossary#885
Conversation
| @@ -0,0 +1,479 @@ | |||
| = Couchbase Glossary | |||
There was a problem hiding this comment.
AsciiDoc apparently has a markup that's designed for glossaries — see Glossary. But it's not clear to me what the benefit of the [glossary] style is or why we would want to apply it. It may be useful if we want to apply specific styling just to the glossary. If that's not necessary we probably don't need it.
There was a problem hiding this comment.
I'm not sure if we have anything that takes advantage of that markup, or if the "book" features are even heavily used in our docs set now? Might be worth a look, might be worth considering, I'm just not sure we're set up for it right now.
| ACID stands for Atomicity, Consistency, Isolation, and Durability. | ||
| Couchbase supports ACID transactions across multiple documents. | ||
|
|
||
| *Adaptive Index*:: An index type that adjusts its structure based on query patterns and data distribution, providing flexibility for evolving workloads. |
There was a problem hiding this comment.
💡 idea! Can we have anchors for each glossary term so that we can link to them from other parts of the documentation?
There was a problem hiding this comment.
Yes, agree we should do this!
(Probably easiest to do as a single post-process, once the list is agreed, to give the LLM less to worry about)
There was a problem hiding this comment.
Yup would love to do this.
Co-authored-by: Simon Dew <39966290+simon-dew@users.noreply.github.com>
I've committed your suggestions for now - please make sure to come back and add links to further explanations! |
rakhi-prathap
left a comment
There was a problem hiding this comment.
@sarahlwelton - Looking at the A-Z Word List, I'm wondering if we could try a similar layout for the glossary too. It seems more readable and easy to scan. Just a thought for later!
Good idea! Definitely something we can see about getting set up, if we want to move away from the classic description list format - this was just AI's first attempt at formatting :) @simon-dew , if we do that, I'm not sure that we'd be able to take advantage of the |
Rebecca-Martinez007
left a comment
There was a problem hiding this comment.
Adding in some suggestions. I'll need to re-review to include links to more of the definitions.
| Collection:: A logical container within a scope that stores related JSON documents. | ||
| Collections provide data organization similar to tables in relational databases and serve as the unit of authorization and resource allocation. | ||
|
|
||
| Columnar Collection:: A collection in Capella Analytics optimized for columnar storage, suitable for analytical workloads with efficient storage and query processing. |
There was a problem hiding this comment.
Just something I noticed, do we still say "Columnar Collection"? CC: @zeba-shireen
|
|
||
| == C | ||
|
|
||
| Capella:: Couchbase's fully managed database-as-a-service (DBaaS) platform that runs on cloud infrastructure (AWS, Azure, GCP), providing operational databases, analytics, App Services, and AI capabilities without requiring server management. |
There was a problem hiding this comment.
| Capella:: Couchbase's fully managed database-as-a-service (DBaaS) platform that runs on cloud infrastructure (AWS, Azure, GCP), providing operational databases, analytics, App Services, and AI capabilities without requiring server management. | |
| Capella:: Couchbase's fully managed database-as-a-service (DBaaS) platform that runs on cloud infrastructure (AWS, Azure, GCP), providing operational clusters, analytics, App Services, and AI capabilities without requiring server management. |
There was a problem hiding this comment.
I don't think I quite want to make this change when we're trying to introduce people to the concepts of Couchbase. Let me think on it a bit more.
|
|
||
| Primary Index:: An index covering all documents in a collection using the document key, enabling queries without secondary indexes and supporting full collection scans. | ||
|
|
||
| Private Endpoint:: A network interface for accessing Capella services through private network connections rather than the public Internet, enhancing security and performance. |
There was a problem hiding this comment.
| Private Endpoint:: A network interface for accessing Capella services through private network connections rather than the public Internet, enhancing security and performance. | |
| Private Endpoint:: A network interface for accessing Capella services through private network connections rather than the public Internet, enhancing security and performance. | |
| Private connectivity is provided through each cloud provider’s native private endpoint technology, including AWS PrivateLink on Amazon Web Services, Azure Private Link on Microsoft Azure, and Private Service Connect on Google Cloud Platform. |
There was a problem hiding this comment.
Can we say "Cloud Service Provider" instead of "cloud provider"?
|
|
||
| == Q | ||
|
|
||
| Query:: The Couchbase service that executes SQL++ queries for data retrieval and manipulation, providing powerful querying capabilities across JSON documents. |
There was a problem hiding this comment.
| Query:: The Couchbase service that executes SQL++ queries for data retrieval and manipulation, providing powerful querying capabilities across JSON documents. | |
| Query:: A specific SQL++ statement used to retrieve, filter, aggregate, or manipulate data stored within JSON documents. |
There was a problem hiding this comment.
Can we use the {sqlpp} attribute please?
|
|
||
| Query Plan:: The execution strategy generated by the Query Service for a SQL++ query, showing how the query is executed and which indexes are used. | ||
|
|
||
| Query Service:: See Query. |
There was a problem hiding this comment.
| Query Service:: See Query. | |
| Query Service:: The Couchbase service that executes SQL++ queries for data retrieval and manipulation, providing powerful querying capabilities across JSON documents. |
There was a problem hiding this comment.
Attribute, please.
|
|
||
| SDK (Software Development Kit):: Client libraries and tools that enable applications to connect to and interact with Couchbase, available for Java, .NET, Python, Node.js, Go, C, C++, and other languages. | ||
|
|
||
| Search:: The Couchbase service providing full-text search, geospatial search, and vector search capabilities with linguistic analysis and relevance scoring. |
There was a problem hiding this comment.
| Search:: The Couchbase service providing full-text search, geospatial search, and vector search capabilities with linguistic analysis and relevance scoring. | |
| Search:: A full-text query performed against a search index to identify and retrieve documents based on unstructured text content, linguistic analysis, or specific field patterns. |
There was a problem hiding this comment.
Let me tweak this one. Ignoring for now.
|
|
||
| Search Index:: An index designed for full-text and vector search, supporting text analysis, custom analyzers, geospatial queries, and complex search operations. | ||
|
|
||
| Search Service:: See Search. |
There was a problem hiding this comment.
| Search Service:: See Search. | |
| Search Service:: The Couchbase service providing full-text search, geospatial search, and vector search capabilities with linguistic analysis and relevance scoring. |
There was a problem hiding this comment.
Again, I will tweak this one, ignoring for now.
|
|
||
| Workflow:: In Capella AI Services, a coordinated set of operations for data processing and vectorization, automating AI pipeline tasks. | ||
|
|
||
| Workbench:: See Query Workbench. |
There was a problem hiding this comment.
I'm wondering if we should just remove this?
There was a problem hiding this comment.
I think I'm okay with leaving this until we make sure everything uses the same, consistent terms everywhere.
simon-dew
left a comment
There was a problem hiding this comment.
please make sure to come back and add links to further explanations!
As requested, some links for more information.
|
|
||
| Namespace:: The highest level in the hierarchical organization of data in Couchbase. | ||
| Two namespaces are available: `default` and `system`. | ||
| Buckets, scopes, and collections are stored in the `default` namespace. |
There was a problem hiding this comment.
This is a link to the Server docs. I'm not sure if that's the best place as it's equally applicable to Capella?
| Buckets, scopes, and collections are stored in the `default` namespace. | |
| Buckets, scopes, and collections are stored in the `default` namespace. | |
| For more information, see xref:server:n1ql:n1ql-intro/queriesandresults.adoc#logical-hierarchy[Logical Hierarchy]. |
There was a problem hiding this comment.
We could always just link to both, instead.
Co-authored-by: Simon Dew <39966290+simon-dew@users.noreply.github.com> Co-authored-by: Rebecca Martinez <167447972+Rebecca-Martinez007@users.noreply.github.com>
Creating glossary.adoc.
Exact location in nav TBD, pending review from entire team + stakeholders.