Re: Limit large number of threads

[Lukáš Vlček]

Hi,

please note that Bigdesk does not show all internal thread pools in ES now.

Regards,
Lukas

On Fri, Mar 20, 2015 at 10:56 AM, Abid Hussain 
wrote:

> Hi all,
>
> I know I'm not the first one wondering about the number of threads but I
> didn't find anything really appropriate to my question.
>
> We use ES with the default values for the thread pool sizes, that is
> actually (according to what bigdesk says):
> * Search 72
> * Index 24
> * Bulk 24
> * Refresh 10
>
> This values sum up to 130. But in total, nearly 400 threads have been
> created by ES which makes a difference of about 280.
>
> So I wonder which components are using the mentioned 280 threads?
>
> And, is there is recommended way to limit extensive thread creation safely
> (i.e. without compromising cluster functionality)?
>
> Regards,
>
> Abid
>
> --
> 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/cc37ef7c-0eac-4e1c-b084-dc1f26e8915d%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAO9cvUbbvJBv%3DVnE1cOTRuGQFBEBJ9rYBETwO99NzJn3kKN%2BmA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Operators NEARx, BEFOR, AFTER, FIRSTx, LASTx

[Lukáš Vlček]

Hi Petr,

let me try to address some of your questions:

ad 1) I am not sure I understand what you mean. If you want to use span
type of query then simply use it instead of query string query. Especially,
if you pass user input into the query then it is recommended NOT to use
query string query and you should consider using different query type (like
span query in your case).

ad 2) Not sure I fully understand but I can see match for some of those
requested features in span queries. Like "slop". I would recommend you to
read through chapters of "Proximity Matching" [1] to see how you can use
"slop".

ad 3) The input that goes into span queries can go through text analysis
process (as long as I am not mistaken). The fact that there are term
queries behind the scene does not mean you can not process your analysis
first.

May be if you can share some of your configs/documents/queries we can help
you more.

[1]
http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/proximity-matching.html

Regards,
Lukas

On Mon, Jan 19, 2015 at 10:02 AM, Petr Janský  wrote:

