honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Changed 1.x version to 1.7

This commit is contained in:
Clinton Gormley 2015-07-17 17:36:57 +02:00
parent 07b475bb48
commit 7f1926dcbf
1 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
README.md
View File

@ -5,7 +5,7 @@ The mapper attachments plugin adds the `attachment` type to Elasticsearch using
The `attachment` type allows to index different "attachment" type field (encoded as `base64`), for example, The `attachment` type allows to index different "attachment" type field (encoded as `base64`), for example,
microsoft office formats, open document formats, ePub, HTML, and so on (full list can be found [here](http://tika.apache.org/1.8/formats.html)). microsoft office formats, open document formats, ePub, HTML, and so on (full list can be found [here](http://tika.apache.org/1.8/formats.html)).
In order to install the plugin, run: In order to install the plugin, run:
```sh ```sh
bin/plugin install elasticsearch/elasticsearch-mapper-attachments/2.7.0 bin/plugin install elasticsearch/elasticsearch-mapper-attachments/2.7.0
@ -16,7 +16,7 @@ You need to install a version matching your Elasticsearch version:
| Elasticsearch | Attachments Plugin| Docs | | Elasticsearch | Attachments Plugin| Docs |
|------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------| |------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------|
| master | Build from source | See below | | master | Build from source | See below |
| es-1.x | 2.7.0 | [2.7.0](https://github.com/elastic/elasticsearch-mapper-attachments/tree/v2.7.0/#version-270-for-elasticsearch-17) | | es-1.7 | 2.7.0 | [2.7.0](https://github.com/elastic/elasticsearch-mapper-attachments/tree/v2.7.0/#version-270-for-elasticsearch-17) |
| es-1.6 | 2.6.0 | [2.6.0](https://github.com/elastic/elasticsearch-mapper-attachments/tree/v2.6.0/#version-260-for-elasticsearch-16) | | es-1.6 | 2.6.0 | [2.6.0](https://github.com/elastic/elasticsearch-mapper-attachments/tree/v2.6.0/#version-260-for-elasticsearch-16) |
| es-1.5 | 2.5.0 | [2.5.0](https://github.com/elastic/elasticsearch-mapper-attachments/tree/v2.5.0/#version-250-for-elasticsearch-15) | | es-1.5 | 2.5.0 | [2.5.0](https://github.com/elastic/elasticsearch-mapper-attachments/tree/v2.5.0/#version-250-for-elasticsearch-15) |
| es-1.4 | 2.4.3 | [2.4.3](https://github.com/elasticsearch/elasticsearch-mapper-attachments/tree/v2.4.3/#version-243-for-elasticsearch-14) | | es-1.4 | 2.4.3 | [2.4.3](https://github.com/elasticsearch/elasticsearch-mapper-attachments/tree/v2.4.3/#version-243-for-elasticsearch-14) |
@ -30,7 +30,7 @@ To build a `SNAPSHOT` version, you need to build it with Maven:
```bash ```bash
mvn clean install mvn clean install
plugin --install mapper-attachments \ plugin --install mapper-attachments \
--url file:target/releases/elasticsearch-mapper-attachments-X.X.X-SNAPSHOT.zip --url file:target/releases/elasticsearch-mapper-attachments-X.X.X-SNAPSHOT.zip
``` ```
@ -73,7 +73,7 @@ PUT /test/person/1
} }
``` ```
The `attachment` type not only indexes the content of the doc, but also automatically adds meta data on the attachment The `attachment` type not only indexes the content of the doc, but also automatically adds meta data on the attachment
as well (when available). as well (when available).
The metadata supported are: The metadata supported are:
@ -89,7 +89,7 @@ The metadata supported are:
They can be queried using the "dot notation", for example: `my_attachment.author`. They can be queried using the "dot notation", for example: `my_attachment.author`.
Both the meta data and the actual content are simple core type mappers (string, date, ...), thus, they can be controlled Both the meta data and the actual content are simple core type mappers (string, date, ...), thus, they can be controlled
in the mappings. For example: in the mappings. For example:
```javascript ```javascript
@ -115,8 +115,8 @@ PUT /test/person/_mapping
} }
``` ```
In the above example, the actual content indexed is mapped under `fields` name `file`, and we decide not to index it, so In the above example, the actual content indexed is mapped under `fields` name `file`, and we decide not to index it, so
it will only be available in the `_all` field. The other fields map to their respective metadata names, but there is no it will only be available in the `_all` field. The other fields map to their respective metadata names, but there is no
need to specify the `type` (like `string` or `date`) since it is already known. need to specify the `type` (like `string` or `date`) since it is already known.
Copy To feature Copy To feature
@ -181,7 +181,7 @@ PUT /test/person/1?refresh=true
} }
GET /test/person/_search GET /test/person/_search
{ {
"fields": [ "file.content_type" ], "fields": [ "file.content_type" ],
"query": { "query": {
"match": { "match": {
"file.content_type": "text plain" "file.content_type": "text plain"
@ -224,9 +224,9 @@ Will give you:
Indexed Characters Indexed Characters
------------------ ------------------
By default, `100000` characters are extracted when indexing the content. This default value can be changed by setting By default, `100000` characters are extracted when indexing the content. This default value can be changed by setting
the `index.mapping.attachment.indexed_chars` setting. It can also be provided on a per document indexed using the the `index.mapping.attachment.indexed_chars` setting. It can also be provided on a per document indexed using the
`_indexed_chars` parameter. `-1` can be set to extract all text, but note that all the text needs to be allowed to be `_indexed_chars` parameter. `-1` can be set to extract all text, but note that all the text needs to be allowed to be
represented in memory: represented in memory:
``` ```
@ -298,7 +298,7 @@ PUT /test/person/1?refresh=true
} }
GET /test/person/_search GET /test/person/_search
{ {
"fields": [], "fields": [],
"query": { "query": {
"match": { "match": {
"file": "king queen" "file": "king queen"