Commit Graph

468 Commits

Author SHA1 Message Date
James Rodewig 5772c1c7dd
[DOCS] [2 of 5] Change // CONSOLE comments to [source,console] (#46353) 2019-09-09 13:13:41 -04:00
David Turner 23155532d8
Add support for OneZoneInfrequentAccess storage (#46436)
The `repository-s3` plugin has supported a storage class of `onezone_ia` since
the SDK upgrade in #30723, but we do not test or document this fact. This
commit adds this storage class to the docs and adds a test to ensure that the
documented storage classes are all accepted by S3 too.

Fixes #30474
2019-09-09 07:54:02 +01:00
James Rodewig e43be90e6c
[DOCS] [5 of 5] Change // TESTRESPONSE comments to [source,console-results] (#46449) 2019-09-06 14:05:36 -04:00
James Rodewig 97802d8aff
[DOCS] Change // CONSOLE comments to [source,console] (#46441) 2019-09-06 10:55:16 -04:00
James Rodewig 466c59a4a7
[DOCS] Replace "// TESTRESPONSE" magic comments with "[source,console-result] (#46295) 2019-09-05 16:47:18 -04:00
Lisa Cawley 06c4c5cca3
[DOCS] Identify reloadable Azure repository plugin settings (#46358) 2019-09-05 10:44:21 -07:00
Lisa Cawley 7e112ca0f2
[DOCS] Identify reloadable GCS repository plugin settings (#46352) 2019-09-04 16:24:55 -07:00
Lisa Cawley f196e96bea
[DOCS] Identify reloadable S3 repository plugin settings (#46349) 2019-09-04 14:43:58 -07:00
Lisa Cawley 860aff0f37
[DOCS] Identify reloadable EC2 Discovery Plugin settings (#46102) 2019-09-04 10:12:03 -07:00
Jason Tedor 2ced1b00ea
Move plugin.mandatory to its own page
This commit takes the reworking of plugin.mandatory docs even farther by
taking this setting to its own page.
2019-08-30 11:00:42 -04:00
Jason Tedor 1be991de07
Move plugin.mandatory to installing plugins docs
This commit moves the plugin.mandatory settings from the plugin
directory page in the docs to the installing plugins page in the docs.
2019-08-30 10:29:57 -04:00
Jim Ferenczi d66a307599
Add support for inlined user dictionary in the Kuromoji plugin (#45489)
This change adds a new option called user_dictionary_rules to
Kuromoji's tokenizer. It can be used to set additional tokenization rules
to the Japanese tokenizer directly in the settings (instead of using a file).
This commit also adds a check that no rules are duplicated since this is not allowed
in the UserDictionary.

Closes #25343
2019-08-20 15:06:01 +02:00
Chris Dean 96a234e461
[DOCS] - Updating chunk_size values to fix size value notation. Chunksize41591 (#45552)
* changes to chunk_size #41591

* update to chunk size to include ` `

* Update docs/plugins/repository-azure.asciidoc

Co-Authored-By: James Rodewig <james.rodewig@elastic.co>

* Update docs/reference/modules/snapshots.asciidoc

Co-Authored-By: James Rodewig <james.rodewig@elastic.co>

* Update docs/plugins/repository-azure.asciidoc

Co-Authored-By: James Rodewig <james.rodewig@elastic.co>

* Update docs/plugins/repository-s3.asciidoc

Co-Authored-By: James Rodewig <james.rodewig@elastic.co>

* edits to fix passive voice
2019-08-14 13:47:07 -05:00
Bas ten Berge 05404803f0 [DOCS] Remove outdated 5.x community plugins (#40306)
Our docs previously included several community plugins that are only supported for versions 5.x and earlier. This removes those plugins for our 6.6+ docs.
2019-08-07 08:46:46 -04:00
David Turner 784d88617b Fix docs line length
Followup to #44617 that fixes some unexpected wrapping.
2019-07-19 17:03:05 +01:00
David Turner 8b05ac3607
Clarify repository-s3 defaulting to instance role (#44617)
Specifies more clearly that you can leave the client credential settings unset
if you want to use the instance or container role.
2019-07-19 16:07:54 +01:00
Jinhu Wu 6d70276af1 Add disable_chunked_encoding Setting to S3 Repo (#44052)
* Add disable_chunked_encoding setting to S3 repo plugin to support S3 implementations that don't support chunked encoding
2019-07-18 14:39:16 +02:00
surprisingb 73763cafab Update discovery-ec2 docs (#43693)
Fix `discovery.ec2.tag.TAGNAME` example with the correct parameter.
2019-07-11 12:57:59 +01:00
Peter Lieverdink 3fd477a87d Update the gcs chunk_size documentation. (#38749)
Remove `1g` from the examples, as the GCS repository chunk_size can be at most 100m.
2019-07-09 09:01:29 +02:00
Armin Braun d6e23e9bd5
Provide an Option to Use Path-Style-Access with S3 Repo (#41966)
* Provide an Option to Use Path-Style-Access with S3 Repo

* As discussed, added the option to use path style access back again and
deprecated it.
* Defaulted to `false`
* Added warning to docs

* Closes #41816
2019-07-04 17:37:47 +02:00
Armin Braun faffaa9b28
Add SAS Token Authentication Support to Azure Repo Plugin (#42982)
* Added setting for SAS token
* Added support for the token in tests
* Relates #42117
2019-06-11 15:50:05 +02:00
Mayya Sharipova 2eef9707cc
Improve documentation for smart_cn analyzer (#42822) 2019-06-10 06:26:56 -04:00
Andrei Stefan f715d722e8
Since SQL is GA, remove the sql language plugin from this list (#41533) 2019-06-10 09:00:39 +03:00
Christoph Büscher ffc5534584
[Docs] Clarify caveats for phonetic filters replace option (#42807)
The `replace` option in the phonetic token filter can have suprising side
effects, e.g. such as described in #26921. This PR adds a note to be mindful
about such scenarios and offers alternatives to using the `replace` option.

Closes #26921
2019-06-05 22:02:17 +02:00
Christoph Büscher f51db164fa
[Docs] Add example to reimplement stempel analyzer (#42676)
Adding an example of how to re-implement the polish stempel analyzer
in case a user want to modify or extend it. In order for the analyzer to be
able to use polish stopwords, also registering a polish_stop filter for the
stempel plugin.

Closes #13150
2019-06-03 13:22:10 +02:00
David Turner d589cad842
Rework discovery-ec2 docs (#41630)
This commit reworks and clarifies the docs for the `discovery-ec2` plugin:

- folds the tiny "Getting started with AWS" into the page on configuration
- spells out the name of each setting in full instead of noting the
  `discovery.ec2` prefix at the top of the page.
- replaces each `(Secure)` marker with a sentence describing what that means in
  situ
- notes some missing defaults
- clarifies the behaviour of `discovery.ec2.groups` (dependent on `.any_group`)
- clarifies what `discovery.ec2.host_type` is for
- adds `discovery.ec2.tag.TAGNAME` as a (meta-)setting rather than describing
  it in a separate section
- notes that the tags mentioned in `discovery.ec2.tag.TAGNAME` cannot contain
  colons (see #38406)
- clarifies the EC2-specific interface names and what they're for
- reorders and rewords the recommendations for storage
- expands on why you should not span a cluster across regions
- adds a suggestion on protecting instances against termination during scale-in
- reformat to 80 columns where possible

Fixes #38406
2019-05-22 09:26:41 +01:00
Daniel Schneiter 458d942203
Mentioned the name of the icu_analyzer 2019-05-09 15:06:10 +02:00
Alexander Reelsen 1038f23510
Update community client and integration docs (#41513)
Added integrations for a couple of frameworks.

Removed community clients where the last commit was more than three
years ago. Also added the official go client link and removed the
official groovy client, as it is outdated.
2019-04-26 08:56:34 +02:00
Alexander Reelsen 1681870027
Remove stale integrations in docs (#40764)
Removed all integrations in documentation, who have not seen a 
commit for more than three years when the website 
returned an  error.
2019-04-25 05:36:52 +02:00
Jason Tedor 2e7520246b
Fix reference to ignore_above from analyis-icu docs
This commit fixes a reference to the docs for ignore_above from the
analysis-icu plugin docs.
2019-04-19 17:23:15 -04:00
clement-tourriere 8fe7568f73 Add ignore_above in ICUCollationKeywordFieldMapper (#40414)
Add the possibility to use ignore_above parameter in ICUCollationKeywordFieldMapper.

Close #40413
2019-04-19 13:17:00 -07:00
Nik Everett 12d6274088 Docs: Fix deprecation warning in Asciidoctor
Fix a deprecation warning that wasn't rendering correctly in
asciidoctor. This one needed to be explicitly marked as an inline macro
because it is on its own line and it needed to have its text escaped
because it contained a `,`. It also was missing explanitory text for
what the setting was.
2019-04-18 09:22:55 -04:00
Bob Blank 8fb43ab994 Fixing missing link on session_token (#41314)
session_token was missing a "secure link"
2019-04-17 14:08:01 -07:00
James Rodewig a967dde340
[DOCS] Improve docs for 'elasticsearch-keystore add-file' command (#41084) 2019-04-11 08:48:42 -04:00
Ryan Ernst ba9ea6ac62
Improve GCS docs for using keystore (#40605)
This commit tweaks the wording on using the keystore to store GCS
credentials to note it requires a different key type/command.

closes #39993
2019-04-03 07:21:13 -07:00
Jason Tedor 56d9a74edc
Fix more broken links in plugins docs
The archive docs were moved around a bit, and this commit fixes another
broken link in the plugins docs.
2019-03-29 10:44:08 -04:00
Jason Tedor f8cbb74d5f
Fix archives links in plugins docs
This commit fixes some broken links to the archive layouts in the
plugins docs.
2019-03-29 10:18:59 -04:00
James Rodewig a58a829ede
[DOCS] Document common settings for snapshot repository plugins (#40475) 2019-03-28 14:39:34 -04:00
Yannick Welsch 6b03b131be
Remove note about Azure ARM plugin (#40219)
Relates to #22679
2019-03-20 16:31:03 +01:00
Henning Andersen 62bb853161
Blob Store compress default to true (#40033)
Changed default of compress setting from false to true for blob store
repositories. This aligns the code with existing documentation and also
seems like the better default.
2019-03-15 12:23:22 +01:00
Yannick Welsch 3b71a31557
Remove Zen1 (#39466)
Removes all traces of Zen1 from the code base. Some of these commits will also be backported to
7.0/7.x (#39470) as the cluster.coordination package was making use of some things in
discovery.zen and we want to keep 7.x as close as possible to master.
2019-03-04 15:51:12 +01:00
Pedro Silva 518f5ffd0b Add Support for S3 Intelligent Tiering (#39376)
* Add support for S3 intelligent tiering
* Closes #38836
2019-03-04 07:58:54 +01:00
James Baiera c253277c90
Fix the OS sensing code in ClusterFormationTasks (#38457)
This fixes a bug in the sensing of the current OS family in the test cluster
formation code. Previously all builds would assume every environment 
was windows and would jump to using the windows zip build. This fixes 
the OS sensing code as well as updates some tests to account for 
different build flavors.
2019-02-20 11:45:26 -05:00
David Turner 87bb5d0872
repository-s3 also works with S3-compatibles (#38524)
- Notes that you can adjust the `s3.client.*.endpoint` setting to point to a
  repository held on an S3-compatible service.
- Notes that the default is `s3.amazonaws.com` and not to auto-detect the
  endpoint.
- Reformats docs to width.

Closes #35925
2019-02-19 10:00:46 +00:00
David Turner 5a3c452480
Align docs etc with new discovery setting names (#38492)
In #38333 and #38350 we moved away from the `discovery.zen` settings namespace
since these settings have an effect even though Zen Discovery itself is being
phased out. This change aligns the documentation and the names of related
classes and methods with the newly-introduced naming conventions.
2019-02-06 11:34:38 +00:00
David Turner 2d114a02ff
Rename static Zen1 settings (#38333)
Renames the following settings to remove the mention of `zen` in their names:

- `discovery.zen.hosts_provider` -> `discovery.seed_providers`
- `discovery.zen.ping.unicast.concurrent_connects` -> `discovery.seed_resolver.max_concurrent_resolvers`
- `discovery.zen.ping.unicast.hosts.resolve_timeout` -> `discovery.seed_resolver.timeout`
- `discovery.zen.ping.unicast.hosts` -> `discovery.seed_addresses`
2019-02-05 08:46:52 +00:00
Armin Braun 57823c484f
Streamline S3 Repository- and Client-Settings (#37393)
* Make repository settings override static settings
* Cache clients according to settings
   * Introduce custom implementations for the AWS credentials here to be able to use them as part of a hash key
2019-01-30 06:22:31 +01:00
Christoph Büscher 3a96608b3f
Remove more include_type_name and types from docs (#37601) 2019-01-18 14:11:18 +01:00
Christoph Büscher 25aac4f77f
Remove `include_type_name` in asciidoc where possible (#37568)
The "include_type_name" parameter was temporarily introduced in #37285 to facilitate
moving the default parameter setting to "false" in many places in the documentation
code snippets. Most of the places can simply be reverted without causing errors.
In this change I looked for asciidoc files that contained the
"include_type_name=true" addition when creating new indices but didn't look
likey they made use of the "_doc" type for mappings. This is mostly the case
e.g. in the analysis docs where index creating often only contains settings. I
manually corrected the use of types in some places where the docs still used an
explicit type name and not the dummy "_doc" type.
2019-01-18 09:34:11 +01:00
Julie Tibshirani 36a3b84fc9
Update the default for include_type_name to false. (#37285)
* Default include_type_name to false for get and put mappings.

* Default include_type_name to false for get field mappings.

* Add a constant for the default include_type_name value.

* Default include_type_name to false for get and put index templates.

* Default include_type_name to false for create index.

* Update create index calls in REST documentation to use include_type_name=true.

* Some minor clean-ups around the get index API.

* In REST tests, use include_type_name=true by default for index creation.

* Make sure to use 'expression == false'.

* Clarify the different IndexTemplateMetaData toXContent methods.

* Fix FullClusterRestartIT#testSnapshotRestore.

* Fix the ml_anomalies_default_mappings test.

* Fix GetFieldMappingsResponseTests and GetIndexTemplateResponseTests.

We make sure to specify include_type_name=true during xContent parsing,
so we continue to test the legacy typed responses. XContent generation
for the typeless responses is currently only covered by REST tests,
but we will be adding unit test coverage for these as we implement
each typeless API in the Java HLRC.

This commit also refactors GetMappingsResponse to follow the same appraoch
as the other mappings-related responses, where we read include_type_name
out of the xContent params, instead of creating a second toXContent method.
This gives better consistency in the response parsing code.

* Fix more REST tests.

* Improve some wording in the create index documentation.

* Add a note about types removal in the create index docs.

* Fix SmokeTestMonitoringWithSecurityIT#testHTTPExporterWithSSL.

* Make sure to mention include_type_name in the REST docs for affected APIs.

* Make sure to use 'expression == false' in FullClusterRestartIT.

* Mention include_type_name in the REST templates docs.
2019-01-14 13:08:01 -08:00