> Noone? :-(
>
> Petr
>
> Dne úterý 13. ledna 2015 15:37:18 UTC+1 Petr Janský napsal(a):
>>
>> Hi there,
>>
>> I'm looking for a way how to access span_near and span_first
>> functionality to users via search box in gui that uses query string query.
>>
>>1. Is there any easy way how to do it?
>>2. Will ElasticSeach folks implement operators like NEARx, BEFOR,
>>AFTER, FIRSTx, LASTx to be able search by (using query string):
>>   - specific max word distance between key words
>>   - order of key words
>>   - word position of key word in field from start and end of field
>>   text
>>3. Span queries enable to use only terms, is there a way how to use
>>words that will be analysed by lang. analyser - stemming etc.?
>>
>>
>> Thanks
>> Petr
>>
>  --
> 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/f90a0eba-1b61-4a23-a2af-ec6a0c5e461f%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAO9cvUbmQvoJDFQ2aqQdy2eFLOH4RJja4KR__hfyqanJfx2fmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Template Query vs. Search Template

[Lukáš Vlček]

Hi,

I am bit confused about what is the distinction between Template Query [1]
and Search Template [2]. To me there seem to be some overlap in searching
capabilities in both. Is the main difference that the template query is a
query type while the search template adds a new REST end point that can be
used for search template management? Is there any other difference?

Is Mustache templating functionality the same in both APIs? The [1] refers
to [2] saying "[search template] allows you to template an entire search
request" - is this something template query can not do?

[1]
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-template-query.html
[2]
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-template.html

Thanks,
Lukas

-- 
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/CAO9cvUYh62fLpJL3uLuYLaEGGiNX96o1UquGbBKGjETZT7_8vg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Search Templates - sections not working?

[Lukáš Vlček]

Hi,

I can not make Search Templates with Sections to work. Anybody has any idea
what I do wrong?

Let's first take a simple example that works (#1) and then I expand it a
bit (#2).

# Example 1 (works fine)

GET _search/template
{
  "template" : {
"size": "{{size}}",
"query": {
  "match_all": {}
}
  },
  "params": {
"size": 2
  }
}

# Example 2 (fails) - it is the same query as in #1 except it should make
the "size" optional depending on params input.

GET _search/template
{
  "template" : {
{{#apply_size}}
"size": "{{size}}",
{{/apply_size}}
"query": {
  "match_all": {}
}
  },
  "params": {
"size": 2,
"apply_size": false
  }
}

Yields:
ElasticsearchParseException[Failed to parse template]; nested:
JsonParseException[Unexpected character ('{' (code 123)): was expecting
either valid name character (for unquoted name) or double-quote (for
quoted) to start field name\n at [Source: [B@7384e1ef; line: 3, column:
6]]; }]","status":400

Tested with ES:

{"number" : "1.3.0", "build_hash" :
"1265b1454eee7725a6918f57415c480028700fb4", "build_timestamp" :
"2014-07-23T13:46:36Z", "build_snapshot" : false, "lucene_version" : "4.9"}

Regards,
Lukas

-- 
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/CAO9cvUYFzq-4HCy%3DUn%3DaY_jQ%2BMreQHA939jeX5ynKhehm1Kiqw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Difficulties in searching in strings where words are separated by dots, underscores and hyphens

[Lukáš Vlček]

Hi,

this sound like an issue with analyzer to me.
Can you share more info about analyzer configuration for your 'name' and
'description' fields?

Regards,
Lukas

On Tue, Oct 7, 2014 at 9:28 AM, Radim Bukovský 
wrote:

> Hi,
> we use ElasticSearch in our file-sharing website. Our aim is to deliver
> the best search results as we can. We have now implemented ElasticSearch -
> Fuzzy Like This Query. But I am not convinced that is the best way for us.
> We have one search field for users. Keywords are searched in names and
> descriptions of uploaded files. Using Fuzzy Like This Query give us great
> results when description or filename (example: keyword is "trance", it
> finds "trance 2014", "Best trance Ever" etc.).
> Difficulties are with filenames/descriptions where the keywords are
> separated by dots (.), underscores (_) or hyphen (-) (example: keyword is
> "trance", it does not find "Best.trance.Ever" or "Best-trance-Ever" or
> "Best_trance_Ever"). Do you have any advice for this?
> Is it possible to solve it within Fuzzy Like This Query?
>
> Thank you very much for your help.
>
> Best regards,
> Radim Bukovsky
>
> Settings (Fuzzy Like This Query):
> addFields(array('name', 'description'));
> setLikeText($file->name);
> setMaxQueryTerms(12);
> setMinSimilarity(1);
>
> --
> 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/9cdd5b1f-a728-44e5-9efb-c85251a00100%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAO9cvUbBiHQiHO7JEoPODOKVbaWo5M1MqMp95G8k%3DdubKyNnHA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Loading JSON-LD into ES

[Lukáš Vlček]

Jörg,

my concern is that RDF/XML allow to express one thing in several ways. For
example, if you take FOAF specification then there are several ways how you
can express that one Person knows other Person. One way it using reference
IDs other way it using nested Person inside other Person. See [1] for
examples. My understanding is that although both ways express exactly the
same information they lead to different XML representation and thus to
different JSON-LD. Not that you can push such data in ES but I wonder if
you can then have any consistent way of querying such data.

May be there is some way how you can preprocess XML document and convert
all nested Persons to references (would require arbitrary ID
construction?). Or something similar. Though I am not sure this would be
generally applicable approach to any RDF data.

[1] http://www.xml.com/pub/a/2004/02/04/foaf.html

Regards,
Lukas

On Fri, Sep 26, 2014 at 9:28 AM, joergpra...@gmail.com <
joergpra...@gmail.com> wrote:

> JSON-LD is perfect for ES indexing, as long as you use the "compact" form
> of representation.
>
> http://www.w3.org/TR/json-ld-api/#compaction-algorithms
>
> Example:
>
>
> https://github.com/lanthaler/JsonLD/blob/master/Test/Fixtures/sample-compacted.jsonld
>
> This means you should use short field names and shorten IRIs to a prefix
> form. This gives a convenient mapping to ES field names (e.g. "dc:title" or
> "dc:creator"). The '@' fields can also be indexed and they do not control
> anything special in ES (some @id may be mapped to ES _id but for nested
> structures this does not match)
>
> I use my own RDF API and transform RDF graphs (so not only JSON-LD but
> also other formats like N-Triples and RDF/XML) into XContent using this
> method:
>
>
> https://github.com/xbib/xbib/blob/master/content/src/main/java/org/xbib/rdf/content/DefaultResourceContentBuilder.java
>
> I plan to extend this content building by interpreting rdf:type and
> rdf:list etc. to generate correct ES JSON objects and arrays. There is also
> an amount of work left to do for the plethora of XSD types in RDF literals
> or for language tags.
>
> This will be subsumed into an RDF input/output plugin for an ES-based
> Linked Data Platform
>
> http://www.w3.org/TR/ldp/
>
> but there is no ETA yet.
>
> Jörg
>
>
> On Fri, Sep 26, 2014 at 5:08 AM, Lukáš Vlček 
> wrote:
>
>> Hi,
>>
>> I think you will have to preprocess documents on your side first and then
>> push into ES individually (you can push in batch).
>>
>> As a side note, I would say json-ld is quite low level serialization od
>> RDF data IMO not optimal for ES indexing. May be better would be to find
>> some RDF-OOM tool and have your RDF documents mapped to Java POJOs and
>> serialize POJOs into JSONs instead (you can use Jackson library for that
>> for example). This will give you better control over whole RDF -> JSON
>> conversion process.
>>
>> Regards,
>> Lukas
>>
>> On Thu, Sep 25, 2014 at 7:21 PM, abo  wrote:
>>
>>> Hello,
>>>
>>> I'm new to Elasticsearch, so forgive me if this is a basic question or
>>> if it's in some documentation that I haven't read...
>>>
>>> I am trying to load a json-ld file into ES. The json-ld file was
>>> generated from an RDF file, using Jena. The structure starts with:
>>>
>>> {
>>>   "@graph" :
>>>
>>> followed by the individual "documents", each with:
>>>
>>> {
>>> "@id" :
>>>
>>> and a variable number of parameters in each.
>>>
>>> My question is how do I load this into ES and ensure that documents are
>>> individually referenced (as opposed to the entire json-ld file)?
>>>
>>> Do I need to doctor this json-ld file further in order to load it?
>>>
>>> Thanks for your help.
>>>
>>> -- abo
>>>
>>> --
>>> 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/ec26bbe7-5bb1-4c50-96c4-8f586e1e0807%40googlegroups.com
>>> <https://groups.google.com/d/msgid/elasticsearch/ec26bbe7-5bb1-4c50-96c4-8f586e1e0807%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>

Re: Loading JSON-LD into ES

[Lukáš Vlček]

Hi,

I think you will have to preprocess documents on your side first and then
push into ES individually (you can push in batch).

As a side note, I would say json-ld is quite low level serialization od RDF
data IMO not optimal for ES indexing. May be better would be to find some
RDF-OOM tool and have your RDF documents mapped to Java POJOs and serialize
POJOs into JSONs instead (you can use Jackson library for that for
example). This will give you better control over whole RDF -> JSON
conversion process.

Regards,
Lukas

On Thu, Sep 25, 2014 at 7:21 PM, abo  wrote:

> Hello,
>
> I'm new to Elasticsearch, so forgive me if this is a basic question or if
> it's in some documentation that I haven't read...
>
> I am trying to load a json-ld file into ES. The json-ld file was generated
> from an RDF file, using Jena. The structure starts with:
>
> {
>   "@graph" :
>
> followed by the individual "documents", each with:
>
> {
> "@id" :
>
> and a variable number of parameters in each.
>
> My question is how do I load this into ES and ensure that documents are
> individually referenced (as opposed to the entire json-ld file)?
>
> Do I need to doctor this json-ld file further in order to load it?
>
> Thanks for your help.
>
> -- abo
>
> --
> 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/ec26bbe7-5bb1-4c50-96c4-8f586e1e0807%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAO9cvUYiqGoP5%3DpYkkhLzP17pLXAPN9sQVY9Oxn7AH4EY10xGA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multi Tenant DB and JDBC River

[Lukáš Vlček]

Nitin,

If I am not mistaken rivers in ES will be deprecated. So in any case river
is not a good way to go for design of future application. We are using
rivers quite a lot in our project and we will be moving the functionality
to middleware layer.

Regards,
Lukáš
Dne 31.8.2014 3:58 "Nitin Maheshwari"  napsal(a):

> Thanks for the reference, its helpful.
>
>
> On Thu, Aug 28, 2014 at 12:33 PM, joergpra...@gmail.com <
> joergpra...@gmail.com> wrote:
>
>> I work on such a component which can handle jobs and delegate them to
>> other nodes but no working implementation available yet.
>>
>> For a service component that is able to maintain state in the cluster
>> state, see RiverState class in JDBC plugin.
>>
>> Jörg
>>
>>
>> On Thu, Aug 28, 2014 at 8:08 AM, Nitin Maheshwari 
>> wrote:
>>
>>> Thanks Jörg for your quick and timely response.
>>>
>>> I am new to ES, can you point me to any reference implementation for the
>>> ES service component?
>>>
>>> Once again thanks for the help.
>>>
>>> Nitin
>>>
>>>
>>> On Tuesday, 26 August 2014 15:07:05 UTC+5:30, Jörg Prante wrote:
>>>
 For multi tenant, the river concept is awkward. River is a singleton
 and is bound to single user execution, and you are right, creating river
 instances per DB and per index does not scale.

 There are several options:

 - write a more sophisticated plugin which acts as a service and not as
 a singleton. The ES service component, which would maintain state in the
 cluster state, could accept job requests where each job request is
 equivalent to a JDBC pull. The job requests are delegated to a node which
 is not very busy with jobs (load balancing). The code of the JDBC river can
 be reused for that.

 - write a separate middleware for your tenants where they can have
 separate access to the DB and prepare ES JSON bulk files from (maybe be by
 REST API calls similar in style to ES). This would be a domain specific
 solution but offers most flexibility to the tenants, they are free to
 decide how and when to create and index the data from DB.

 Jörg




 On Tue, Aug 26, 2014 at 11:21 AM, Nitin Maheshwari 
 wrote:

> Hi Jörg,
>
> I am working on a multi tenant application where each tenant has its
> own database. I am planning to use ES for indexing the data, and JDBC 
> river
> for doing periodic bulk indexing. I do not want to create one river per DB
> per object type. This will lead to too many rivers.
>
> I wanted to modify the JDBC river so that I can give parent DB
> location, where all tenant db connection information is available. And 
> then
> inside the river, modify it such that a feader thread is created for each
> river.
>
> Do you see any issue with this or do you have any other recommendation?
>
> Thanks,
> Nitin
>
> --
> 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 elasticsearc...@googlegroups.com.
>
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/elasticsearch/771fc3a8-2203-4db8-a07b-067430e7a473%
> 40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

  --
>>> 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/76780b26-5dfa-4de4-9d14-5e1a9cacb2d3%40googlegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "elasticsearch" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/elasticsearch/w88yWcbx4lM/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> elasticsearch+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGTXjgHFeV9ip4n0vO_TJNthcvD1RK-pHWruwL0gx_Rew%40mail.gmail.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Nitin (Nits)
> http://nitin

Re: Dealing with spam in this forum

[Lukáš Vlček]

Ivan,

I would not care much if the frequency is low but I think Elasticsearch
Linkedin group (
https://www.linkedin.com/groups?home=&gid=3393294&trk=anet_ug_hm) could be
more logical target for job postings.

Lukas


On Fri, Aug 1, 2014 at 8:54 PM, Ivan Brusic  wrote:

> I just deleted a couple of non-related job postings and banned the poster.
>
> Going forward, is there a consensus among the community about whether or
> not job postings should be allowed? I do not mind postings that come
> directly from companies, especially those whose existing developers are
> already part of the community. Recruiters on the other hand perhaps should
> not allowed. Of course, the job postings must be Elasticsearch related, and
> not simply a buzzword in the overall tech stack.
>
> This mailing list has not seen any yet, but they will appear eventually.
>
> Thoughts?
>
> Ivan
>
>
>  On Thu, Jul 24, 2014 at 2:30 PM, Mark Walkom 
> wrote:
>
>> You're better off starting a new thread around this :)
>>
>> (But take a look here
>> http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup.html
>> )
>>
>> Regards,
>> Mark Walkom
>>
>> Infrastructure Engineer
>> Campaign Monitor
>> email: ma...@campaignmonitor.com
>> web: www.campaignmonitor.com
>>
>>
>> On 25 July 2014 04:01, Sudhakar Chokkalingam 
>> wrote:
>>
>>> One help, i am new user to elastic search ..like to know the recommended
>>> java version for the elastic search 1.1.0
>>>
>>> On Tuesday, July 1, 2014 1:36:44 PM UTC-5, Clinton Gormley wrote:

 Hi all

 Recently we've had a few spam emails that have made it through Google's
 filters, and there have been a calls for us to change to a
 moderate-first-post policy. I am reluctant to adopt this policy for the
 following reasons:

 We get about 30 new users every day from all over the world, many of
 whom are early in their learning phase and are quite stuck - they need help
 as soon as possible. Fortunately this list is very active and helpful. In
 contrast, we've only ever banned 34 users from the list for spamming.  So
 making new users wait for timezones to swing their way feels like a heavy
 handed solution to a small problem. Yes, spammers are annoying but they are
 a small minority on this list.

 Instead, we have asked 10 of our long standing members to help us with
 banning spammers.  This way we have Spam Guardians active around the globe,
 who only need to do something if a spammer raises their ugly head above the
 parapet. One or two spam emails may get through, but hopefully somebody
 will leap into action and stop their activity before it becomes too
 tiresome.

 This isn't an exclusive list. If you would like to be on it, feel free
 to email me.  Note: I expect you to be a long standing and currently active
 member of this list to be included.

 If this solution doesn't solve the problem, then we can reconsider
 moderate-first-post, but we've managed to go 5 years without requiring it,
 and I'd prefer to keep things as easy as possible for new users.

 Clint

>>>  --
>>> 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/f02c850f-1601-400c-be9d-fd6a5472885b%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> 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/CAEM624ZUDOpS-M%2Bi7Y-WZ_BCmgSGLq-Dgta-MP0NLeTNncDvGQ%40mail.gmail.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> 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/CALY%3DcQCjkdtho6jnfaUSvaymf63H-_2jpJZqePV7M8RunbM6Xw%40mail.gmail.com
> 
> .
>
>

Re: ES 1.3.0 and 1.2.3 released

[Lukáš Vlček]

Hi,

Bigdesk (2.x) uses JSONP. Elasticsearch is dropping JSONP support starting
with 1.3 release. Still you can enable it in Elasticsearch but I do not
recommend it if Bigdesk would be the only reason. From my point of view
JSONP is hack-ish anti pattern and should be avoided.

There is this ticket for Bigdesk
https://github.com/lukas-vlcek/bigdesk/issues/55
I am still stuck with older version of Elasticsearch which means I do not
feel the heat of dropped JSONP but feel free to jump to this ticket and
have your say in comment so that I can see how much urgent it is for you.

On a general note, I consider Bigdesk 2.x series more in maintenance mode,
something new (Bigdesk 3.x) should be out hopefully by the end of this
year. This means new release of Bigdesk 2.x will come out only if community
express need for it. :-)

Regards,
Lukas


On Thu, Jul 24, 2014 at 5:49 AM, vjbangis  wrote:

> is the bigdesk plugin still supported in the new release?
>
> --
> 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/e88b62d6-9ef5-4306-b880-b99182baa551%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAO9cvUb-Uf0d1MdvTbS727Z227Y-k%2BFDqXK-qq0NeM5YnFsh4g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: CLA sign required even for tiny typo fix?

[Lukáš Vlček]

Shay,

I think it is not fair to say that JBoss is trying to be the beacon here
(my formulation could make it sound like that in my initial post - sorry
about that), it is more about JBoss catching up with the rest of the
company (i.e. Red Hat). See the below link for more details:
https://www.openshift.com/blogs/keep-calm-and-merge-on-lowering-barriers-to-open-source-contributions-with-apache-v2

Regards,
Lukas


On Tue, Jul 8, 2014 at 8:51 PM, Shay Banon  wrote:

> We can’t start to differentiate between one contribution or the other,
> cause then we start a different discussion, to where does the line goes.
> Its simpler to have a consistent message.
>
> Btw, our CLA is explicitly very lightweight, and it aims at protecting the
> contributors as well. Its quite tricky legally, but this is the spirit (of
> the stricter) Apache CLA as well.
>
> I would personally not use either Joynet or JBoss as the beacon to follow
> on such issues. Obviously, if this spreads, then I will make sure we study
> the legal aspects of it, from both contributors *and users* perspective.
>
> On Jul 8, 2014, at 19:19, Lukáš Vlček  wrote:
>
> Ivan,
>
> I think it is mostly about lowering the barrier for contributors regarding
> small updates ("so you found a missing comma in guide example and you want
> to fix it") and saving resources on the company side with CLA maintenance.
> As a company you can always explicitly ask for CLA sign in individual
> cases. As a result you end up with more resources for the other things.
> Anyway, I just wanted to point this out for inspiration.
>
> Regards,
> Lukas
>
>
> On Tue, Jul 8, 2014 at 6:12 PM, Ivan Brusic  wrote:
>
>> Elasticsearch as a company is relatively new, so I hope it will adjust
>> its practices, not just the CLA, as time goes on. The codebase has been
>> evolving so rapidly, that I would assume they are working on the code and
>> the revenue stream and not its licensing model.
>>
>> --
>> Ivan
>>
>>
>> On Tue, Jul 8, 2014 at 4:33 AM, Mark Walkom 
>> wrote:
>>
>>> I'd support this for what it's worth :)
>>>
>>> Regards,
>>> Mark Walkom
>>>
>>> Infrastructure Engineer
>>> Campaign Monitor
>>> email: ma...@campaignmonitor.com
>>> web: www.campaignmonitor.com
>>>
>>>
>>> On 8 July 2014 21:27, Lukáš Vlček  wrote:
>>>
>>>> Hi,
>>>>
>>>>
>>>> http://www.infoworld.com/d/open-source-software/red-hat-joyent-and-others-break-down-licensing-barriers-244727
>>>>
>>>> May be some companies showing what the future trend will be? :-)
>>>>
>>>> (yes, I am biased, I work for one of the companies listed in the blog
>>>> post)
>>>>
>>>> Regards,
>>>> Lukas
>>>>
>>>> --
>>>> 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/CAO9cvUZf_5TAocgmMNLfyU%2BR_NnGEXjGtD%2BkiFUJzzFwtJG3Og%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/elasticsearch/CAO9cvUZf_5TAocgmMNLfyU%2BR_NnGEXjGtD%2BkiFUJzzFwtJG3Og%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>> --
>>> 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/CAEM624YGbGQu09UB1Nx9RO64tbGgd%2BsZNKnKTsNG%2BwEGecgfgw%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/elasticsearch/CAEM624YGbGQu09UB1Nx9RO64tbGgd%2BsZNKnKTsNG%2BwEGecgfgw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> 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

Re: CLA sign required even for tiny typo fix?

[Lukáš Vlček]

Ivan,

I think it is mostly about lowering the barrier for contributors regarding
small updates ("so you found a missing comma in guide example and you want
to fix it") and saving resources on the company side with CLA maintenance.
As a company you can always explicitly ask for CLA sign in individual
cases. As a result you end up with more resources for the other things.
Anyway, I just wanted to point this out for inspiration.

Regards,
Lukas


On Tue, Jul 8, 2014 at 6:12 PM, Ivan Brusic  wrote:

> Elasticsearch as a company is relatively new, so I hope it will adjust its
> practices, not just the CLA, as time goes on. The codebase has been
> evolving so rapidly, that I would assume they are working on the code and
> the revenue stream and not its licensing model.
>
> --
> Ivan
>
>
> On Tue, Jul 8, 2014 at 4:33 AM, Mark Walkom 
> wrote:
>
>> I'd support this for what it's worth :)
>>
>> Regards,
>> Mark Walkom
>>
>> Infrastructure Engineer
>> Campaign Monitor
>> email: ma...@campaignmonitor.com
>> web: www.campaignmonitor.com
>>
>>
>> On 8 July 2014 21:27, Lukáš Vlček  wrote:
>>
>>> Hi,
>>>
>>>
>>> http://www.infoworld.com/d/open-source-software/red-hat-joyent-and-others-break-down-licensing-barriers-244727
>>>
>>> May be some companies showing what the future trend will be? :-)
>>>
>>> (yes, I am biased, I work for one of the companies listed in the blog
>>> post)
>>>
>>> Regards,
>>> Lukas
>>>
>>> --
>>> 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/CAO9cvUZf_5TAocgmMNLfyU%2BR_NnGEXjGtD%2BkiFUJzzFwtJG3Og%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/elasticsearch/CAO9cvUZf_5TAocgmMNLfyU%2BR_NnGEXjGtD%2BkiFUJzzFwtJG3Og%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> 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/CAEM624YGbGQu09UB1Nx9RO64tbGgd%2BsZNKnKTsNG%2BwEGecgfgw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/elasticsearch/CAEM624YGbGQu09UB1Nx9RO64tbGgd%2BsZNKnKTsNG%2BwEGecgfgw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> 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/CALY%3DcQAZoMG_%3D5_H5OegF%3DwsxAc0q8ajK-VcJ_pOtEnqx1nGHA%40mail.gmail.com
> <https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQAZoMG_%3D5_H5OegF%3DwsxAc0q8ajK-VcJ_pOtEnqx1nGHA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAO9cvUYRJ31WMcVt%2BDfT9JqFxUwGZ9gf%2BGrmOkd6atf25CwTtA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

CLA sign required even for tiny typo fix?

[Lukáš Vlček]

Hi,

http://www.infoworld.com/d/open-source-software/red-hat-joyent-and-others-break-down-licensing-barriers-244727

May be some companies showing what the future trend will be? :-)

(yes, I am biased, I work for one of the companies listed in the blog post)

Regards,
Lukas

-- 
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/CAO9cvUZf_5TAocgmMNLfyU%2BR_NnGEXjGtD%2BkiFUJzzFwtJG3Og%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Formal Grammar of Query DSL?

[Lukáš Vlček]

Not direct match but very interesting indeed! :-)


On Tue, Apr 22, 2014 at 10:40 PM, Nick Tackes  wrote:

> Not a direct match,
> but i did locate this grammar to lucene.
>
>
> https://github.com/thoward/lucene-query-parser.js/blob/master/lucene-query.grammar
>
>
>
> On Tuesday, April 22, 2014 1:26:23 PM UTC-7, Lukáš Vlček wrote:
>>
>> Hi,
>>
>> is there available any formal grammar of Query DSL for Elasticsearch?
>> (may be a PEG one [1] could be a good fit?)
>>
>> Regards,
>> Lukas
>>
>> [1] http://en.wikipedia.org/wiki/Parsing_expression_grammar
>>
>  --
> 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/eae27cb6-5bc1-44cf-91a4-43e1edc4132c%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/eae27cb6-5bc1-44cf-91a4-43e1edc4132c%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAO9cvUZKODYkJ_-fUiJzEaWB4cDo_FH1ndCJf9Q7CvDiUiSyBQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Formal Grammar of Query DSL?

[Lukáš Vlček]

Hi,

is there available any formal grammar of Query DSL for Elasticsearch? (may
be a PEG one [1] could be a good fit?)

Regards,
Lukas

[1] http://en.wikipedia.org/wiki/Parsing_expression_grammar

-- 
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/CAO9cvUabCUw%3DkwQrKvVTS1cQ4aE0DTcqN2OuQomRJqNyrmtkvA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Elasticsearch on java7u55 ?

[Lukáš Vlček]

Excellent, thanks Michael.
Dne 18.4.2014 18:18 "Michael McCandless" 
napsal(a):

> 1.7u55 should be safe for ElasticSearch; we just put out a blog post about
> this:
>
>
> http://www.elasticsearch.org/blog/java-1-7u55-safe-use-elasticsearch-lucene/
>
> And I'll fix the nightly Lucene benchmarks to use u55 too!  I should NOT
> have been using u40: it's not safe.
>
> Mike
>
> http://blog.mikemccandless.com
>
>
> On Fri, Apr 18, 2014 at 9:52 AM, Jason Wee  wrote:
>
>> will these two links help?
>>
>> https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/SYSTEM_REQUIREMENTS.txt
>> http://people.apache.org/~mikemccand/lucenebench/indexing.html
>>
>> lucene performance test is using java 1.70 u40. that's the same version
>> i'm using for lucene 4.6.0.
>>
>> jason
>>
>>
>> On Fri, Apr 18, 2014 at 8:54 PM, Lukáš Vlček wrote:
>>
>>> Hi,
>>>
>>> is anybody using Oracle Java 1.7.0_55 with Elasticsearch (v0.90.5)? Is
>>> it safe and recommended?
>>>
>>> I found Robert and Uwe discussed this Java version here:
>>> http://lucene.472066.n3.nabble.com/Update-lucene-apache-org-java-recommendations-with-java7u55-td4131353.html
>>> I found couple of failed builds in
>>> http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/ after Apr 16
>>> that might be related to this version of Java but all seemed to be rather
>>> Solr related.
>>>
>>> Regards,
>>> Lukas
>>>
>>> --
>>> 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/CAO9cvUbM_HdMBeRKoqCEAZvixiLyF%3Dkh2T6WwEZEn4SRWXuc%3DA%40mail.gmail.com<https://groups.google.com/d/msgid/elasticsearch/CAO9cvUbM_HdMBeRKoqCEAZvixiLyF%3Dkh2T6WwEZEn4SRWXuc%3DA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> 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/CAHO4itwFJV3g%2BEG0pLG%3DYP4Jv0V-xyPTX2zhi1EsdvyVT0ZAVA%40mail.gmail.com<https://groups.google.com/d/msgid/elasticsearch/CAHO4itwFJV3g%2BEG0pLG%3DYP4Jv0V-xyPTX2zhi1EsdvyVT0ZAVA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> 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/CANPQZbw5KOvKO38pfT6y0azci9cUzYOR2%3DicJy4_RW6jry1Tcw%40mail.gmail.com<https://groups.google.com/d/msgid/elasticsearch/CANPQZbw5KOvKO38pfT6y0azci9cUzYOR2%3DicJy4_RW6jry1Tcw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAO9cvUYGjznSKZos%2Bb-Ar-s%2BAeSyJHWJqtY_4_ny1So4ka0iUw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Elasticsearch on java7u55 ?

[Lukáš Vlček]

Hi,

is anybody using Oracle Java 1.7.0_55 with Elasticsearch (v0.90.5)? Is it
safe and recommended?

I found Robert and Uwe discussed this Java version here:
http://lucene.472066.n3.nabble.com/Update-lucene-apache-org-java-recommendations-with-java7u55-td4131353.html
I found couple of failed builds in
http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/ after Apr 16 that
might be related to this version of Java but all seemed to be rather Solr
related.

Regards,
Lukas

-- 
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/CAO9cvUbM_HdMBeRKoqCEAZvixiLyF%3Dkh2T6WwEZEn4SRWXuc%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Guide Search UX] search suggestions enhancement

[Lukáš Vlček]

Thanks,
feel free to let me know if there is better place where to report these...
Lukas


On Wed, Apr 9, 2014 at 8:30 PM, Binh Ly  wrote:

> Lukas, thank you, I will pass along :)
>
> --
> 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/b320cbe6-ffd1-4989-a11d-e112e40a9a22%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAO9cvUbML1TJYEsGbSSCQqCx-f1gkeTADnkY9P-w6mxcyehhuw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Guide Search UX] search suggestions enhancement

