Alfresco官方支持搜索语言咨询及solr-alfresco生命周期确认

Hey there, let's break down your questions about Alfresco's query languages one by one, based on my hands-on experience with Alfresco deployments:

1. Officially Supported Search Languages in Alfresco #

Alfresco officially endorses and documents these core query languages:

• fts-alfresco: The recommended advanced full-text search language. It’s engine-agnostic, automatically switching between Solr or DB-AFTS based on your system configuration and query needs.
• cmis-alfresco: An Alfresco-specific extension of the standard CMIS query language, adding support for Alfresco-exclusive properties and behaviors.
• Standard CMIS Query: The CMIS-compliant base query language, which works across any CMIS-compatible repository (not limited to Alfresco).

2. Long-Term Availability of solr-alfresco #

Let’s clear up the rumor first: solr-alfresco isn’t an "unofficial" language—it’s a lower-level query syntax tied directly to Alfresco’s Solr integration. That said, Alfresco’s official guidance has always prioritized fts-alfresco as the go-to choice for developers and end users, since it abstracts away underlying search engine specifics.

For long-term viability:

• Right now, solr-alfresco is still present in all supported Alfresco versions (cloud and on-prem) because many legacy systems and internal Alfresco processes depend on it.
• That being said, Alfresco’s roadmap focuses on consolidating around fts-alfresco as the single, unified query interface. There’s no immediate plan to remove solr-alfresco, but it’s not getting active feature updates. If your system relies heavily on it, I’d recommend starting a gradual migration to fts-alfresco—it’ll keep you aligned with future updates and engine changes.

3. Result Limit Differences Between Query Languages #

Your observation about result limits is spot-on, with a bit of extra context:

• fts-alfresco, cmis-alfresco, and solr-cmis: These languages respect Alfresco’s default global result limit (usually 1000 entries) set in configuration. Even with pagination, you can’t fetch results beyond this limit unless you adjust relevant settings (like alfresco.search.maxResults in Alfresco or Solr’s query.maxResults). This is a intentional guardrail to avoid performance hits from oversized result sets.
• solr-alfresco and solr-fts-alfresco: These languages bypass the global Alfresco-level limit by default, letting you paginate through all matching documents. This is because they interact directly with Solr’s native query capabilities, without the abstraction layer that enforces the global limit.

A quick heads-up: While you can raise the global limit for other languages, be careful—setting it too high can hurt performance, especially on large repositories.

内容的提问来源于stack exchange，提问作者Ekaterina Ivanova iceja.net