> ## Documentation Index > Fetch the complete documentation index at: https://doc.lucidworks.com/llms.txt > Use this file to discover all available pages before exploring further. # Lucidworks Search export const LwTemplate = ({title = "Key questions to get you started", icon = "sparkles", cta = "Powered by Agent Studio", linkHref = "https://lucidworks.com/demo/?utm_source=docs&utm_medium=referral&utm_campaign=docs_cta_ai"}) => { const [isLoaded, setIsLoaded] = useState(false); useEffect(() => { const timer = setTimeout(() => { setIsLoaded(true); }, 500); return () => clearTimeout(timer); }, []); return
{isLoaded && ` }} />} Powered by Lucidworks Agent Studio
; }; [localhost link]: http://localhost:3000/docs/lucidworks-search/overview [mintlify link]: https://doc.lucidworks.com/docs/lucidworks-search/overview [old doc.lw link]: https://doc.lucidworks.com/managed-fusion/5.9/ckqr0j Lucidworks Search is a search and machine learning platform that lets you deploy AI-powered data discovery and search applications in a modern, containerized, cloud-native architecture. It can index billions of documents from any data source and process thousands of queries per second from thousands of concurrent users. Lucidworks Search integrates with popular machine learning frameworks, making it easy to build and deploy AI-powered applications. **FAQ** **How is Lucidworks Search different from Fusion?** Lucidworks takes care of deployments, upgrades, and high availability for your Lucidworks Search instance. Additionally, some features and capabilities may be available only in Fusion or only in Lucidworks Search. For more information on the key differences between Lucidworks Search and Fusion, see [Lucidworks Search versus Fusion](/docs/lucidworks-search/02-lucidworks-search-vs-fusion/overview). ## Features ### Connectors Lucidworks Search offers dozens of connectors so you can access your data from a large number of sources, including [Amazon AWS S3](/docs/fusion-connectors/connectors/amazon-aws-s3-v2), [SharePoint](/docs/fusion-connectors/connectors/sharepoint-v2-optimized), or almost [any website](/docs/fusion-connectors/connectors/web-v2). Your data moves through the [indexing Data Flow](/docs/lucidworks-search/04-move-data-in/overview), where it is transformed to meet the specific needs of your use case. To learn more about Lucidworks Search connectors, see [Lucidworks Connectors](/docs/fusion-connectors/overview). ### Signals Signals are recorded user events that provide insights on user behavior. Almost any user event can be captured as a signal, including when a user clicks a search result, adds an item to their cart, or makes a purchase. Lucidworks Search uses signals to improve search result relevancy and deliver the right results to the right users. For more information on signals, see [Signals](/docs/lucidworks-search/07-improve-your-queries/signals/overview). ### Rules Rules are manually created formulas for rewriting queries. This is the most versatile strategy for creating custom query rewrites. It supports a variety of conditions and actions to address a wide range of use cases. Use rules to boost, bury, or block results to customize your search experience, or take it further with other rule actions. For more information on rules, see [Business rules](/docs/lucidworks-search/07-improve-your-queries/business-rules/overview). ### Recommendations Create personalized recommendations for users based on signals data, even if they have not performed a search. Use these recommendations with search-driven assets to drive users to the most relevant content. * **Items-for-item.** Customers shopping for bicycles may be interested in more items, such as a helmet and bike lock. Use items-for-items recommendations to surface those items for them. * **Items-for-query.** Sometimes, semantic relevance is not the same as user relevance. Items-for-query recommendations show items commonly associated with a query, based on user behavior. * **Items-for-user.** Winter clothing needs are different for customers in Arizona versus Alaska. Items-for-user recommendations help each customer find what works best for them. * **Queries-for-query.** Help users who are not finding the right words. Queries-for-query recommendations show queries that are related to the current query. * **Trending items and queries.** Show items that have been popular lately, so customers can see the latest and greatest. * **Users-for-item.** Find which users have interacted with specific items, and reach out with your marketing campaign. For more information on recommendations, see [Recommendations](/docs/lucidworks-search/07-improve-your-queries/recommendations/overview). ### Search curation Predictive Merchandiser and Experience Optimizer are AI-powered tools that provide insights, customer recommendations, and search optimization. Predictive Merchandiser is designed for product discovery, such as ecommerce. Experience Optimizer is designed for knowledge management. For example, a site providing news, information, or documentation. For more information on these tools, see [Curate your search experience](/docs/lucidworks-search/07-improve-your-queries/curate-search-experience/overview). ## Technology Lucidworks Search builds upon trusted technology that makes it reliable, secure, fast, and effective. Major components of its technology stack include Kubernetes, Solr, Spark, and ZooKeeper. **Kubernetes** Kubernetes is a container orchestration service used for deploying, scaling, and managing distributed applications. Lucidworks Search uses Google Kubernetes Engine (GKE) and benefits from Google’s global infrastructure, security, and support. **Apache Solr** Solr is a highly reliable and scalable search platform. Lucidworks Search uses Solr to index and query billions of documents and serve millions of users. **Apache Spark** Spark is an analytics engine used by Lucidworks Search for large-scale data processing. This includes processing millions of signals and generating recommendations. **Apache ZooKeeper** ZooKeeper is a distributed configuration service that Lucidworks Search uses to configure your components and keep them consistent within your deployment. ## About this documentation Lucidworks' documentation is written to inform and instruct all users on product features and capabilities. If you want to leave feedback for the Documentation team, use the feedback widget or send an email to [docs@lucidworks.com](mailto:docs@lucidworks.com). **Document types** Lucidworks documentation is categorized by document type, which is indicated under the title and on each search result. The following are descriptions of each document type: * **Concept:** A concept article provides a high-level, less technical overview of a topic. * **Reference:** A reference article provides technical details, such as configuration specifications. * **How-to:** A how-to article provides step-by-step instructions for completing a task. * **Release note:** Release notes describe the latest developments in Lucidworks Search. ## Support Lucidworks provides technical support to customers 24 hours a day, 7 days a week, with unlimited incidents. You can open a support case at any time. Before doing so, complete the instructions found in the [Technical Support](/docs/policies/technical-support) policy. ## LucidAcademy The learning path for **Managing Fusion** focuses on how to navigate the available technical support and resources for Lucidworks Search. ## Learn more ## Technical support When you need personalized, expert assistance, the Lucidworks technical support team is available 24/7. Before you open a support case, see the instructions below to learn how to gather data that the technical support team can use to evaluate your issue and provide a solution. Once you have obtained the relevant data from Fusion, [Submit a request](https://support.lucidworks.com/hc/en-us/requests/new). The course for **Support Portal Overview** focuses on how to navigate the support portal, open a support ticket, identify the severity of your issue, and escalate issues as needed. ### Finding log files in the filesystem Log files are located in the `https://FUSION_HOST:FUSION_PORT/var/log` directory. Generally, the log files below are the most useful in diagnosing an issue: * API logs `https://FUSION_HOST:FUSION_PORT/var/log/api/api.log` and `https://FUSION_HOST:FUSION_PORT/var/log/api/gc_.log.0.current` * Connectors logs `https://FUSION_HOST:FUSION_PORT/var/log/connectors-classic/connectors-classic.log` and `https://FUSION_HOST:FUSION_PORT/var/log/connectors-rpc/connectors-rpc.log` If it is apparent that additional components are involved, collect their logs and associated `gc` logs from the `https://FUSION_HOST:FUSION_PORT/var/log` directory. ### Opening a support case Lucidworks provides technical support to customers 24 hours a day, 7 days a week, with unlimited incidents. Once you have obtained the relevant data from Fusion as described above, you can open a support case. For detailed information about submitting a support case, see [Lucidworks Customer Center Training](https://support.lucidworks.com/hc/en-us/articles/360049594894-Lucidworks-Customer-Center-Training). To open a support case, complete the following: 1. Access the [Lucidworks Submit a request page](https://support.lucidworks.com/hc/en-us/requests/new).\ You can also select **Contact Support** from any page on the Lucidworks support site. 2. Enter information in the following fields: * **Your email address** * **Subject** * **Description** 3. In the **Severity** field, select the appropriate severity value for your issue according to the guidelines below. | Severity | Time | Definition | Example | | -------- | -------- | -------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | | S1 | 1 Hour | Severe commercial impact on Customer 's business which either makes the system inoperable or prevents content discovery. | Production search is down. | | S2 | 12 Hours | Significant commercial impact on Customer 's business which makes one or more critical areas of functionality inoperable. | Search performance has slowed down to a crawl. | | S3 | 24 Hours | Moderate commercial impact on Customer 's business which makes one or more non-critical areas of functionality inoperable. | Slight increase in query time. | | S4 | 48 Hours | No commercial impact on Customer 's business. | How to implement a certain search feature. | 4. Select values in the following fields: * **Product Line** * **Fusion Version** (optional) * **Solr Version** (optional) 5. In the **Environment** field, select one of the following: * **Dev/Sandbox/POC** * **Performance** * **Production** * **QA/UAT** * **Staging** 6. In the **Attachments** field, drag files or click to add [log files](#finding-log-files-in-the-filesystem). You can attach only one file. Upload all of your files as one `.tar` or `.zip` archive. 7. When you have attached all pertinent data, click **Submit**. You will receive an email message containing your case number. A Lucidworks support engineer will contact you within the time period corresponding to your issue’s severity level.