Re: MS Excel plugin for Elasticsearch

2014-04-20 Thread Ase J
Try this,

https://github.com/chetanganatra/Excel-2-Elasticsearch/blob/master/README.md

Regards
Asif J.

On Sunday, May 19, 2013 9:35:23 PM UTC+5:30, Vineeth Mohan wrote:
>
> Hi ,
>
> Is there any plugin point already worked on for MS Excel.
> I just wanted to run the query from MS Excel and fetch the results in MS 
> Excel.
> Is that possible using any current work ?
>
> Thanks
>Vineeth
>

-- 
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/451ce3a7-0f57-442a-9ad4-1ad8cc7a16d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Cache cleaner in hot threads

2014-04-20 Thread Gabriel Kastenbaum
I have the same issue. The configuration is :  Two nodes, we sent them some 
data (1m) and now they  are running at 200%/400% around 
  
org.elasticsearch.indices.cache.filter.IndicesFilterCache$ReaderCleaner$1.run(IndicesFilterCache.java:183)
 for hours. (ES version 1.0.1)


Le vendredi 18 avril 2014 20:26:09 UTC+2, Nikolas Everett a écrit :
>
> I'm still doing performance work and I keep seeing the CacheCleaner pop up 
> [1].  I don't know how much of an effect its actually having, but I imagine 
> its something.
>
> It looks like entries in the cache get queued for deletion both by cache 
> clear commands and by readers closing.  Would it make sense to forgo 
> removing entries when the readers close and let the LRU policy clean it up?
>
> Nik
>
> [1]:
>100.4% (502.1ms out of 500ms) cpu usage by thread 
> 'elasticsearch[elastic1001][generic][T#73]'
>  2/10 snapshots sharing following 5 elements
>
> org.elasticsearch.common.cache.LocalCache$HashIterator.remove(LocalCache.java:4353)
>
> org.elasticsearch.indices.cache.filter.IndicesFilterCache$ReaderCleaner$1.run(IndicesFilterCache.java:186)
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>java.lang.Thread.run(Thread.java:724)
>  4/10 snapshots sharing following 8 elements
>
> org.elasticsearch.common.cache.LocalCache$HashIterator.nextInTable(LocalCache.java:4306)
>
> org.elasticsearch.common.cache.LocalCache$HashIterator.advance(LocalCache.java:4271)
>
> org.elasticsearch.common.cache.LocalCache$HashIterator.nextEntry(LocalCache.java:4346)
>
> org.elasticsearch.common.cache.LocalCache$KeyIterator.next(LocalCache.java:4362)
>
> org.elasticsearch.indices.cache.filter.IndicesFilterCache$ReaderCleaner$1.run(IndicesFilterCache.java:183)
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>java.lang.Thread.run(Thread.java:724)
>  4/10 snapshots sharing following 7 elements
>
> org.elasticsearch.common.cache.LocalCache$HashIterator.advance(LocalCache.java:4271)
>
> org.elasticsearch.common.cache.LocalCache$HashIterator.nextEntry(LocalCache.java:4346)
>
> org.elasticsearch.common.cache.LocalCache$KeyIterator.next(LocalCache.java:4362)
>
> org.elasticsearch.indices.cache.filter.IndicesFilterCache$ReaderCleaner$1.run(IndicesFilterCache.java:183)
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>java.lang.Thread.run(Thread.java:724)   
>

-- 
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/76076d38-e928-4eae-aa04-aff92e5c8983%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Ann] Elasticsearch Image Plugin 1.2.0 released

2014-04-20 Thread V
Ok, so it wasn't actually that difficult to find out what was going on :)

https://github.com/kzwang/elasticsearch-image/blob/master/src/main/java/org/elasticsearch/index/query/image/AbstractImageScorer.java

I don't really understand the motivation for the following bit of code, is 
there something bad about returning the Lire score? Could you possibly 
explain please?

if (Float.compare(distance, 1.0f) <= 0) { // distance less than 1, consider 
as same image
  score = 2f - distance;
} else {
  score = 1 / distance;
}


Thank you,
V

-- 
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/dc239a01-7d7b-48e8-9fd5-caa6b829b11c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: TransportClient - Sniffing Issue