[Lukáš Vlček]

Hi,

I would like to propose two enhancements to web UX related to search
suggestions in .org Guide.

1) Hide search suggestions upon click event
In particular this can lead to strange situation like the following one:
- User is here
http://www.elasticsearch.org/guide/en/elasticsearch/rivers/current/index.html
- User types "river" into search field
- User clicks "rivers > rivers" item (currently ~ 6th from the top).
The problem is that this suggestion leads to the same page, it only jumps a
little bit down to #id-1 anchor. (
http://www.elasticsearch.org/guide/en/elasticsearch/rivers/current/index.html#id-1
)
As a result the page is still covered by search suggestions and actual text
on the page is not visible.
It might be actually useful to catch click event at the document level
meaning any click outside search suggestions will hide them.

2) Hide suggestions and clear search field on ESC key event while focus is
in search field.
So far the only way how to hide search suggestions is manually delete the
text in search field. Also note that there seem to be a bug when
a) the text in search field is selected (for example cmd+A or
cmd+Shift+left-arrow)
b) delete key is hit
because if b) happens quickly after a) search suggestions (re-)appear again
despite the search filed is already empty.

Regards,
Lukas

-- 
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/CAO9cvUa3m3VLTRMu_FoZtvLkRfXfGotbrtKuB_mnECQnSNy5qw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: River documentation vanished?

