ElasticSearch in a Docker / Mesosphere enviroment

[Petar Djekic]

Hi,

anybody using ElasticSearch in combination with Docker (and Mesosphere)? 
Curious about how other approach persisting data volumes and host resource 
allocation. 

Best,
Petar

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/7a45f690-eb5a-4c3c-b8f3-38996124279c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Understanding tokenization for auto-complete

[Petar Djekic]

I'm using ES's auto-completion and i'd like to understand how the prefix 
tokenization works. Example queries and results its returning currently:

1) 'blackb' -> 'Blackberry Q10 Red' 
--> Expected

2) 'q' -> 'Blackberry Q10 Red'
--> Expected

3) 'q10' -> No result, expected is 'Blackberry Q10 Red'
--> Why are results returned when typing in 'q' but not 'q10'?

4) 'blackberry q10' 
--> Expected

5) 'sam' -> 'Samsung Galaxy S5' 
--> Expected

6) 'galax' > -> 'Samsung Galaxy S5' 
--> Expected

7) 'S5' 
-> No result, expected is 'Samsung Galaxy S5' 

I'm indexing the document using input: ["blackberry, "Q10 Red"], input: 
["samsung", "galaxy s5"], please find the mapping / query below. I thought 
the standard tokenizer would also tokenize on whitespaces and hence give 
result for S5, also i don't understand why 'q' gives results but 'q10' 
doesn't. Can i use the prefix tokenizer for such a use case or would it 
need to switch to ngrams completely?

My mapping looks as follow:

 "mappings" : {

"suggestions" : {

 "_timestamp": {

   "enabled": true,

   "path" : "lastTimestamp"

  },

 "properties" : {

   "suggest" : { "type" : "completion",

"index_analyzer" : "standard",

"search_analyzer" : "simple",

"payloads" : true,

"context" : {

  "type" : {

"type" : "category",

"path" : "entity"

and query like this:

{

"suggestions" : {

"text" : "'",

"completion" : {

"size" : 5,

"field" : "suggest",

"fuzzy" : {

"fuzziness" : 1

},

"context" : {

"type" : "'"

}

}

}

 }





-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/4a917898-8525-4916-807e-cb72001b30c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: NewRelic and Elasticsearch

[Petar Djekic]

@Jeremy: I've placed the newrelic installer in /usr/share/elasticsearch and 
ran the installer but it would not work. How did you get it working?

On Friday, July 11, 2014 8:21:04 AM UTC+2, Jérémy Lecour wrote:
>
>
>
> Le jeudi 14 février 2013 01:59:13 UTC+1, Shairon Toledo a écrit :
>>
>> I did that, however the newrelic agent only works by default with servlet 
>> interface. Since elasticsearch uses netty it does not work automatically. 
>> You will need patch elasticsearch with newrelic annotation in some methods 
>> to get it working. The best option is http://sematext.com/spm/index.html 
>> or paramedic for on-the-fly monitoring.
>>
>
>  According to the documentation, NewRelic supports Netty : 
> https://docs.newrelic.com/docs/java/new-relic-for-java
>
> I've installed the latest agent and restarted Elasticsearch. I get a few 
> JVM metrics, but nothing aout response time, throughput, …
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/446ec455-746c-4233-b043-eb271e259c9c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] ElasticUI AngularJS Directives - Easily Build an Interface on top of Elasticsearch

[Petar Djekic]

wow, this is really cool!

On Wednesday, July 2, 2014 12:56:48 PM UTC+2, Yousef El-Dardiry wrote:
>
> Hi all,
>
> I just open sourced a set of AngularJS Directives for Elasticsearch. It 
> enables developers to rapidly build a frontend (e.g.: faceted search 
> engine) on top of Elasticsearch.
>
> http://www.elasticui.com (or github 
> )
>
> It makes creating an aggregation and listing the buckets as simple as:
>
> * eui-aggregation="ejs.TermsAggregation('text_agg').field('text').size(10)">*
> *{{bucket}}*
> **
>
> I think this was currently missing in the ecosystem, which is why I 
> decided to build and open source it. I'd love any kind of feedback.
>
> - Yousef
>
> *-*
> Another example; add a checkbox facet based on a field using one of the 
> built-in widgets 
> :
>
> **
>
> Resulting in
> [image: checklist screenshot]
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/d1f09022-81f3-4b45-bcfc-2991a6190a6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.