[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-11(UTC)"],[],[],null,["Full-text search\n\nMost apps allow users to search app content. For example, you may want to search\nfor posts containing a certain word or notes you've written about a specific\ntopic.\n\nFirestore doesn't support native indexing or search for\ntext fields in documents. Additionally, downloading an entire collection to\nsearch for fields client-side isn't practical.\n\nTo enable full text search of your Firestore data, use a dedicated\nthird-party search service. These services provide advanced indexing and search\ncapabilities far beyond what any simple database query can offer.\n\nBefore continuing, research then choose one of the search providers below:\n\n- [Elastic](https://www.elastic.co/app-search/)\n- [Algolia](https://www.algolia.com/)\n- [Typesense](https://typesense.org/)\n\nSolution: External search service \nElastic Algolia Typesense"]]