mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-28 17:34:17 -04:00
* delete asciidoc files
* add migrated files
* fix errors
* Disable docs tests
* Clarify release notes page titles
* Revert "Clarify release notes page titles"
This reverts commit 8be688648d
.
* Comment out edternal URI images
* Clean up query languages landing pages, link to conceptual docs
* Add .md to url
* Fixes inference processor nesting.
---------
Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
Co-authored-by: Liam Thompson <leemthompo@gmail.com>
Co-authored-by: Martijn Laarman <Mpdreamz@gmail.com>
Co-authored-by: István Zoltán Szabó <szabosteve@gmail.com>
1.5 KiB
1.5 KiB
Frozen Indices [sql-index-frozen]
By default, Elasticsearch SQL doesn’t search frozen indices. To search frozen indices, use one of the following features:
- dedicated configuration parameter
- Set to
true
propertiesindex_include_frozen
in the SQL search API orindex.include.frozen
in the drivers to include frozen indices. - dedicated keyword
- Explicitly perform the inclusion through the dedicated
FROZEN
keyword in theFROM
clause orINCLUDE FROZEN
in theSHOW
commands:
SHOW TABLES INCLUDE FROZEN;
catalog | name | type | kind
---------------+---------------+----------+---------------
javaRestTest |archive |TABLE |FROZEN INDEX
javaRestTest |emp |TABLE |INDEX
javaRestTest |employees |VIEW |ALIAS
javaRestTest |library |TABLE |INDEX
SELECT * FROM FROZEN archive LIMIT 1;
author | name | page_count | release_date
-----------------+--------------------+---------------+--------------------
James S.A. Corey |Leviathan Wakes |561 |2011-06-02T00:00:00Z
Unless enabled, frozen indices are completely ignored; it is as if they do not exist and as such, queries ran against them are likely to fail.