[Lukáš Vlček]

Clinton,

has the search been fixed? I notice that if I am in 0.90 guide docs and do
search for "river" it does not provide suggestion for
http://www.elasticsearch.org/guide/en/elasticsearch/reference/0.90/index.htmlpage.
Only when I am at some different (probably top?) level I can get this
suggestions.

For example:
- when I am here
http://www.elasticsearch.org/guide/en/elasticsearch/reference/0.90/index.htmlthen
search for river yields only one suggestions (river plugins - that is
not what I was looking for)
- when I am here
http://www.elasticsearch.org/guide/en/elasticsearch/reference/index.htmlthen
search for river yields nothing
- when I am here http://www.elasticsearch.org/guide/ then search for river
gives me a lot more links including the one I am looking for (except it is
for "current" version, not 0.90 which I navigate to manually by changing
URL then).

Regards,
Lukas


On Wed, Mar 5, 2014 at 1:46 PM, Clinton Gormley wrote:

>
> On 4 March 2014 10:27, Lukáš Vlček  wrote:
>
>> we try to keep documentation for our rivers updated but I noticed that
>> the general river documentation page [1] is probably no longer available on
>> Elaticsearch.org site?
>> Is this intentional? I can see twitter river is still pointing to it as
>> well [2]
>>
>
> thanks for spotting. it was a bug in my indexing script, which i've now
> fixed.  Will take a little time until the index rebuilds though.
>
> clint
>
> --
> 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/CAPt3XKSFeYm%2BVNjx0T80Y4TFqBaZLMCKQUqsJ0koNKGw2640oA%40mail.gmail.com<https://groups.google.com/d/msgid/elasticsearch/CAPt3XKSFeYm%2BVNjx0T80Y4TFqBaZLMCKQUqsJ0koNKGw2640oA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/CAO9cvUa5cLSr5zOxQc82PjH0%2B4Dg5-7xFmAr1od-WeXSC10ZJg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: OpenSearch for elasticsearch.org docs?

[Lukáš Vlček]

Hi Clint,

hard to say, just to make sure we are on the same page here is how I did it
for search.jboss.org back some time. I think it is still quite up to date.
https://community.jboss.org/en/website/blog/2012/09/26/jboss-community-search-upgraded(see
the "Adding OpenSearch Support")
There is also video in the blog post showing this thing in action (please
do not laugh too hard at the narrator voice).

Although the OpenSearch "standard" is IMO a bit dated and not actively
maintained it brings fast and easy shortcuts to repetitive searching in the
site. I would welcome this on elasticsearch.org/guide (and you would still
get most of the metrics if you track any). In fact I think it can be quite
easy to add it there (you already have suggester and all that would be
needed is to add some xml file into web root and create a new output format
of the search suggester to match the opensearch format).

HTH,
Lukáš


On Wed, Mar 19, 2014 at 4:08 PM, Clinton Gormley wrote:

> Hmm I tried this on google.com and cnn.com on Chrome and Safari and
> didn't see what you describe at all. Tab just selected the first option
> from the list of suggestions under the URL field. What am I missing?
>
>
> On 18 March 2014 19:25, Ivan Brusic  wrote:
>
>> That is not how OpenSearch works. With OpenSearch, you don't need to type
>> ?s= As Lukas explained, if you visited the site before, you should be
>> presented with a search interface after pressing TAB after entered the
>> first few (unique) characters of a domain. Try it out with google.com or
>> cnn.com
>>
>> Great feature. I wish more sites supported it. My own company doesn't,
>> but that is because I have nothing to do with the front end! It would be
>> done immediately if I had access.
>>
>> --
>> Ivan
>>
>>
>> On Tue, Mar 18, 2014 at 10:52 AM, David Pilato  wrote:
>>
>>> Hi Lukas,
>>>
>>> Actually it's working as you described in google chrome. I don't know
>>> for other browsers.
>>> It redirects to http://www.elasticsearch.org/?s=bulk
>>>
>>> (I searched for "bulk" here)
>>>
>>>  --
>>> *David Pilato* | *Technical Advocate* | *Elasticsearch.com*
>>> @dadoonet <https://twitter.com/dadoonet> | 
>>> @elasticsearchfr<https://twitter.com/elasticsearchfr>
>>>
>>>
>>> Le 18 mars 2014 à 14:41:01, Lukáš Vlček (lukas.vl...@gmail.com) a écrit:
>>>
>>> Hi,
>>>
>>> is there any plan to provide OpenSearch API for Elasticsearch docs soon?
>>>
>>> It would be really nice if I could search the docs directly from browser
>>> URL. Many browsers support that and it is quite fast shortcut to docs: once
>>> you start typing into URL field "elast" -> it will give you a hint that you
>>> can hit TAB to search in elasticsearch.org -> if you hit the TAB it
>>> will allow you to directly input search term and send it into search API of
>>> docs, also search suggestions are fully supported in many browsers.
>>>
>>> Just wanted to ping the ML before opening ticket for this.
>>>
>>> Regards,
>>> Lukas
>>>  --
>>> 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/CAO9cvUYCZE4Rkyks6hpentrDZ1c7xyawFCTgZniN0hOOcKZPrA%40mail.gmail.com<https://groups.google.com/d/msgid/elasticsearch/CAO9cvUYCZE4Rkyks6hpentrDZ1c7xyawFCTgZniN0hOOcKZPrA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>  --
>>> 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/etPan.532887f0.7724c67e.97ca%40MacBook-Air-de-David.local<https://groups.google.com/d/msgid/elasticsearch/etPan.532887f0.7724c67e.97ca%40MacBook-Air-de-David.local?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> You received this message becau

