You are here:
Search Index Reference
Data 360 search supports many different file formats with unstructured data, embedding models, and pre-filter operations on search results.
Required Editions
| Available in: All Editions supported by Data 360. See Data 360 edition availability. |
Supported Embedding Models
Data 360 supports these embedding models.
| Model | Modality | Max Sequence/Input length |
|---|---|---|
| E5-large-v2 | Text | 512 tokens |
| Multilingual-E5-large | Text | 512 tokens |
| Whisper-Large-V3 | Audio | 30 seconds |
| SFR-v2-small | Text | 8,000 tokens |
Supported File Formats for Unstructured Data
Data 360 supports several file formats for unstructured data and search index configurations. See Unstructured Data File Formats and Connectors for details.
Supported Operators
Enhance your search queries with pre-filtering fields. Use logical operators and manage case sensitivity for field names and values to ensure precise data retrieval.
Search Index Considerations
Note these limitations when working with search indexes.
- Search index supports only UTF-8 encoding. Multilingual content must use UTF-8 encoding.
- Search Indexes aren't supported when platform encryption is turned on.
- Search indexes don’t support Developer Edition orgs if namespaces are enabled in those orgs.
- If you’re creating a search index for unstructured data that you’ve connected from an external blob store to Data 360, ensure you have set up a file notification pipeline.
- A DMO that has mappings from one or more external DLOs can only be used as the data source if caching is enabled for all those external DLOs. For more information see, Caching in Data Federation.
- Search Indexes don't support date and datetime fields for chunking. Only numerical and text fields are available for chunking data.
Did this article solve your issue?
Let us know so we can improve!

