David Padilla Elasticsearch 

@dabit 

Elasticsearch 

No content

SELECT * FROM properties; 

No content

SELECT * FROM properties WHERE bedrooms = 2; 

No content

SELECT * FROM properties WHERE bedrooms = 2 AND bathrooms = 2; 

No content

SELECT * FROM properties INNER JOIN tasks ON tasks.property_id = properties.id WHERE bedrooms = 2 AND bathrooms = 3 AND tasks.pending = true; 

No content

SELECT * FROM properties INNER JOIN tasks ON tasks.property_id = properties.id WHERE bedrooms = 2 AND bathrooms = 3 AND tasks.pending = true AND name LIKE ('%query%'); 

SELECT * FROM properties INNER JOIN tasks ON tasks.property_id = properties.id LEFT JOIN addresses ON addresses.id = property.id WHERE bedrooms = 2 AND bathrooms = 3 AND tasks.pending = true AND (name LIKE ('%query%') OR address.street LIKE('%query%') OR address.state LIKE ('%query%')); 

Elasticsearch 

No content

Java ew 

Shay Banon 

REST API Lucene 

REST API Lucene Cliente Cliente Cliente 

REST 

GET POST PUT DELETE 

Escalable 

REST API Lucene REST API Lucene REST API Lucene REST API Lucene 

No content

Alta disponibilidad 

No content

Índices Propiedades Documentos 

Analogía con SQL Índices Propiedades Documentos Tablas Columnas Filas Tipos Base de datos 

Schemaless 

Crear un índice POST localhost:9200/sistemix 

Crear un documento POST localhost:9200/sistemix/contacto { nombre: "Daniel Pliego", edad: 25, intereses: ["diseño"] } 

POST sistemix/contacto { nombre: "Omaro Cancellara", edad: 30, intereses: ["angular", "rails"] } POST sistemix/contacto { nombre: "Alvaro Pereyra", edad: 25, intereses: ["node", "rails"] } POST sistemix/contacto { nombre: "Gloria Palma", edad: 20, intereses: ["angular", "cloud"] } 

Búsquedas 

GET sistemix/contacto/_search { query: { match: { nombre: "omaro" } } } match 

{"hits": [{"_index":"sistemix","_type":"contacto","_id":"AUxX 2Y-xjmAhoUOInopz", “_score":0.8784157,"_source":{ nombre: "Omaro Cancellara", edad: 30, intereses: ["angular", "rails"] } }]}} 

GET sistemix/contacto/_search { query: { term: { edad: 25 } } } term 

hits: { { nombre: "Daniel Pliego", edad: 25, intereses: ["diseño"] } ,{ nombre: "Alvaro Pereyra", edad: 25, intereses: ["node", "rails"] } } 

GET sistemix/contacto/_search { query: { term: { intereses: "rails" } } } term sobre arrays 

hits: { { nombre: "Omaro Cancellara", edad: 30, intereses: ["angular", "rails"] }, { nombre: "Alvaro Pereyra", edad: 25, intereses: ["node", "rails"] } } 

SELECT * FROM contacts INNER JOIN interests ON contact.id = interest.id WHERE interest.name = "rails"; 

Índice Invertido 1 2 3 4 5 6 7 daniel x pliego x omaro x cancellara x gloria x palma x alvaro x pereyra x 

Tokenización Tokenize Char Filter Token Filter Limpiar caracteres no deseados Partir en tokens Limpiar tokens 

Char filter El hierro es el amigo más honesto que puedes tener El hierro es el amigo mas honesto que puedes tener 

Tokenize El hierro es el amigo mas honesto que puedes tener el hierro es el amigo mas honesto que puedes tener 

Token Filter El hierro es el amigo mas honesto que puedes tener hierro amigo honesto puedes tener 

Índice Invertido 1 2 hierro x honesto x amigo x puedes x tener x 

Búsquedas Parciales 

Poor man’s full text search WHERE nombre LIKE “oma*” WHERE nombre LIKE “dan*” WHERE nombre LIKE “*plie*” 

N-Gram Tokenizer 

Daniel dan dani daniel ani anie aniel nie niel 

GET sistemix/contacto/_search { query: { match: { nombre: "dan" } } } 

Índice Invertido 1 2 dan x dani x daniel x ani x anie x aniel x nie x niel x 

Aggregations 

No content

GET sistemix/contacto/_search { query: { term: { intereses: "rails" } } } aggregations 

aggregations GET sistemix/contacto/_search { query: { term: { intereses: "rails" } }, aggregations: { edades: { terms: { field: "edad" } } } } 

{ nombre: "Omaro Cancellara", edad: 30, intereses: ["angular", "rails"] } },{ nombre: "Alvaro Pereyra", edad: 25, intereses: ["node", "rails"] } } }]}, "aggregations":{ "edades":{ "_type":"terms","missing":0,"total":2,"other":0, "terms": [ {"term":25,"count":1}, {"term":30,"count":1} ] } } } 

aggregations GET sistemix/contacto/_search { query: { term: { intereses: "rails" } }, aggregations: { edades_promedio: { avg: { field: "edad" } } } } 

{ nombre: "Omaro Cancellara", edad: 30, intereses: ["angular", "rails"] } },{ nombre: "Alvaro Pereyra", edad: 25, intereses: ["node", "rails"] } } }]}, "aggregations":{ “edades_promedio”:{ { “value”: 27.5 } } } 

term average max min sum range date range 

Búsqueda Espacial 

{ "pin" : { "location" : { "lat" : 40.12, "lon" : -71.34 } } } 

geo distance { "filtered" : { "query" : { "match_all" : {} }, "filter" : { "geo_distance" : { "distance" : "200km", "pin.location" : { "lat" : 40, "lon" : -70 } } } } } 

200 km 

{ "filtered" : { "query" : { "match_all" : {} }, "filter" : { "geo_bounding_box" : { "pin.location" : { "top_left" : { "lat" : 40.73, "lon" : -74.1 }, "bottom_right" : { "lat" : 40.01, "lon" : -71.12 } } } } } } geo bounding box 

No content

geo polygon { "filtered" : { "query" : { "match_all" : {} }, "filter" : { "geo_polygon" : { "person.location" : { "points" : [ {"lat" : 40, "lon" : -70}, {"lat" : 30, "lon" : -80}, {"lat" : 20, "lon" : -90} ] } } } } } 

No content

Conclusión 

Fácil de usar 

No content

Fácil de configurar 

##################### Elasticsearch Configuration Example ##################### # This file contains an overview of various configuration settings, # targeted at operations staff. Application developers should # consult the guide at . # # The installation procedure is covered at # . # # Elasticsearch comes with reasonable defaults for most settings, # so you can try it out without bothering with configuration. # # Most of the time, these defaults are just fine for running a production # cluster. If you're fine-tuning your cluster, or wondering about the # effect of certain configuration option, please _do ask_ on the # mailing list or IRC channel [http://elasticsearch.org/community]. # Any element in the configuration can be replaced with environment variables # by placing them in ${...} notation. For example: # #node.rack: ${RACK_ENV_VAR} # For information on supported formats and syntax for the config file, see # ################################### Cluster ################################### # Cluster name identifies your cluster for auto-discovery. If you're running # multiple clusters on the same network, make sure you're using unique names. # cluster.name: julian #################################### Node ##################################### # Node names are generated dynamically on startup, so you're relieved # from configuring them manually. You can tie this node to a specific name: # node.name: "Luna" 

Moderno 

Fin Fin 

@dabit david @ easybroker.com 

Desarrollo, Pizza y Cerveza 3er Jueves de cada mes http://www.meetup.com/ chilango-rails 

No content