OpenSearch for elasticsearch.org docs?

[Lukáš Vlček]

Hi,

is there any plan to provide OpenSearch API for Elasticsearch docs soon?

It would be really nice if I could search the docs directly from browser
URL. Many browsers support that and it is quite fast shortcut to docs: once
you start typing into URL field "elast" -> it will give you a hint that you
can hit TAB to search in elasticsearch.org -> if you hit the TAB it will
allow you to directly input search term and send it into search API of
docs, also search suggestions are fully supported in many browsers.

Just wanted to ping the ML before opening ticket for this.

Regards,
Lukas

-- 
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/CAO9cvUYCZE4Rkyks6hpentrDZ1c7xyawFCTgZniN0hOOcKZPrA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Deploy in Jboss

[Lukáš Vlček]

Craig,

if you want you can also check how we do it for EAP6,
https://github.com/searchisko/searchisko (we use CDI)
What we do is similar to what David already mentioned, we use embedded Node
for development (works also on OpenShift) and TransportClient for
production where Elasticsearch cluster can be scaled independently.

Regards,
Lukáš


On Tue, Mar 11, 2014 at 1:26 PM, Craig Graham wrote:

> Hi Jörg,
>
>>
>> Thanks for the suggestion. I don't think I will be able to speak at the
>> same level of understanding that you have in regards to this issue. Are you
>> suggesting using an approach such as
>> https://github.com/elasticsearch/elasticsearch-transport-wares to
>> include ES in the same .war file as my Java web application?
>
>
> Thanks!
>
>
> --
> 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/b6db63a3-1805-452a-89ae-16d682e38d05%40googlegroups.com
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAO9cvUazz_CXwgvt7L8ntY4%2BxxfVxpsZ63hRTw%3DAT3qV666qKg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Deploy in Jboss

[Lukáš Vlček]

Craig,

out of curiosity, what is the advantage of such deployment? Why you want to
run JBoss server (or EAP) for each Elasticsearch node?

Regards,
Lukáš


On Tue, Mar 11, 2014 at 1:01 PM, Craig Graham wrote:

> Hi David,
>
> Thanks for the quick response.  For the purposes of this POC we need to
> mock an environment where ElasticSearch is running similar to how it does
> "out of the box" in Jetty, except use JBoss instead.  We would like to have
> an instance of JBoss which we can deploy ElasticSearch to and interact with
> it using the Java API. I have been looking around for any information about
> the possibility of deploying ElasticSearch in JBoss and how to do so if it
> is possible, but so far I haven't found much.
>
> Thanks Again!
>
>
>
> --
> 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/ef0e74e3-7c17-461f-9772-83e3188e48b5%40googlegroups.com
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAO9cvUYRp2HUA3t%3DCghq%3DcwH9Pwr3V_ivZBnSbXCQo52mkJfvA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: ELK source tar balls

[Lukáš Vlček]

Jörg

IMO the best approach would be to do this in context on Fedora packaging,
this means opening a ticket in appropriate system, where Fedora packaging
issues are tracked and do the work in context of such ticket. This way it
could get attention from the people that have a lot of experience in this
domain. If you are fine with that I will try to find which forum is the
right one. WDYT?

Regards,
Lukáš


On Thu, Mar 6, 2014 at 11:58 AM, joergpra...@gmail.com <
joergpra...@gmail.com> wrote:

> Yes, I'm aware of building the dependencies SRPMs too, and I agree it is a
> lot of work.
>
> Examining the Solr SRPM at
> https://bugzilla.redhat.com/show_bug.cgi?id=1025904 a lot of work has
> been already done regarding dependencies, and that encourages me to add the
> missing ones for ES.
>
> I think it is worth a try now that ES 1.0 is out. I'm unsure about how far
> I can proceed and if I find time to provide SRPMs for all future ES
> patch/bugfix versions. Maybe others are also interested in package
> maintaining and jump in, I'd welcome this.
>
> Jörg
>
>
>
> On Thu, Mar 6, 2014 at 11:24 AM, Lukáš Vlček wrote:
>
>> Jörg
>>
>> my point about shaded deps is that if you want to deliver crystal clear
>> RPM from Fedora POW then you need to build source RPM first and then noarch
>> RPM. Which means that you would first need to have all the shaded deps as a
>> separate RPMs available in some RPM repo (and if they have transitive deps
>> then these need to be also build as a standalone RPMs as well ... etc). At
>> least that is how I understand this and it can be a lot of work if you want
>> to support it long term and according to all Linux packaging standards.
>>
>> Regards,
>> Lukáš
>>
>>
>>
>>  --
> 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/CAKdsXoH2eJZmPzDPrF%2B%2BVXJOx7dhHZ28%3DhvrUY%3DLyyKDCaFcRw%40mail.gmail.com<https://groups.google.com/d/msgid/elasticsearch/CAKdsXoH2eJZmPzDPrF%2B%2BVXJOx7dhHZ28%3DhvrUY%3DLyyKDCaFcRw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/CAO9cvUbmrUtDS%3D56rg7SA%3DD_K4PA7RrVrJQzYMip585e-0P-9g%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: ELK source tar balls

[Lukáš Vlček]

Jörg

my point about shaded deps is that if you want to deliver crystal clear RPM
from Fedora POW then you need to build source RPM first and then noarch
RPM. Which means that you would first need to have all the shaded deps as a
separate RPMs available in some RPM repo (and if they have transitive deps
then these need to be also build as a standalone RPMs as well ... etc). At
least that is how I understand this and it can be a lot of work if you want
to support it long term and according to all Linux packaging standards.

Regards,
Lukáš



On Thu, Mar 6, 2014 at 10:29 AM, joergpra...@gmail.com <
joergpra...@gmail.com> wrote:

> I hope the shaded deps will work just by using the maven shade plugin.
> AFAIK Maven itself uses shaded deps.
>
>
> http://ftp.redhat.com/redhat/rhel/beta/7/x86_64/os/Packages/maven-shade-plugin-2.0-5.el7.noarch.rpm
>
> It could be that traveling down the path with RHEL7 Beta will be dead
> ended, then I'd switch to Fedora 20 / Fedora Rawhide / Fedora EPEL 7 /
> whatever.
>
> Jörg
>
>
> On Wed, Mar 5, 2014 at 1:27 PM, Lukáš Vlček  wrote:
>
>> Jörg,
>>
>> how are you going to approach shaded deps?
>> Also, it might be interesting to you, RPM for Lucene 4.7 is available in
>> Fedora (Rawhide) now: https://apps.fedoraproject.org/packages/lucene/ so
>> you may not need to rebuild it.
>>
>>  --
> 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/CAKdsXoF5og0pim%2ByFFp%2BAmyavkCpj9gE860GMEHYPWnU4burrg%40mail.gmail.com<https://groups.google.com/d/msgid/elasticsearch/CAKdsXoF5og0pim%2ByFFp%2BAmyavkCpj9gE860GMEHYPWnU4burrg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/CAO9cvUbbymek%3DCTtoSqW4J45xpSc6NAWuVR%2BrpWNJrjNUyoC1g%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: ELK source tar balls

[Lukáš Vlček]

Jörg,

how are you going to approach shaded deps?
Also, it might be interesting to you, RPM for Lucene 4.7 is available in
Fedora (Rawhide) now: https://apps.fedoraproject.org/packages/lucene/ so
you may not need to rebuild it.

Lukas


On Wed, Mar 5, 2014 at 9:15 AM, joergpra...@gmail.com  wrote:

> Tomasz, Elasticsearch source tarballs are available at github
> https://github.com/elasticsearch/elasticsearch/releases and the RPM
> should be automatically built, just by issuing the command "mvn install".
>
> For the RPM, I agree with you. I'm also disappointed by the RPM package
> offer so far. It seems to me the ES team misunderstands RPM as a solely
> binary distribution format, and used a simplified Maven RPM plugin build in
> pom.xml.
>
> I have installed a RHEL7 Beta yesterday to start a rebuild of
> Elasticsearch with Maven according to Fedora rules
> http://fedoraproject.org/wiki/How_to_create_an_RPM_package
>
> This will include src.rpm, spec file, correct target architecture, and
> dependencies, like in the Solr RPM at
> https://bugzilla.redhat.com/show_bug.cgi?id=1025904
>
> I hope it will be useful.
>
> Jörg
>
>
>
> On Wed, Mar 5, 2014 at 5:42 AM, Tomasz Kloczko 
> wrote:
>
>> On Wednesday, 5 March 2014 03:58:41 UTC, Mark Walkom wrote:
>>>
>>> There are rpm/deb repos http://www.elasticsearch.org/blog/apt-
>>> and-yum-repositories/
>>> Otherwise you can find the sources on github
>>>
>>
>> rpm packages cannot be build from github repo so this is why I'm asking
>> where are source tar balls.
>> Someone created these tar balls before rpm packages have been created ..
>>
>> In above yum repo there is no any traces of source rpm packages.
>> In github repo there is no spec files which can be used on build rpm
>> packages.
>> (If in source tar ball is .spec file such tar ball can be used
>> to build rpm package by for example "rpmbuild -ta
>> -.tar.gz")
>>
>> Don't get me wrong but lack of officially released tar balls, files used
>> on build binary packages is some kind of contradiction to claim "this
>> project is open source" ;)
>> Someone build rpm packages available on download page. Question is only
>> who did this and why these source packages are not published on official
>> pages? :)
>>
>> I'm not paranoid but I don't see reasons why I should trust official rpm
>> packages specially when I see that official rpm packages are noarch and
>> some of these packages contains shared object files which never should be
>> packaged into noarch.rpm packages.
>>
>> Tomasz
>>
>> --
>> 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/df95d569-924b-433c-9295-fd4774bdf589%40googlegroups.com
>> .
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>  --
> 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/CAKdsXoF2sMOPLVfma%2B35x2ocR7eP%2BR5FGsWjB6nfFGEHfjM0qQ%40mail.gmail.com
> .
>
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/CAO9cvUZyaZt_fqE6P6tjkCjhEQ-OJL%3D-cY0qRaeWafj7z48hLA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: node not allowed to joined cluster?

