search for all hip-hop cds
$ curl -XGET host:9200/amazon/cd/_search?q=tag:hip-hop‘
search across _type(s)
search across _type(s)
search on both `cd` and `book` using `name`
$ curl -XGET ‘host:9200/amazon/cd,book/_search?q=name:call’
search across _type(s)
search on both `cd` and `book` using `name`
$ curl -XGET ‘host:9200/amazon/cd,book/_search?q=name:call’
search on `_all` types using `name`
$ curl -XGET ‘host:9200/amazon/_search?q=name:call’
search across _type(s)
search on both `cd` and `book` using `name`
$ curl -XGET ‘host:9200/amazon/cd,book/_search?q=name:call’
search on `_all` types using `name`
$ curl -XGET ‘host:9200/amazon/_search?q=name:call’
search on specific fields types
$ curl -XGET ‘host:9200/amazon/_search?q=book.author.first_name:jack
OR cd.artist:jack‘
book and cd can be indices as well
$ curl -XPUT host:9200/book/info/0812504321 -d ‘
{
"isbn" : "0812504321",
"name" : "Call of the Wild",
"author" : {
"first_name" : "Jack",
"last_name" : "London"
},
"pages" : 128,
"tag" : ["fiction", "children"]
}
‘
... `book` is now the _index
$ curl -XPUT host:9200/book/info/0812504321 -d ‘
{
"isbn" : "0812504321",
"name" : "Call of the Wild",
"author" : {
"first_name" : "Jack",
"last_name" : "London"
},
"pages" : 128,
"tag" : ["fiction", "children"]
}
‘
... `info` is the _type
$ curl -XPUT host:9200/book/info/0812504321 -d ‘
{
"isbn" : "0812504321",
"name" : "Call of the Wild",
"author" : {
"first_name" : "Jack",
"last_name" : "London"
},
"pages" : 128,
"tag" : ["fiction", "children"]
}
‘
cd is an index as well
$ curl -XPUT host:9200/cd/info/B00192IV0O -d ‘
{
"asin" : "B00192IV0O",
"name" : "THE E.N.D. (Energy Never Dies)",
"artist" : "Black Eyed Peas",
"label" : "Interscope",
"release_date": "2009-06-09",
"tag" : ["hip-hop", "pop-rap"]
}
‘
search across _index(es)
search across _index(es)
search on both `cd` and `book` using `name`
$ curl -XGET ‘host:9200/cd,book/info/_search?q=name:call’
search across _index(es)
search on both `cd` and `book` using `name`
$ curl -XGET ‘host:9200/cd,book/info/_search?q=name:call’
search on `_all` indices using `name`
$ curl -XGET ‘host:9200/_search?q=name:call’
query_dsl
query_dsl
done with the your_data part
query_dsl
done with the your_data part
=> now to the your_search part
... term_query
{
“term” : {
“name” : “call”
}
}
... term_query, also with type
{
“term” : {
“name” : “call”
}
}
{
“term” : {
“book.name” : “call”
}
}
create another index
node 1 node 2 node 3 node 4
1 1
2 2
PUT /amazon2
{
“index.number_of_shards” : 1,
“index.number_of_replicas” : 1
}
create another index
node 1 node 2 node 3 node 4
1 1 1
1 2 2
PUT /amazon2
{
“index.number_of_shards” : 1,
“index.number_of_replicas” : 1
}
create another index
node 1 node 2 node 3 node 4
1 1 1
1 2 2
almost all settings are index based
per document consistency
per document consistency
- you index it, its there
per document consistency
- you index it, its there
- no need to commit / flush
per document consistency
- you index it, its there
- no need to commit / flush
- uses a transaction log
(near) real_time search
(near) real_time search
- automatic, 1 second refresh rate
(near) real_time search
- automatic, 1 second refresh rate
- there’s an api for that
(near) real_time search
- automatic, 1 second refresh rate
- there’s an api for that
- POST /_refresh
long_term persistency
long_term persistency
- similar to apple time_machine
long_term persistency
- similar to apple time_machine
- or data_grid write_behind
long_term persistency
- similar to apple time_machine
- or data_grid write_behind
- write changes to index / translog
long_term persistency
- similar to apple time_machine
- or data_grid write_behind
- write changes to index / translog
- to a shared persistent storage
long_term persistency
- similar to apple time_machine
- or data_grid write_behind
- write changes to index / translog
- to a shared persistent storage
- asynchronously (reliable)
long_term persistency
- similar to apple time_machine
- or data_grid write_behind
- write changes to index / translog
- to a shared persistent storage
- asynchronously (reliable)
- low requirements from storage
long_term persistency
- similar to apple time_machine
- or data_grid write_behind
- write changes to index / translog
- to a shared persistent storage
- asynchronously (reliable)
- low requirements from storage
- cluster meta_data persisted
long_term persistency ... storage options
long_term persistency ... storage options
- shared file system
long_term persistency ... storage options
- shared file system
- no need for locking, etc ...
long_term persistency ... storage options
- shared file system
- no need for locking, etc ...
- hadoop, using HDFS
long_term persistency ... storage options
- shared file system
- no need for locking, etc ...
- hadoop, using HDFS
- cloud (aws_s3, rackspace_cloud_files)
long_term persistency ... node storage
long_term persistency ... node storage
- considered transient
long_term persistency ... node storage
- considered transient
- can be recovered from gateway
long_term persistency ... node storage
- considered transient
- can be recovered from gateway
- can be stored on
long_term persistency ... node storage
- considered transient
- can be recovered from gateway
- can be stored on
- local file system
long_term persistency ... node storage
- considered transient
- can be recovered from gateway
- can be stored on
- local file system
- heap (jvm) memory
long_term persistency ... node storage
- considered transient
- can be recovered from gateway
- can be stored on
- local file system
- heap (jvm) memory
- native (os) memory
long_term persistency ... node storage
- considered transient
- can be recovered from gateway
- can be stored on
- local file system
- heap (jvm) memory
- native (os) memory
- fs & memory combination
native cloud support
native cloud support
in the cloud
native cloud support
in the cloud
machine removed / added more dynamically
native cloud support
in the cloud
machine removed / added more dynamically
machine fail more “dynamically”
native cloud support
in the cloud
machine removed / added more dynamically
machine fail more “dynamically”
local storage is wiped
native cloud support ... storage
native cloud support ... storage
- local storage is wiped
native cloud support ... storage
- local storage is wiped
- use external storage (aws ebs)
native cloud support ... storage
- local storage is wiped
- use external storage (aws ebs)
- needs to be per machine / shard
native cloud support ... storage
- local storage is wiped
- use external storage (aws ebs)
- needs to be per machine / shard
- can get wiped as well ...
native cloud support ... storage
- local storage is wiped
- use external storage (aws ebs)
- needs to be per machine / shard
- can get wiped as well ...
- mmm..., ok, snapshot to aws s3
native cloud support ... storage
- local storage is wiped
- use external storage (aws ebs)
- needs to be per machine / shard
- can get wiped as well ...
- mmm..., ok, snapshot to aws s3
- expensive => ebs & s3
native cloud support ... storage
- local storage is wiped
- use external storage (aws ebs)
- needs to be per machine / shard
- can get wiped as well ...
- mmm..., ok, snapshot to aws s3
- expensive => ebs & s3
- snapshot interval problematic
native cloud support ... storage
- local storage is wiped
- use external storage (aws ebs)
- needs to be per machine / shard
- can get wiped as well ...
- mmm..., ok, snapshot to aws s3
- expensive => ebs & s3
- snapshot interval problematic
native cloud support ... the elastic way
native cloud support ... the elastic way
- use long term persistency
native cloud support ... the elastic way
- use long term persistency
- directly into cloud blob storage
native cloud support ... the elastic way
- use long term persistency
- directly into cloud blob storage
- aws s3, rackspace cloud_files
native cloud support ... the elastic way
- use long term persistency
- directly into cloud blob storage
- aws s3, rackspace cloud_files
native cloud support ... the elastic way
- use long term persistency
- directly into cloud blob storage
- aws s3, rackspace cloud_files
- reliable & asynchronous
native cloud support ... discovery
native cloud support ... discovery
- no multicast
native cloud support ... discovery
- no multicast
- resort to unicast discovery
native cloud support ... discovery
- no multicast
- resort to unicast discovery
- who’s my special nodes ...
native cloud support ... discovery
- no multicast
- resort to unicast discovery
- who’s my special nodes ...
- require persistent ip’s
native cloud support ... discovery
- no multicast
- resort to unicast discovery
- who’s my special nodes ...
- require persistent ip’s
- complicate operations
native cloud support ... the elastic way
native cloud support ... the elastic way
- discovery support multicast & unicast
native cloud support ... the elastic way
- discovery support multicast & unicast
- but also support cloud discovery
native cloud support ... the elastic way
- discovery support multicast & unicast
- but also support cloud discovery
- use cloud_provider API
native cloud support ... the elastic way
- discovery support multicast & unicast
- but also support cloud discovery
- use cloud_provider API
- ... to get the current list of nodes
ping end_session
ping end_session
icmq_seq=0 desc=brief overview of elasticsearch
ping end_session
icmq_seq=0 desc=brief overview of elasticsearch
icmq_seq=1 version=current version is 0.8
ping end_session
icmq_seq=0 desc=brief overview of elasticsearch
icmq_seq=1 version=current version is 0.8
icmq_seq=2 notice=is beta
ping end_session
icmq_seq=0 desc=brief overview of elasticsearch
icmq_seq=1 version=current version is 0.8
icmq_seq=2 notice=is beta
so expect bugs ...
ping end_session
icmq_seq=0 desc=brief overview of elasticsearch
icmq_seq=1 version=current version is 0.8
icmq_seq=2 notice=is beta
so expect bugs ...
they are actively fixed
ping end_session
icmq_seq=0 desc=brief overview of elasticsearch
icmq_seq=1 version=current version is 0.8
icmq_seq=2 notice=is beta
so expect bugs ...
they are actively fixed
as new features are being added
ping end_session
icmq_seq=0 desc=brief overview of elasticsearch
icmq_seq=1 version=current version is 0.8
icmq_seq=2 notice=is beta
so expect bugs ...
they are actively fixed
as new features are being added
icmq_seq=3 join=mailing list, suggestions, code
ping end_session
icmq_seq=0 desc=brief overview of elasticsearch
icmq_seq=1 version=current version is 0.8
icmq_seq=2 notice=is beta
so expect bugs ...
they are actively fixed
as new features are being added
icmq_seq=3 join=mailing list, suggestions, code
icmq_seq=4 thanks!
1–3 of 3 previous next Post a comment