2014-04-20 Thread joergpra...@gmail.com
Which is the hostName/hostPort you connect to?

Jörg


On Sun, Apr 20, 2014 at 12:08 PM, Savva  wrote:

> Small typo in the configuration of the replica node.
> "node.master" is actually set to "false"
>
> --
> 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/911e4e2a-404d-4835-9426-96df65bf7756%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/CAKdsXoHaceQ3a_%2BQVKu4Uc3mBtRvzVneCoJd1428hSL4S6mtPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Ann] Elasticsearch Image Plugin 1.2.0 released

2014-04-20 Thread V
Hi Kevin,

I've been using Lire for a little while now and was happy to see a plugin 
for ES had been created. Great work. 

I have a question about the score in ES vs the score in Lire.

For the same dataset, indexed with the same features, and then searched 
with the same feature I get the same results however, there are different 
scores in the ES results from those in the Lire results, is this normal?

I'm asking because I have some historical stuff which has recorded the 
scores given by Lire, and the lower ES scores are going to make it 
problematic to use the plugin.

An example:

ES top 3 scores:
0.06624806
0.04820513
0.036607143

Lire Jar top 3 scores:
0.8094672560691833
0.7381518483161926
0.6551922559738159


I'm keen to use ES as it helps to solve some scaling problems. But I'm very 
new to ES so I'm not sure how to look in to the difference with the 
scoring, do you have any insight?

Many thanks,
V