[Lukáš Vlček]

Clint,
seems I misinterpreted
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html#unicasthosts
settings.
I am sorry about that.

Lukas



On Wed, Mar 5, 2014 at 12:51 PM, Clinton Gormley wrote:

>
> On 5 March 2014 08:30, Lukáš Vlček  wrote:
>
>> You can provide a list of nodes (IP addresses or DNS names) that are
>> allowed to join the cluster. Other nodes will not be allowed.
>
>
> Where? I'm not aware of this option?
>
> --
> 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/CAPt3XKSTzva93ONrBehDQjs1kvxOOEvuqF5yK_O5or12WOn2_Q%40mail.gmail.com<https://groups.google.com/d/msgid/elasticsearch/CAPt3XKSTzva93ONrBehDQjs1kvxOOEvuqF5yK_O5or12WOn2_Q%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/CAO9cvUZa5kpTxa5tLc6mUkVdBFniLM5FGRhTYbfEHkCKYVkkkw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: node not allowed to joined cluster?

[Lukáš Vlček]

You can provide a list of nodes (IP addresses or DNS names) that are
allowed to join the cluster. Other nodes will not be allowed.
Lukáš
Dne 5.3.2014 7:03 "rene z"  napsal(a):

> For security reasons, is it possible to prevent or not allowing a node to
> join a cluster?
> With the use of some key.
> Bye,
> René
>
>  --
> 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/47ebeb7b-4d47-4b26-b0c4-83fe95f14c55%40googlegroups.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/CAO9cvUbedWSTAsU4-3fjU_51pCSJR7qymLb8vg%3DCHa-mX6XLzg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: River documentation vanished?

[Lukáš Vlček]

OK, I can see the doc page is still in sources:
https://github.com/elasticsearch/elasticsearch/blob/master/docs/river/index.asciidoc
and available at
http://www.elasticsearch.org/guide/en/elasticsearch/rivers/current/index.html

But for some reason it is not reachable via guide search.


On Tue, Mar 4, 2014 at 10:27 AM, Lukáš Vlček  wrote:

> Hi,
>
> we try to keep documentation for our rivers updated but I noticed that the
> general river documentation page [1] is probably no longer available on
> Elaticsearch.org site?
> Is this intentional? I can see twitter river is still pointing to it as
> well [2]
>
> [1]
> http://web.archive.org/web/20130819045449/http://www.elasticsearch.org/guide/reference/river
> [2] https://github.com/elasticsearch/elasticsearch-river-twitter
>
> Regards,
> Lukas
>

-- 
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/CAO9cvUYqN-Vt5LojcV5TvQbpveM5nUrPj999%2B8aR89Qi7DRkSA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

River documentation vanished?

[Lukáš Vlček]

Hi,

we try to keep documentation for our rivers updated but I noticed that the
general river documentation page [1] is probably no longer available on
Elaticsearch.org site?
Is this intentional? I can see twitter river is still pointing to it as
well [2]

[1]
http://web.archive.org/web/20130819045449/http://www.elasticsearch.org/guide/reference/river
[2] https://github.com/elasticsearch/elasticsearch-river-twitter

Regards,
Lukas

-- 
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/CAO9cvUaaq04dfBxqd4JRNK-HmYk3y6e6yVHdh9OyjJVOK-SBNA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[ANN] Bigdesk 2.4.0 released - support for Elasticsearch 1.0.0 (including RC1 and RC2)

[Lukáš Vlček]

Hi,

I am happy to announce release of Bigdesk 2.4.0. It brings support for
Elasticsearch 1.0.0 (including RC1 and RC2).
Note there was also release 2.2.3 last week with improved support for
Elasticsearch 0.90.10 and above.

Make sure to check updated Elasticsearch support matrix [1] and Release
Notes [2].

[1] https://github.com/lukas-vlcek/bigdesk#support-matrix
[2] https://github.com/lukas-vlcek/bigdesk#release-notes

Last but not least I would like to thank everyone who was pushing either me
or PRs towards this release.

http://bigdesk.org/

Regards,
Lukas

-- 
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/CAO9cvUYBQ_eUsKvZ43LqR-G0xdPVwwfH3Ufe3aLwE3YwTrLNUQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Marvel architecture question

[Lukáš Vlček]

Ah, so the plugin needs to be installed on both clusters, I missed that
part. Thanks for clarification.

BTW, is it required to have the plugin on both sides because the plugin on
cluster B does more than just serving the web app in this case? Say, I want
to monitor cluster A and store data into cluster B - thus I install plugin
on cluster A and configure accordingly, but do not install the plugin on B,
instead I just keep copy of the web app locally in case I would want to
access the data in cluster B? Hope my question makes sense...

Regards,
Lukas


On Thu, Jan 30, 2014 at 11:32 AM, Boaz Leskes  wrote:

> Hi Lukas,
>
> Not sure I follow. The Marvel plugin has to be installed on all nodes in
> cluster A and on nodes in cluster B (with the agent disabled). To view the
> data you would open http://node_from_cluster_B:9200/_plugin/marvel  , so
> if something goes wrong with A, you still have access to the data.
>
> Makes sense?
>
> Cheers,
> Boaz
>
>
> On Thursday, January 30, 2014 8:27:32 AM UTC+1, Lukáš Vlček wrote:
>>
>> Hi,
>>
>> first of all, congrats for Marvel release. Step in the right direction.
>>
>> I have some questions: If I understand correctly, as of now Marvel has to
>> run in the cluster that it collects metrics from (as a plugin). Let's call
>> this cluster A. It is recommended for production env to have the Marvel
>> store the metrics to a different cluster. Let's call it B. Now, does it in
>> fact mean that in order to browse collected metrics (that are stored in B)
>> the client has to have an access to at least one node of A? (I assume this
>> is necessary to download the Kibana based web app?). Or let me put it this
>> way: in case of critical state of cluster A client has to know which nodes
>> of A are responsive and able to serve the web app prior to investigating
>> historical data stored in B? If yes, is there any plan to get just the web
>> app as a standalone package (like zip, war ...) so that client does not
>> have to rely on cluster A to serve it? Am I misunderstanding the concept?
>>
>> Regards,
>> Lukas
>>
>  --
> 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/fd46420c-2c72-43b7-9b95-0d8b7e81ed14%40googlegroups.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/CAO9cvUaKBMZo_zOEEczFqcHf7PndH%3DfOMOfbHM1_G5Aq347z_A%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Memory Usage

[Lukáš Vlček]

Just a note: Bigdesk does not show breakdown of GC between old and new
generation. So currently one needs to be careful when interpreting this
chart. Better chart is coming. There are other tools that will show you the
breakdown of GC (Sematext SPM, Marvel, HQ might as well, you can use
visualVM ...)

Lukáš


On Thu, Jan 30, 2014 at 10:14 AM, Mark Walkom wrote:

> Facets use a fair bit of memory and in general ES will cache a much as it
> can to speed up query times.
>
> Your graphs look pretty reasonable to me, lots of little GC's rather than
> big ones rarely is what you want.
> What are you expecting?
>
> Regards,
> Mark Walkom
>
> Infrastructure Engineer
> Campaign Monitor
> email: ma...@campaignmonitor.com
> web: www.campaignmonitor.com
>
>
> On 30 January 2014 18:43, Vaidik Kapoor  wrote:
>
>> Hi Guys,
>>
>> I have the following situation. I have 3 nodes cluster, each node has 32
>> GB DDR3 RAM and 2 Octocore Processors (16 cores), with HT. Allocated 50% of
>> the RAM to Elasticsearch. We have only 1 index with 32 shards and 1 replica
>> each, making it 64 shards in the cluster. We have a lot of mappings in the
>> index (more than 3000 ~ no. of users).
>>
>> We have a lot of updates queries. In fact, we have only update queries
>> with upserts. We are using routing to put similar data in the same shard.
>> We see the rate of update queries ranging between 20/sec to 60/sec. This is
>> going to increase to about 130-140/sec when we go live. Our queries are
>> mostly filtered queries with a lot of use of term faceting (now we are
>> using the Aggregations module).
>>
>> We are using doc_values as much as possible to reduce bringing of field
>> data in the field data cache.
>>
>> For the last 2 weeks, I have been noticing that the memory usage would
>> never drop. Every node in the cluster is using about 90% of the memory all
>> the time. This triggers the GC a lot (sometimes more than 5 times in a
>> minute). We are using G1GC instead of the default CMS.
>>
>> I then decided to stop querying and indexing both. The memory usage still
>> does not drop and there are still a lot of GCs in a given minute. The
>> effect of this is visible in the queue we are using to update documents. I
>> can clearly relate the spikes in the queue with the GC activity i.e.
>> whenever GC happens, indexing seems to become slow. This is sort of
>> worrying me.
>>
>> I am attaching screenshots of BigDesk of two of our nodes in the cluster
>> (1 master data node and 1 non-master data node).
>>
>> What could be the reason? How should I debug this issue? Will be happy to
>> share more details if needed.
>>
>> Vaidik Kapoor
>> vaidikkapoor.info
>>
>> --
>> 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/CACWtv5k%3Dy9%2BY93jFQUV%2Bp5TM9D-rS-2HF1cOqPPTEatFrwjMPQ%40mail.gmail.com
>> .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>  --
> 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/CAEM624aA5rbhjKhSWJEVyx-_Rn7BqM2%3D_vvbvrOoq%2B251%3D_A4A%40mail.gmail.com
> .
>
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/CAO9cvUZ8a4Zvz6MAqARGPj_AtUJ_4NabaPGKnae%3DL9bHoKPxZg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Marvel architecture question

