The following features, which were supported with Search and Insight Engine 2.x and Search Services 2.x (Solr) are not supported in the 3.1 release for Search Enterprise 3.x (Elasticsearch).
Indexing
- Indexing of nodes created during content repository bootstrap. For example, the sample site data.
Search features
- Aspect queries (it works only using exact aspect name)
- Highlighting
- Fingerprinting
- Multi-lingual support (documents will be accepted and searchable with multiple languages, but only English grammar rules will be applied)
- Template search
- Resource limiting
- Scoped search
- Statistics
Search Syntax
- Fuzzy matching
- Search for spans and positions
- Search for boosts
- Wildcards in phrase queries
- Field Facets Pagination
- Field Facets Tags Exclusion
Field Queries
- PATHWITHREPEATS
- PNAME
- ANAME
- NPATH
- PARENT
- PRIMARYPARENT
- QNAME
- ANCESTOR
- PRIMARYASSOCQNAME
- PRIMARYASSOCTYPEQNAME
- ISNULL
- ISNOTNULL
- ISUNSET
- FINGERPRINT
- ISROOT
- ISCONTAINER
- CASCADETX
- DBID
- TX
- TXID
- INTXID
- TXCOMMITTIME
- ACLID
- INACLTXID
- ACLTXID
- ACLTXCOMMITTIME
- TENANT
- OWNERSET
- READERSET
- AUTHSET
- DENYSET
- FTSSTATUS
Path Indexing
- Secondary paths (paths including secondary parents)
Behavior of unsupported fields
Supplying an unsupported or non-existent field will cause a query to fail. This is a change in behavior from Search and Insight Engine and Search Services, which silently ignore these issues.
Search Enterprise focuses on the most commonly used features, and in some cases allows you to work around unsupported features. The following are examples of how to use different fields for queries:
| Old Query | Replacement Query |
|---|---|
| QNAME:’comment’ | TYPE:’fm:post’ |
| PNAME:’0/wiki’ | PATH:’//cm:wiki/*’ |
| NPATH:’2/Company Home/Sites/swsdp’ | PATH: ‘/app:company_home/st:sites/cm:swsdp//*’ |
Note: Secondary paths and secondary parents are not supported at this time, so there may still be some differences if these are in use.
Query languages
- CMIS query language
- SQL query language using JDBC Driver
Tools & Components
- Alfresco Search and Insight Engine
- Alfresco Governance Services
- Alfresco Federation Services
- Alfresco Intelligence Services
- Alfresco Content Connector for AWS Glacier
- Alfresco Content Connector for Salesforce
- Alfresco Content Connector for SAP applications
- Alfresco Collaboration Connector for Microsoft 365
- Alfresco Outlook Integration
- Alfresco Office Services
- Alfresco Google Docs Integration
- Alfresco Enterprise Viewer
- Alfresco Content Accelerator
Unsupported data types and properties
Data types and properties supported in Search and Insight Engine 2.x and Search Services 2.x that are not currently supported for Search Enterprise 3.1.
- http://www.alfresco.org/model/cmis/1.0/cs01}id
- http://www.alfresco.org/model/dictionary/1.0}any
- http://www.alfresco.org/model/dictionary/1.0}assocref
- http://www.alfresco.org/model/dictionary/1.0}category
- http://www.alfresco.org/model/dictionary/1.0}childassocref
- http://www.alfresco.org/model/dictionary/1.0}locale
- http://www.alfresco.org/model/dictionary/1.0}noderef
- http://www.alfresco.org/model/dictionary/1.0}qname