Found 26 results for "content-services indexes"
The search executed in 0.001077473 seconds. That's fast.
Gitana / 3.2 / Guide / Guide / Branches / Custom IndexesCustom Indexes Cloud CMS internally maintains indexes to improve the speed of your data lookups across all data store types. In most cases, there is no need to concern yourself with these as they deliver optimal performance. With respect to content repositories, however, Cloud CMS allows you to define custom database indexes on a per-branch basis. These custom indexes add to the default set that Cloud CMS automatically maintains. Each branch and/or snapshot maintains its own "tip" collection tha
Score: 9.402846
|
|
Gitana / 4.0 / Data Engine / Branches / Custom IndexesCustom Indexes Cloud CMS internally maintains indexes to improve the speed of your data lookups across all data store types. In most cases, there is no need to concern yourself with these as they deliver optimal performance. With respect to content repositories, however, Cloud CMS allows you to define custom database indexes on a per-branch basis. These custom indexes add to the default set that Cloud CMS automatically maintains. Each branch and/or snapshot maintains its own "tip" collection tha
Score: 9.402846
|
|
Query PerformanceApplication queries Application code which consumes Cloud CMS content typically runs query API calls. These queries can be optimized in the following ways: Request only the properties needed When an application requires only a few properties from a set of nodes you should use “_fields” to limit the properties returned. This can drastically reduce the size of the payload and therefore the response time. In this example, we only need “_doc”, “title” and “_type” so these are the only fields that wi
Score: 3.3609488
|
|
Gitana / 3.2 / Guide / Guide / Features / IndexableIndexable QName: f:indexable Informs a node of how it should be indexed. Cloud CMS maintains multiple indexes including a search index, a database index and special indexes for things like path-based retrieval. By default, all n:node instances have the f:indexable feature applied to them. The default behavior is for search to be enabled and for search-indexes to be updated synchronously upon a write. Nodes that are indexed for search will take a little extra time on write (create or update) sinc
Score: 3.1186123
|
|
Gitana / 4.0 / Data Engine / Aspects / IndexableIndexable QName: f:indexable Informs a node of how it should be indexed. Cloud CMS maintains multiple indexes including a search index, a database index and special indexes for things like path-based retrieval. By default, all n:node instances have the f:indexable feature applied to them. The default behavior is for search to be enabled and for search-indexes to be updated synchronously upon a write. Nodes that are indexed for search will take a little extra time on write (create or update) sinc
Score: 3.1186123
|
|
Gitana / 3.2 / Guide / Guide / Docker / Maintenance / UpgradesUpgrades This document provides technical guidance for upgrades. Upgrade to Cloud CMS Version 3.2 The Elastic Search version in this release has been updated from 1.7.1 to 6.2.4. Steps to follow to set up Docker 3.2: Download the Docker release 3.2 here. Download the Zip or Tar file of Elastic Search 6.2.4 here and then Unzip the package. Unzip the Docker release package, Create a new folder and paste the kit you use from the package. You can also replace your existing kit with the new release's
Score: 2.8722677
|
|
Gitana / 4.0 / Self Managed / Maintenance / UpgradesUpgrades This document provides technical guidance for upgrades. Upgrade to Cloud CMS Version 3.2 The Elastic Search version in this release has been updated from 1.7.1 to 6.2.4. Steps to follow to set up Docker 3.2: Download the Docker release 3.2 here. Download the Zip or Tar file of Elastic Search 6.2.4 here and then Unzip the package. Unzip the Docker release package, Create a new folder and paste the kit you use from the package. You can also replace your existing kit with the new release's
Score: 2.8722677
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / project-manage-contextproject-manage-context [ { "evaluator": "context-project", "config": { "project-manage-context": { "items": [ { "key": "project/manage/header", "title": "Manage", "order": 10000, "header": true, "allowAuthority": [ "collaborator", "manager" ], "items": [ { "key": "project/settings", "title": "Project Settin
Score: 2.8365736
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / project-manage-contextproject-manage-context [ { "evaluator": "context-project", "config": { "project-manage-context": { "items": [ { "key": "project/manage/header", "title": "Manage", "order": 10000, "header": true, "allowAuthority": [ "collaborator", "manager" ], "items": [ { "key": "project/settings", "title": "Project Settin
Score: 2.8365736
|
|
Gitana / 3.2 / Guide / Guide / SearchSearch Any content you put into Cloud CMS is automatically indexed for full-text and structured search. This lets your editorial teams instantly search for content and find the things they're looking for. Under the hood, Cloud CMS uses Elastic Search and makes available to your editorial users and developers the full syntax of the Elastic Search Query DSL. This allows you to execute simple searches as well as more complex queries that take into account term and phrase matching, nested operations
Score: 2.4912925
|
|
Gitana / 4.0 / Data Engine / Discovery / SearchSearch Any content you put into Cloud CMS is automatically indexed for full-text and structured search. This lets your editorial teams instantly search for content and find the things they're looking for. Under the hood, Cloud CMS uses Elastic Search and makes available to your editorial users and developers the full syntax of the Elastic Search Query DSL. This allows you to execute simple searches as well as more complex queries that take into account term and phrase matching, nested operations
Score: 2.4912925
|
|
Gitana / 3.2 / Guide / Guide / BranchesBranches Cloud CMS stands apart from just about every other content management product on the market in that it offers a versioning model that is based around changesets. It is inspired by Git and Mercurial which are popular source-control products within the software development world. As such, Cloud CMS provides a changeset versioning system that captures every touch - every create, update or delete - that you make. Nothing is ever lost. Every data operation is fully transactional with every t
Score: 2.3010182
|
|
Gitana / 4.0 / Data Engine / Branches / OverviewBranches Cloud CMS stands apart from just about every other content management product on the market in that it offers a versioning model that is based around changesets. It is inspired by Git and Mercurial which are popular source-control products within the software development world. As such, Cloud CMS provides a changeset versioning system that captures every touch - every create, update or delete - that you make. Nothing is ever lost. Every data operation is fully transactional with every t
Score: 2.3010182
|
|
How do I search for nested content?Cloud CMS maintains two indexes that are of interest for finding things. The primary index is the MongoDB index - against which you can run any query you can dream up using the MongoDB DSL. The secondary index is the Elastic Search index - against which you can run any search you can dream up using the Elastic Search DSL. For information all kinds of really powerful stuff you can do with this, see: https://www.cloudcms.com/documentation/content-services/query.html https://www.cloudcms.com/docume
Score: 2.1451755
|
|
Gitana / 3.2 / Guide / Guide / Command LineCommand Line The Cloud CMS command-line client gives developers a way to work with their Cloud CMS tenant projects, applications, data stores and other resources from the command line. The CLI (command-line client) is a Node.js based command line tool that is very easy to use and available at no charge. Note: A valid Cloud CMS subscription is required to connect to Cloud CMS with the command-line client. This subscription can be a paid subscription or a free trial account. Getting Started To get
Score: 1.9435282
|
|
Gitana / 4.0 / Developers / Command Line Interface / OverviewCommand Line The Cloud CMS command-line client gives developers a way to work with their Cloud CMS tenant projects, applications, data stores and other resources from the command line. The CLI (command-line client) is a Node.js based command line tool that is very easy to use and available at no charge. Note: A valid Cloud CMS subscription is required to connect to Cloud CMS with the command-line client. This subscription can be a paid subscription or a free trial account. Getting Started To get
Score: 1.9435282
|
|
Gitana / 3.2 / Guide / Guide / QueryQuery Cloud CMS provides SQL-like, structured query for all of your content. The platform uses MongoDB under the hood to store the JSON for your content. MongoDB offers a powerful, unmatched query engine so that you can execute complex lookups of your content to support both your editorial and runtime application needs. The platform also offers "composite" query operations which let you layer MongoDB queries on top of Elastic Search DSL searches and traversals around node objects. Cloud CMS auto
Score: 1.9288204
|
|
Gitana / 4.0 / Data Engine / Discovery / QueryQuery Cloud CMS provides SQL-like, structured query for all of your content. The platform uses MongoDB under the hood to store the JSON for your content. MongoDB offers a powerful, unmatched query engine so that you can execute complex lookups of your content to support both your editorial and runtime application needs. The platform also offers "composite" query operations which let you layer MongoDB queries on top of Elastic Search DSL searches and traversals around node objects. Cloud CMS auto
Score: 1.9288204
|
|
Automatic Extraction from AttachmentsWhen you upload files into Cloud CMS all kinds of interesting things happen. For example, Cloud CMS automatically indexes your files for full-text search. All of the textual content is discovered and made available so your editorial teams can instantly search and find things after uploading. Did you know that Cloud CMS can also automatically extract metadata about uploaded files and make that information available? This is done via the Cloud CMS f:extractable feature. When you upload files, Clou
Score: 1.8357449
|
|
What is the reason for "Failed to index node"?If you scan your log entries and see "Failed to index node", this indicates that Elastic Search failed to update its index for a node. Cloud CMS tells Elastic Search to updates its index whenever a node is created or updated. When a node is deleted, Cloud CMS tells Elastic Search to remove the node from its index. This error message means that Elastic Search failed to update the index and therefore the index wasn't updated. If you open up the error, you may see further information that indicates
Score: 1.7842703
|
|
Product Releases - GitanaProduct Releases - Gitana Status Releases Registry Blog Cloud CMS Platform Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Enterprise Data Engine Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Automate Automate your content creation and approval flows while taking advantage of AI services to enhance and c
Score: 1.2507582
|
|
Gitana / 3.2 / Guide / Guide / APIAPI The Cloud CMS API consists of an HTTP/HTTPS endpoint that uses OAuth 2.0 authentication. It supports both REST concepts and asynchronous data operations. You can access this API using any of our drivers as well as curl or any HTTP client library. Our API provides functionality that covers all aspects of content production, publishing and presentation. 100% of the functionality of Cloud CMS is accessible from the API, including: Content Models, Creation and Editing Workflow, Scheduled Publish
Score: 0.58559704
|
|
Gitana / 4.0 / Data Engine / API / OverviewAPI The Cloud CMS API consists of an HTTP/HTTPS endpoint that uses OAuth 2.0 authentication. It supports both REST concepts and asynchronous data operations. You can access this API using any of our drivers as well as curl or any HTTP client library. Our API provides functionality that covers all aspects of content production, publishing and presentation. 100% of the functionality of Cloud CMS is accessible from the API, including: Content Models, Creation and Editing Workflow, Scheduled Publish
Score: 0.58559704
|
|
Documentation: Developers - Overview - GitanaDocumentation: Developers - Overview - Gitana Status Releases Registry Blog Cloud CMS Platform Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Enterprise Data Engine Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Automate Automate your content creation and approval flows while taking advantage of AI servi
Score: 0.5273988
|
|
Gitana / 4.0 / Self Managed / Configuration / API ServerAPI Server The Cloud CMS API Server is a Java application that launches inside of a Java Servlet Container. The Java application surfaces a REST API as well as backend services and DAOs to support connectivity to Mongo DB, Elastic Search and a slew of Amazon services including S3, SNS, SQS, Route 53, Cloud Front and more. Properties File Cloud CMS is primarily configured via a properties file that is auto-detected and loaded when the underlying Spring Framework starts up. This properties file is
Score: 0.20795727
|