[Lukáš Vlček]

Hi,

first of all, congrats for Marvel release. Step in the right direction.

I have some questions: If I understand correctly, as of now Marvel has to
run in the cluster that it collects metrics from (as a plugin). Let's call
this cluster A. It is recommended for production env to have the Marvel
store the metrics to a different cluster. Let's call it B. Now, does it in
fact mean that in order to browse collected metrics (that are stored in B)
the client has to have an access to at least one node of A? (I assume this
is necessary to download the Kibana based web app?). Or let me put it this
way: in case of critical state of cluster A client has to know which nodes
of A are responsive and able to serve the web app prior to investigating
historical data stored in B? If yes, is there any plan to get just the web
app as a standalone package (like zip, war ...) so that client does not
have to rely on cluster A to serve it? Am I misunderstanding the concept?

Regards,
Lukas

-- 
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/CAO9cvUaRZ2sO-tcFNGcikzDX4qKK4jBKeYiY5CVNUxGP4CAc3g%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: For those wanting to try Marvel

[Lukáš Vlček]

If my memory serves me well one of the issues with plugins is missing
classloading isolation. If you have two plugins installed on a single node
they can clash (we have been hit by this with our own plugins and it took
us some time to figure it out because the symptom was not deterministic).
If Marvel contains Java code that is installed as a plugin it would be imo
useful if the code were a bit more transparent, especially for plugin
developers.

Regards,
Lukáš


On Wed, Jan 29, 2014 at 2:42 AM, Ivan Brusic  wrote:

> Marvel doesn't different much from elasticsearch plugins in that the code
> now runs in the same JVM instead of a separate process. The event data is
> pushed rather than pulled. It is great not having to re-invent the wheel,
> but having monitoring outside of elasticsearch is not an issue. Great
> observation about the tribe node BTW.
>
> Given that efficient JSON parsing libraries exist in most languages, I
> rather go that route over the cat API. Time to re-visit monitoring.
>
> Ivan
>
>
> On Tue, Jan 28, 2014 at 5:33 PM, Mark Walkom wrote:
>
>> Or perhaps something could come from the new cat API if they don't want
>> to go that route.
>>
>> Regards,
>> Mark Walkom
>>
>> Infrastructure Engineer
>> Campaign Monitor
>> email: ma...@campaignmonitor.com
>> web: www.campaignmonitor.com
>>
>>
>> On 29 January 2014 12:21, joergpra...@gmail.com wrote:
>>
>>> Marvel comes with hidden Java plugin code for an event pusher. Node
>>> events, route events, and shard events of ES can be indexed into ES. Very
>>> useful for historic analysis and post mortem views.
>>>
>>> It seems this was also a motivation for the tribe node mode: grow two
>>> separate clusters, one for the data, another one for the metrics.
>>>
>>> It would be nice if also the event pushing source code could be opened,
>>> so other monitoring tools are able to build on this facility too. Or at
>>> least documenting the event pushing API, for re-implementing it from
>>> scratch.
>>>
>>> Jörg
>>>
>>>  --
>>> 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/CAKdsXoG-JaWZU4qFQsUaM_UHCwkzMdYnLruUHNmcnkiZ-wX6jA%40mail.gmail.com
>>> .
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>  --
>> 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/CAEM624Yn5y1bxGYd%3DjeG%3DiUVzowhOsuzKi_8erKrPEmTNbxb%3DQ%40mail.gmail.com
>> .
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>  --
> 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/CALY%3DcQD%3Dh804DJBr2J8V3gDvkSK0ddXHvg0xDBf9XYzUza_n5w%40mail.gmail.com
> .
>
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/CAO9cvUbtaLcYfteU3CO8EWL4oP36OR86cE4Rj-JFEs3SLvjWGA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Native client or REST

[Lukáš Vlček]

>
> Question: If I index the files using native JAVA API, will I be able to
> perform queries/searches from the web application via http/REST API?
>

Yes.

-- 
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/CAO9cvUZKd-oWY%3DrZuhQgMeps85TL3qEfKvueFnH6mmDxHRi1nw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: A Question on Plugin redundancy

[Lukáš Vlček]

Roy,

Sounds a bit like similar approach to Sematext SPM to me (except they use
CollectD - which is based on RRD is I am not mistaken) - but that shouldn't
stop you.

As for RHQ it is upstream for JON (JBossON). See
http://planet.jboss.org/post/jboss_operations_network_jbosson_jon_rhq_whats_in_a_name
I think it might have been renamed (this happens in JBoss world :-)).

Regards,
Lukáš


On Wed, Jan 22, 2014 at 4:43 PM, Roy Russo  wrote:

> Hi Jorg,
>
> I think gatherer may be a little heavy for what I'm trying to achieve.
> What I'm working on can be compared to MMS:
> https://mms.mongodb.com/learn-more#monitoring
>
> Simple idea. No magic. I like to delude myself in to thinking its the next
> phase for ElasticHQ. ;-)
>
> Lukas has a point in that distribution as a plugin is not ideal, as a
> monitoring agent should not be affected by the system it is monitoring -
> not intimately tied.
>
> Lukas,
>
> Didn't know of RHQ. I was there for JBossON.
>
>
>
> On Tuesday, January 21, 2014 1:57:18 PM UTC-5, Roy Russo wrote:
>>
>> Hello all,
>>
>> Curious here on what is the recommended way of plugin deployment in a
>> cluster, for redundancy on that plugin. Say I have 10 nodes... I deploy a
>> plugin on Node1. Node1 dies. Now what? I may have a new master node, but my
>> plugin is gone.
>>
>> Is there an idea of deploying plugins on every node, and having only the
>> elected master be the "active" plugin?
>>
>> Excuse me if it's a dumb question. I can't seem to find the answer
>> anywhere.
>>
>> Regards,
>> Roy Russo
>> http://www.elastichq.org/
>>
>  --
> 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/f69b698e-47cd-48d6-b738-76f7a059a5e3%40googlegroups.com
> .
>
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/CAO9cvUZo2bV9xo7%3DvUmCWcm%2BpA7UNfqUo4-3nPnWf2pnZX7J2A%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: A Question on Plugin redundancy

[Lukáš Vlček]

Roy,

if you want to kick start some process like every 2 seconds and all it does
is fire couple of HTTP requests and store responses to local file then
using Java for this might have higher cost compared to existing
alternatives. That is all I meant by "heavy" java. If such job can finish
in terms of millis then you can not even fully benefit from JVM goodies.

If, however, you mean long running agent then Java is valid option. JBoss
RHQ is a good example of monitoring implemented in Java (as you surely know
:-)).

Regards,
Lukáš
Dne 22.1.2014 6:41 "Roy Russo"  napsal(a):

> Hi Lukas,
>
> Somewhat... The idea is a monitoring 'service'. Hosted. Where its hosted
> is a separate conversation.
>
> I agree with most everything  you stated. Having a local agent running is
> the way to go. I'm avoiding remote polling and little to no advantage in
> distributing as a plugin. The one advantage is that it is very clean and
> simple to install, but such a tight dependency has its downsides, as you
> mentioned.
>
> I don't agree on not using java. Folks using elasticsearch already have a
> JVM installed obviously, so its an easy jar drop and run. I'm not sure why
> you would consider it a heavy process. Have you been looking at my old
> jboss code? ;-) rrd is lighter. No objection there. So is Perl.
>
> At first the data from elasticsearch is meant to be condensed and sent
> across the wire... Small payloads. At some point, I may move to storing the
> full blobs, but that can task a system and certainly add to hardware costs
> for retention. Across x,000 clusters, storing monitoring metrics form
> histograms and analysis can get heavy.
>
>
>
> On Jan 21, 2014 11:24 PM, "Lukáš Vlček"  wrote:
>
>> Roy,
>>
>> if you are in fact talking about implementation of monitoring system for
>> ES then the following are my 2 cents:
>>
>> - regarding how to poll data from ES nodes, I would not implement it as a
>> "plugin" or anything similar that is dependent on ES platform itself. It
>> should be an external process and possibly very light process (Java process
>> is not light). The impact on ES should be as minimal as possible and it
>> should not rely on plugin system of ES either. I would consider looking at
>> something like RRD tools (and extensions on top of it). Really lightweight
>> process that sits on each node, kicks once a while, grabs all metrics via
>> REST API and stores it into local storage. It should then try to send these
>> data into central store but it may not be always available thus storing it
>> locally is important in case the connection to central store is restored at
>> later time. The other argument why not to use plugin system of ES is that
>> you should be able to upgrade monitoring system independently on ES cluster
>> - you can not do this with ES plugins.
>>
>> - should it poll the same stats from every single node? I think it
>> should! If ES cluster gets into trouble is can be because not every part of
>> the cluster sees "the same picture". IMO the only way how to learn about
>> this is collecting individual "pictures from every node". It is also the
>> most simple way of doing it (and you should definitely aim for simplicity).
>> Solving duplicities on the central storage side later should be possible
>> but you might not even need to do it if the size of collected data is not a
>> problem for you. The part where you need to be very careful when polling
>> the same stats from each node is making sure this is not putting high load
>> on the ES cluster. If it is possible to poll from the local node only (like
>> using _local in URL) then opt for it. Though I am no sure if this option is
>> still available post 1.0.0.RC1 release.
>>
>> Regards,
>> Lukas
>>
>>
>> On Tue, Jan 21, 2014 at 10:09 PM, joergpra...@gmail.com <
>> joergpra...@gmail.com> wrote:
>>
>>> You must deploy plugins to all nodes, so you will still have the plugin
>>> available when nodes come and go. You could add an action so that you can
>>> turn on/off a plugin explicitly by remote command. Or you can define a
>>> condition so a plugin can decide when to run. For example if you want a
>>> singleton, you can check if you run on the master node, and execute only
>>> then.
>>>
>>> Jörg
>>>
>>>  --
>>> 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 ela