On Thursday, March 20, 2014 10:41:20 AM UTC, Kevin Wang wrote:
>
> Hi All,
>
> I've released version 1.2.0 of Elasticsearch Image Plugin.
> The Image Plugin is an Content Based Image Retrieval Plugin for 
> Elasticsearch using LIRE (Lucene Image Retrieval). It allows users to index 
> images and search for similar images.
>
> Changes in 1.2.0:
>
>- Use multi-thread when multiple features are required to improve 
>index speed
>- Allow index metadata
>- Allow query by existing image in index
>
>
>
> https://github.com/kzwang/elasticsearch-image
>
> Also I've created a demo website for this plugin (
> http://demo.elasticsearch-image.com/), it has 1,000,000 images  from 
> MIRFLICKR-1M collection (http://press.liacs.nl/mirflickr)
>
>
> Thanks,
> Kevin
>
>

-- 
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/a387f60e-63f0-44d8-9960-6caa918c97ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Facetted Search Misbehaving

2014-04-20 Thread Nik Everett
Sorry, wasn't reading too closely. If the execution:and is taking sometimes 
then that sounds like a bug.  

Nik

Sent from my iPhone

> On Apr 20, 2014, at 3:49 PM, Igal  wrote:
> 
> hey Nik,
> 
> thanks for your reply.  
> 
> you are correct about the default operator being "or", but as I've posted in 
> the original post I explicitly set it to "and" via "execution": "and" and I 
> see the difference in the results between "or" and "and" so I know that it is 
> working.  for some reason the numbers still do not match some of the time 
> though.
> 
> 
> Igal
> 
>> On Sunday, April 20, 2014 12:32:31 PM UTC-7, Nikolas Everett wrote:
>> 
>> 
>> Sent from my iPhone 
>> 
>> > On Apr 20, 2014, at 3:06 PM, "Igal @ getRailo.org"  
>> > wrote: 
>> > 
>> > I have an index for a Store with a type for Items, i.e. /store/items.  
>> > among other properties, Items have a Title (analyzed text), a Description 
>> > (analyzed text), and Tags (not-analyzed text). 
>> > 
>> > I want to be able to show the facets over Tags with counts, so if a facet 
>> > of the Tag "Yellow" has a count of 12, for example, then when the user 
>> > adds that Tag to the filter she will see only 12 items. 
>> > 
>> > I am using a Filtered Query with Aggs, as shown below, on Elasticsearch 
>> > 1.1.0 on a single node: 
>> > 
>> > GET _search { 
>> >  "query": { 
>> >"filtered": { 
>> >   "query": { 
>> >"multi_match": { 
>> >   "query": "Large Widgets" 
>> >  ,"fields": [ "title^3", "description" ] 
>> >   }} 
>> >  ,"filter": { 
>> >"terms": { 
>> >   "tags": [ "Colorful" ] 
>> >  ,"execution": "and" 
>> >   
>> >  ,"aggs": {"available_tags": {"terms": {"field": "tags"}}, "size": 20} 
>> > } 
>> > 
>> > I have two problems: 
>> > 
>> > 1) no matter what value I pass for the aggs/size I get 10 aggregations.  I 
>> > want to get more than 10. 
>> > 
>> > 2) the hits count that comes back when adding the new tag to the filter 
>> > doesn't match the doc_count that came with the aggregations, for example, 
>> > the aggregations might show a doc_count of 12 for the tag "Yellow", but if 
>> > I add "Yellow" to the filter terms so that it reads "tags": [ "Colorful", 
>> > "Yellow" ]I get 17 hits instead of the expected 12. 
>> 
>> If I recall the terms filter is an or filter. So you are getting colorful or 
>> yellow. It might have an and option. Not sure, on my phone now. Otherwise 
>> use a bool filter with two must subfilters to do an and. 
>> 
>> Nik 
>> > 
>> > am I doing something wrong?  is there a bug somewhere? 
>> > 
>> > TIA, 
>> > 
>> > 
>> > Igal 
>> > 
>> > 
>> > 
>> > 
>> > -- 
>> > 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/53541AB6.4000403%40getrailo.org.
>> >  
>> > 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/f6ce5c0d-37ec-45b6-972b-03dbd426e7de%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/B4C0631C-7665-4380-BDD6-E6C84292CAEB%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Facetted Search Misbehaving

2014-04-20 Thread Igal
hey Nik,

thanks for your reply.  

you are correct about the default operator being "or", but as I've posted 
in the original post I explicitly set it to "and" via "execution": "and" 
and I see the difference in the results between "or" and "and" so I know 
that it is working.  for some reason the numbers still do not match some of 
the time though.


Igal

On Sunday, April 20, 2014 12:32:31 PM UTC-7, Nikolas Everett wrote:
>
>
>
> Sent from my iPhone 
>
> > On Apr 20, 2014, at 3:06 PM, "Igal @ getRailo.org" 
> > > 
> wrote: 
> > 
> > I have an index for a Store with a type for Items, i.e. /store/items. 
>  among other properties, Items have a Title (analyzed text), a Description 
> (analyzed text), and Tags (not-analyzed text). 
> > 
> > I want to be able to show the facets over Tags with counts, so if a 
> facet of the Tag "Yellow" has a count of 12, for example, then when the 
> user adds that Tag to the filter she will see only 12 items. 
> > 
> > I am using a Filtered Query with Aggs, as shown below, on Elasticsearch 
> 1.1.0 on a single node: 
> > 
> > GET _search { 
> >  "query": { 
> >"filtered": { 
> >   "query": { 
> >"multi_match": { 
> >   "query": "Large Widgets" 
> >  ,"fields": [ "title^3", "description" ] 
> >   }} 
> >  ,"filter": { 
> >"terms": { 
> >   "tags": [ "Colorful" ] 
> >  ,"execution": "and" 
> >   
> >  ,"aggs": {"available_tags": {"terms": {"field": "tags"}}, "size": 20} 
> > } 
> > 
> > I have two problems: 
> > 
> > 1) no matter what value I pass for the aggs/size I get 10 aggregations. 
>  I want to get more than 10. 
> > 
> > 2) the hits count that comes back when adding the new tag to the filter 
> doesn't match the doc_count that came with the aggregations, for example, 
> the aggregations might show a doc_count of 12 for the tag "Yellow", but if 
> I add "Yellow" to the filter terms so that it reads "tags": [ "Colorful", 
> "Yellow" ]I get 17 hits instead of the expected 12. 
>
> If I recall the terms filter is an or filter. So you are getting colorful 
> or yellow. It might have an and option. Not sure, on my phone now. 
> Otherwise use a bool filter with two must subfilters to do an and. 
>
> Nik 
> > 
> > am I doing something wrong?  is there a bug somewhere? 
> > 
> > TIA, 
> > 
> > 
> > Igal 
> > 
> > 
> > 
> > 
> > -- 
> > 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/53541AB6.4000403%40getrailo.org.
>  
>
> > 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/f6ce5c0d-37ec-45b6-972b-03dbd426e7de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Facetted Search Misbehaving

2014-04-20 Thread Nik Everett


Sent from my iPhone

> On Apr 20, 2014, at 3:06 PM, "Igal @ getRailo.org"  wrote:
> 
> I have an index for a Store with a type for Items, i.e. /store/items.  among 
> other properties, Items have a Title (analyzed text), a Description (analyzed 
> text), and Tags (not-analyzed text).
> 
> I want to be able to show the facets over Tags with counts, so if a facet of 
> the Tag "Yellow" has a count of 12, for example, then when the user adds that 
> Tag to the filter she will see only 12 items.
> 
> I am using a Filtered Query with Aggs, as shown below, on Elasticsearch 1.1.0 
> on a single node:
> 
> GET _search {
>  "query": {
>"filtered": {
>   "query": {
>"multi_match": {
>   "query": "Large Widgets"
>  ,"fields": [ "title^3", "description" ]
>   }}
>  ,"filter": {
>"terms": {
>   "tags": [ "Colorful" ]
>  ,"execution": "and"
>  
>  ,"aggs": {"available_tags": {"terms": {"field": "tags"}}, "size": 20}
> }
> 
> I have two problems:
> 
> 1) no matter what value I pass for the aggs/size I get 10 aggregations.  I 
> want to get more than 10.
> 
> 2) the hits count that comes back when adding the new tag to the filter 
> doesn't match the doc_count that came with the aggregations, for example, the 
> aggregations might show a doc_count of 12 for the tag "Yellow", but if I add 
> "Yellow" to the filter terms so that it reads "tags": [ "Colorful", "Yellow" 
> ]I get 17 hits instead of the expected 12.

If I recall the terms filter is an or filter. So you are getting colorful or 
yellow. It might have an and option. Not sure, on my phone now. Otherwise use a 
bool filter with two must subfilters to do an and. 

Nik 
> 
> am I doing something wrong?  is there a bug somewhere?
> 
> TIA,
> 
> 
> Igal
> 
> 
> 
> 
> -- 
> 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/53541AB6.4000403%40getrailo.org.
> 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/E9B277B9-31A2-4DC6-A4F9-A30E0C5265CF%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


Facetted Search Misbehaving

2014-04-20 Thread Igal @ getRailo.org
I have an index for a Store with a type for Items, i.e. /store/items.  
among other properties, Items have a Title (analyzed text), a 
Description (analyzed text), and Tags (not-analyzed text).


I want to be able to show the facets over Tags with counts, so if a 
facet of the Tag "Yellow" has a count of 12, for example, then when the 
user adds that Tag to the filter she will see only 12 items.


I am using a Filtered Query with Aggs, as shown below, on Elasticsearch 
1.1.0 on a single node:


GET _search {
  "query": {
"filtered": {
   "query": {
"multi_match": {
   "query": "Large Widgets"
  ,"fields": [ "title^3", "description" ]
   }}
  ,"filter": {
"terms": {
   "tags": [ "Colorful" ]
  ,"execution": "and"
  
  ,"aggs": {"available_tags": {"terms": {"field": "tags"}}, "size": 20}
}

I have two problems:

1) no matter what value I pass for the aggs/size I get 10 aggregations.  
I want to get more than 10.


2) the hits count that comes back when adding the new tag to the filter 
doesn't match the doc_count that came with the aggregations, for 
example, the aggregations might show a doc_count of 12 for the tag 
"Yellow", but if I add "Yellow" to the filter terms so that it reads 
"tags": [ "Colorful", "Yellow" ]I get 17 hits instead of the expected 12.


am I doing something wrong?  is there a bug somewhere?

TIA,


Igal




--
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/53541AB6.4000403%40getrailo.org.
For more options, visit https://groups.google.com/d/optout.


Elasticsearch with JSON-array, causing serialize -error

2014-04-20 Thread PyrK
 

I'm using elasticsearch with mongodb -collection using 
elmongo. 
I have a collection (elasticsearch index's point of view json-array), that 
contains for example field: 
"random_point": [  0.10007477086037397,  0 ]

That's most likely the reason I get this error, when trying to index my 
collection.
[2014-04-20 16:48:51,228][DEBUG][action.bulk  ] [Emma Frost] [
mediacontent-2014-04-20t16:48:44.116z][4] failed to execute bulk item (index
) index {[mediacontent-2014-04$

org.elasticsearch.index.mapper.MapperParsingException: object mapping [
random_point] trying to serialize a value with no field associated with 
it,current value 
[0.1000747708603739$

at org.elasticsearch.index.mapper.object.ObjectMapper.serializeValue
(ObjectMapper.java:595)

at org.elasticsearch.index.mapper.object.ObjectMapper.parse(
ObjectMapper.java:467)

at org.elasticsearch.index.mapper.object.ObjectMapper.serializeValue
(ObjectMapper.java:599)

at org.elasticsearch.index.mapper.object.ObjectMapper.serializeArray
(ObjectMapper.java:587)

at org.elasticsearch.index.mapper.object.ObjectMapper.parse(
ObjectMapper.java:459)

at org.elasticsearch.index.mapper.DocumentMapper.parse(
DocumentMapper.java:506)

at org.elasticsearch.index.mapper.DocumentMapper.parse(
DocumentMapper.java:450)

at org.elasticsearch.index.shard.service.InternalIndexShard.
prepareIndex(InternalIndexShard.java:327)

at org.elasticsearch.action.bulk.TransportShardBulkAction.
shardIndexOperation(TransportShardBulkAction.java:381)

at org.elasticsearch.action.bulk.TransportShardBulkAction.
shardOperationOnPrimary(TransportShardBulkAction.java:155)

at org.elasticsearch.action.support.replication.
TransportShardReplicationOperationAction$AsyncShardOperationAction.
performOnPrimary(TransportShardReplicationOperationAction$

at org.elasticsearch.action.support.replication.
TransportShardReplicationOperationAction$AsyncShardOperationAction$1.run(
TransportShardReplicationOperationAction.java:430)

at java.util.concurrent.ThreadPoolExecutor.runWorker(
ThreadPoolExecutor.java:1146)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(
ThreadPoolExecutor.java:615)

at java.lang.Thread.run(Thread.java:701)

[2014-04-20 16:48:54,129][INFO ][cluster.metadata ] [Emma Frost] [
mediacontent-2014-04-20t16:39:09.348z] deleting index


Is there any ways to bypass this? That array is a needed value in my 
collection. Is there anyways to give some option in elasticsearch to not to 
index that JSON-field, tho it's not going to be searchable field at all?


Best regards,

PK

-- 
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/edc6d83b-6e88-4cbc-b5db-78bfd1de5a46%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


service wrapper vs /etc/init.d/elasticsearch

2014-04-20 Thread mikesam460
Which one should be use for production machines, service wrapper or 
/etc/init.d/elasticsearch? What are their ultimate difference?

-- 
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/add49793-84a0-489a-82d7-4693e24a3093%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: array of strings vs string

2014-04-20 Thread Clinton Gormley
Also have a read about position_offset_gap:
http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/_multi_value_fields_2.html


On 17 April 2014 14:42, Aleh Aleshka  wrote:

> Thanks!
>
>
> On Wednesday, April 16, 2014 6:39:00 PM UTC+3, vineeth mohan wrote:
>
>> Hello Aleh ,
>>
>> Both should be good for your purpose.
>>
>> But then if you want to match against "abc def" ( that is with the space)
>> tomorrow , the array type will alone help.
>> You can disable the analyzer for the field  and achieve the functionality
>> which you cant if its a normal string.
>>
>> Thanks
>> Vineeth
>>
>>
>> On Wed, Apr 16, 2014 at 6:23 PM, Aleh Aleshka  wrote:
>>
>>>  Hi
>>>
>>> i'd like to have a field in document to which i'm going to append
>>> strings and use span_near queries to search for a specific sequence of
>>> strings in it
>>> i wonder if that kind of usage makes sense, and if using array of
>>> strings instead of one long string would be better?
>>>
>>> i.e.
>>> which document is better for this kind of query
>>>
>>>  GET /my_index/_search
>>> {
>>>   "query": {
>>> "span_near": {
>>>   "clauses": [
>>> {
>>>   "span_term": {
>>> "seq" : "lolrof"
>>> }
>>>   }
>>>
>>> ,{
>>>   "span_multi": {
>>> "match": {
>>>   "regexp": {"seq" : "000200<0-20003>"}
>>> }
>>>   }
>>> }
>>>   ],
>>>   "slop": 100500,
>>>   "in_order": true
>>> }
>>>   }
>>> }
>>>
>>>
>>> and this kind of update:
>>>
>>>  POST /my_index/4aeN2WBSS8WIpUpplUryPg/_update
>>> {
>>>   "script" : "ctx._source.seq += ['tag']"
>>> }
>>>
>>>
>>> documents:
>>>
>>>  POST /my_index
>>> {
>>> "seq": ["lolrofl","000100010001","000200020002"]
>>> }
>>>
>>>
>>>  POST /my_index
>>> {
>>> "seq": "lolrofl 000100010001 000200020002"
>>> }
>>>
>>>
>>> Thanks, Aleh
>>>
>>> --
>>> 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/534E7D48.407%40gmail.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/1fcaee3c-aa5b-4e59-8189-82ff46eb770f%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/CAPt3XKSeQ3p%2B%2BQSpTDma4M1kzt2BGJEDUJq_3GZRR0_XEjmFYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: MVEL scripting to return 0 or 1 for a boolean

2014-04-20 Thread Clinton Gormley
On 19 April 2014 20:57, Shane Neeley  wrote:

> "script": "log(_score * (doc['field1'].value == doc['field2'].value)"


 "script": "log(_score * ((doc['field1'].value == doc['field2'].value) ? :
1 : 0)"

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


Re: TransportClient - Sniffing Issue

2014-04-20 Thread Savva
Small typo in the configuration of the replica node.
"node.master" is actually set to "false"

-- 
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/911e4e2a-404d-4835-9426-96df65bf7756%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


TransportClient - Sniffing Issue

2014-04-20 Thread savva . khalaman
Hello, 

I have an ES cluster that consists of two nodes. The first one is 
explicitly set to be a master and the second serves as a replica. The 
configuration of the nodes is following:

*Master Node:*
cluster.name: "test-es-cluster"
node.name: "primary1"
cluster.routing.allocation.awareness.force.group.values: primary, replica
cluster.routing.allocation.awareness.attributes: group
node.group: primary
node.master: true
node.data: true
bootstrap.mlockall: true
discovery.zen.minimum_master_nodes: 1

*Replica Node:*
cluster.name: "test-es-cluster"
node.name: "replica1"
cluster.routing.allocation.awareness.force.group.values: primary, replica
cluster.routing.allocation.awareness.attributes: group
node.group: replica
node.master: true
node.data: true
bootstrap.mlockall: true
discovery.zen.minimum_master_nodes: 1

Next step, I would like to explicitly connect to the replica node using a 
transport client. In order to do that, I add the client as follows:
Settings settings = ImmutableSettings.settingsBuilder()
.put("cluster.name", "test-es-cluster")
.put("client.transport.ping_timeout", "10s")
.put("client.transport.sniff", false)
.build(); 
Client client = new TransportClient(settings)
.addTransportAddress(new InetSocketTransportAddress(hostName, hostPort));

However, when I try to send any request to the node via the client, I catch 
the "No node available" exception:
org.elasticsearch.client.transport.NoNodeAvailableException: No node 
available
at 
org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:196)
at 
org.elasticsearch.client.transport.support.InternalTransportIndicesAdminClient.execute(InternalTransportIndicesAdminClient.java:73)
at 
org.elasticsearch.client.support.AbstractIndicesAdminClient.stats(AbstractIndicesAdminClient.java:425)

Interestingly, If "client.transport.sniff" is set to be true, then 
everything works perfectly. But this way the client sends (round-robin) 
requests to the primary node too, which I try to avoid. If someone faced 
similar problem and can help to solve it, I will appreciate very much.

P.s. I run ElasticSearch 1.0.0 with AWS plugin (2.0.0.RC1) over the ec2 
instances. 

-- 
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/aec61522-40ff-4a80-acb2-1c88435998f4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.