Found 98 results for "getting-started index"

The search executed in 6.21023E-4 seconds. That's fast.

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: 2.6095803

Gitana / 3.2 / Guide / Guide / Branches / Custom Indexes

Custom 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: 2.5709946

Gitana / 4.0 / Data Engine / Branches / Custom Indexes

Custom 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: 2.5709946

Gitana / 3.2 / Guide / Guide / Features / Indexable

Indexable 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: 2.5075912

Gitana / 4.0 / Data Engine / Aspects / Indexable

Indexable 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: 2.5075912

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.3017495

Query Performance

Application 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: 2.2982502

Gitana / 3.2 / Guide / Guide / Docker / Maintenance / Upgrades

Upgrades 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.1892745

Gitana / 4.0 / Self Managed / Maintenance / Upgrades

Upgrades 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.1892745

Gitana / 3.2 / Guide / Guide / User Interface / Projects / Deleted Items

Deleted Items Cloud CMS provides a "copy on write" mechanism for any creates, updates or deletes to the content in a branch. This means that whenever you delete something, you're actually masking it as deleted. The content itself is never destroyed or removed permanently. As such, it is always possible walk backwards in time and discover content that was deleted - all the way back to the moment when your branch or repository was created. To make things easier, Cloud CMS provides a "deletions" in

Score: 1.9396787

Gitana / 4.0 / User Interface / Projects / Deleted Items

Deleted Items Cloud CMS provides a "copy on write" mechanism for any creates, updates or deletes to the content in a branch. This means that whenever you delete something, you're actually masking it as deleted. The content itself is never destroyed or removed permanently. As such, it is always possible walk backwards in time and discover content that was deleted - all the way back to the moment when your branch or repository was created. To make things easier, Cloud CMS provides a "deletions" in

Score: 1.9396787

Gitana / 3.2 / Guide / Guide / Application Server / Services / Web Content Management

Web Content Management Whether to support dynamic loading of web pages from Cloud CMS. This enables the Cloud CMS web content management solution. Here is what a full configuration set looks like: { "wcm": { "enabled": true, "cache": true, "cacheKey": { "params": { "includes": [], "excludes": [], "excludeAll": false } }, "pageCacheTTL": (24 * 60 * 60) * 1000, // 24 hours "p

Score: 1.8308598

Gitana / 4.0 / Developers / Application Server / Services / Web Content Management

Web Content Management Whether to support dynamic loading of web pages from Cloud CMS. This enables the Cloud CMS web content management solution. Here is what a full configuration set looks like: { "wcm": { "enabled": true, "cache": true, "cacheKey": { "params": { "includes": [], "excludes": [], "excludeAll": false } }, "pageCacheTTL": (24 * 60 * 60) * 1000, // 24 hours "p

Score: 1.8308598

Gitana / 3.2 / Guide / Guide / Search

Search 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: 1.8068987

Gitana / 4.0 / Data Engine / Discovery / Search

Search 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: 1.8068987

Pagination options

You can specify pagination options in an optional second argument to the queryNodes function, basically like this: Chain(branch).queryNodes({  "_type": "video:essentials"  }, {  "sort": {  "title": -1  },  "limit": 10,  "skip": 30  }).then(function() {  ...  }); In this example, the results will start at index 30 in the record set and will contain the next 10 entries. The record set is sorted by "title" in a descending order ahead of being returned. If pagination sort isn't provided, then the o

Score: 1.7823439

Gitana / 3.2 / Guide / Guide / Command Line

Command 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.6603354

Gitana / 4.0 / Developers / Command Line Interface / Overview

Command 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.6603354

Gitana / 3.2 / Guide / Guide / API / Pagination

Pagination Pagination allows you to control the result set that comes back from Cloud CMS for any operations that produce a list of items. It is called pagination because it gives you a way to organize your record set into pages and then get those pages back, one at a time. Pagination gives you a way to adjust the result set before it is sent over the wire (and back to you) so that you can have smaller "paged" payloads. Pagination is useful because, most of the time, unless the result set is ver

Score: 1.5772985

Gitana / 4.0 / Data Engine / API / Pagination

Pagination Pagination allows you to control the result set that comes back from Cloud CMS for any operations that produce a list of items. It is called pagination because it gives you a way to organize your record set into pages and then get those pages back, one at a time. Pagination gives you a way to adjust the result set before it is sent over the wire (and back to you) so that you can have smaller "paged" payloads. Pagination is useful because, most of the time, unless the result set is ver

Score: 1.5772985

Gitana / 3.2 / Guide / Guide / User Interface / Search

Search Content is automatically indexed when it is created, modified, or uploaded in Cloud CMS. The index is across the Content properties and any attached file eg Word, PDF,.. Platform At Platform level you can search for Content across all projects subject to your access permissions. Project Search at Project level provides more options and is configurable: Project Search Settings Search for a Project can be configured. go to Project Settings (left nav). Note: To have the Project Settings as a

Score: 1.466894

Gitana / 4.0 / User Interface / User Interface / Search

Search Content is automatically indexed when it is created, modified, or uploaded in Cloud CMS. The index is across the Content properties and any attached file eg Word, PDF,.. Platform At Platform level you can search for Content across all projects subject to your access permissions. Project Search at Project level provides more options and is configurable: Project Search Settings Search for a Project can be configured. go to Project Settings (left nav). Note: To have the Project Settings as a

Score: 1.466894

Gitana / 4.0 / Forms / API / Templates

Templates Alpaca includes an advanced templating system that is driven by views. You can create your own views and templates at compile time (when you actually build Alpaca) or you can override them on the fly at runtime. Templates can be supplied either as inline functions (which are discovered if you've built them at compile time), as URLs (which are loaded at runtime), as DOM references (which are then sourced) or as HTML strings. In the latter two cases, the templates are acquired and then c

Score: 1.4297922

Gitana / 4.0 / Forms / Fields / Object Field

Object Field The object field. Properties Title Object Description Object field for containing other fields Field Type object Base Field Type container Schema Property Type Default Description maxProperties number The maximum number of properties that this object is allowed to have minProperties number The minimum number of properties that this object is required to have properties object List of child properties. Options Property Type Default Description animate boolean true Up and down transit

Score: 1.4190553

Gitana / 4.0 / Forms / API / Lookups

Lookups Alpaca provides abstractions for forms, fields, connectors and other types so as to provide a consistent and easy-to-use interface. This interface lets you find other objects in the JSON structure and plug in function handlers that make decisions by drawing from values of other fields. Every field that renders fundamentally receives an ID. The ID is a dynamically assigned value of no particular significance other than that it is unique. Typically, it is something like alpaca123. Each fie

Score: 1.1868254