Re: A Question on Plugin redundancy

[Lukáš Vlček]

Roy,

if you are in fact talking about implementation of monitoring system for ES
then the following are my 2 cents:

- regarding how to poll data from ES nodes, I would not implement it as a
"plugin" or anything similar that is dependent on ES platform itself. It
should be an external process and possibly very light process (Java process
is not light). The impact on ES should be as minimal as possible and it
should not rely on plugin system of ES either. I would consider looking at
something like RRD tools (and extensions on top of it). Really lightweight
process that sits on each node, kicks once a while, grabs all metrics via
REST API and stores it into local storage. It should then try to send these
data into central store but it may not be always available thus storing it
locally is important in case the connection to central store is restored at
later time. The other argument why not to use plugin system of ES is that
you should be able to upgrade monitoring system independently on ES cluster
- you can not do this with ES plugins.

- should it poll the same stats from every single node? I think it should!
If ES cluster gets into trouble is can be because not every part of the
cluster sees "the same picture". IMO the only way how to learn about this
is collecting individual "pictures from every node". It is also the most
simple way of doing it (and you should definitely aim for simplicity).
Solving duplicities on the central storage side later should be possible
but you might not even need to do it if the size of collected data is not a
problem for you. The part where you need to be very careful when polling
the same stats from each node is making sure this is not putting high load
on the ES cluster. If it is possible to poll from the local node only (like
using _local in URL) then opt for it. Though I am no sure if this option is
still available post 1.0.0.RC1 release.

Regards,
Lukas


On Tue, Jan 21, 2014 at 10:09 PM, joergpra...@gmail.com <
joergpra...@gmail.com> wrote:

> You must deploy plugins to all nodes, so you will still have the plugin
> available when nodes come and go. You could add an action so that you can
> turn on/off a plugin explicitly by remote command. Or you can define a
> condition so a plugin can decide when to run. For example if you want a
> singleton, you can check if you run on the master node, and execute only
> then.
>
> Jörg
>
>  --
> 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/CAKdsXoFQUHak0-PQ%3DLW3C0_0GQy8EwJThOKC__RhGgzGJk4MvA%40mail.gmail.com
> .
>
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/CAO9cvUbcy%2B-F1EdrOAJE%2Bh8Ud8JcbnpWpAf78ijZ4yO0jn6RYA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: BigDesk: Persist the ES endpoint?

[Lukáš Vlček]

Hi,
In this case I usually instruct Bigdesk about node endpoint URL via
'endpoint' URL patameter. It is documented on web or github.

So you will end up using URL like the following example:

http://bigdesk.org/v/2.2.0/index.html?endpoint=http://complete_path_to_your_endpoint&connect=true

You can bookmark this URL and it will autoconnect the bigdesk plugin to
endpoint at specified location.

It is recommend to URL encode the endpoint parameter value.

HTH,
If you are missing features, feel free to open ticket (it is good time for
that right now).

Lukáš
Dne 14.1.2014 10:18 "Steinar Bang"  napsal(a):

> Is there a way to persist the ES endpoint of BigDesk?
>
> I'm using nginx to forward port 9000 to a sub-path,
> eg. http://ip-number/elasticsearch/ instead of http://ip-number:9200 and
> when I Disconnect and Connect after a node restart, what's in the ES
> endpoint textbox is http://ip-number (no port number).
>
> Thanks!
>
>
> - Steinar
>
> --
> 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/upzcppnuapky.fsf%40dod.no.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/CAO9cvUZRRM8gKz0HMboXycAzYQje%2BBCwTiwBfBhbLXZ2qTpWug%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Facets loading time

[Lukáš Vlček]

Hi,

did you try
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/_field_data_formats.html#_fielddata_loading
?

Regards,
Lukas


On Mon, Jan 13, 2014 at 9:46 AM, oreno  wrote:

> Hi,
> is there any way to improve facets loading time (into memory)?
> I'm using field facets on a single string field and It's kind of a problem
> that the first query after indexing period is taking a long time (many
> unique users).
>
> Has anyone ever faced this problem?
> is there anyway to set the fields to load to cache automatically while
> indexing or warming up the index?
>
> Thanks in advanced,
>
> Oren
>
>
>
> --
> View this message in context:
> http://elasticsearch-users.115913.n3.nabble.com/Facets-loading-time-tp4047460.html
> Sent from the ElasticSearch Users mailing list archive at Nabble.com.
>
> --
> 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/1389602799729-4047460.post%40n3.nabble.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/CAO9cvUZCf_QJ4k5tAM7d0z7-98s3cOhM8hNr8uQ8GR_R0dU3Ow%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Is there a help document about bigdesk plugin？

[Lukáš Vlček]

Hi,

explanation about how to use it can be found on github pages or
bigdesk.orgweb site. There is no single document explaining individual
charts, but we
can start creating one. Feel free to ask.

Regards,
Lukáš
Dne 10.1.2014 7:35 "Eric Lu"  napsal(a):

> Or some detail introduction about the various charts？
>
> --
> 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/b9a893a8-9c16-4d2d-9efe-7218a4895896%40googlegroups.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/CAO9cvUb0MjLCf9UFUoeRx6PLBPP9NK4OHafYyOVDfuJo%3DbUd1Q%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Did ES ever consider replacing current query DSL with an external DSL?

[Lukáš Vlček]

Jörg,
is opensearch active? The last time I checked it it seemed pretty much dead.
Lukáš
Dne 20.12.2013 13:32 "joergpra...@gmail.com" 
napsal(a):

> Just some food for thought:
>
> In the DSL you give, there are some subtle issues which makes it hard for
> implementing a parser and correct query execution.
>
> For example, the word "New feature": is it just a phrase, or is it two
> terms? Is a span query for the two terms also valid?
>
> Another issue is well-formed input data typing. Is "ES" in the query an
> input of type "string"? And is "3.1" is double value or also a string type?
> Can types always be inferenced? What about date parsing, will date types be
> assigned automatically? Maybe by looking up the ES mapping (well, ES
> parsers do that already) ? Or, how to decide if "true" is the string "true"
> or the boolean constant? ES catches this but I mean the general case of an
> external DSL is dealing with JSON data type flaws. You are forced to
> re-implement the ES parser for all these nasty pitfalls.
>
> How to declare facets and filters in an external DSL? Or multi phrase and
> multi wildcard searching? It's not straightforward if there is simply no
> context information how to execute such things. How do you parse and
> translate wildcards mixed/nested with phrases such as "scien* 'week*
> magazin*'"? I was surprised how many folks are trained to use wildcards
> excessively. It is only possible to replace such "bad queries" with
> heuristics that can be executed on ES with high performance, with ranked
> results etc.
>
> I have written a CQL parser
> http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/os/part5-cql/searchRetrieve-v1.0-os-part5-cql.pdfto
>  generate ES DSL, but for Java API only. If anyone is interested in
> adding a CQL parser as a REST action, I could offer it as a plugin. It is
> of course not perfect, I'm not very satisfied with the result.
>
> My experience so far is, at least for CQL, because it is a weak typed
> query language (it does not have a notion of input data types) , that
> external query languages must really be able to match the power of
> Lucene/ES features, or you get into trouble implementing simplifications,
> fallbacks, and shortcuts all the way.
>
> So my favorite is still ES DSL, and for establishing simple searches,
> there are special featured query types that are designed for simplified
> free form input. E.g. ES DSL query type "query_string" understands the
> Lucene syntax, or the "match" query, and now we also have the
> "simple_query" https://github.com/elasticsearch/elasticsearch/pull/4402
>
> I'm interested in OpenSearch for ES http://www.opensearch.org/ so if
> anyone is working on this, it would be nice to know.
>
> Jörg
>
>
> On Thu, Dec 19, 2013 at 8:05 PM, xin zhang  wrote:
>>
>>
>> project = ES AND issuetype = "New Feature" AND fixVersion = 3.1 ORDER BY
>> created DESC, cf[10514] DESC
>>
>>
>>  --
> 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/CAKdsXoGhkOE038spXw1Tmm0zLv%3DS%3D8YAztaMZEYK-hVNwhMB5Q%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/CAO9cvUbqrVMq%3DoM5MS%3DwW2tJqFxC8FwC-d7R9CG4Hm1ihjfgtQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.