How to fetch the offset of the highlighted word in the Elastic search result

[Harish Alwala]

I have indexed a book contents to Elastic search. Now from the search 
results I need to navigate to the page of the book. I am looking to fetch 
the offset of the search word in the results and map to the offset in the 
book to get the page number.

I have seen similar question in this forum, but they have no solution in 
it. I know it is easy to get it in LUCENE. I tried with TermVector in 
mapping, but it does not give me the offset in the query result.

I have spend good time in elastic search documentation and other forums to 
get the offsets of the highlighted search results, but I didnot get the 
solution.

Any suggestions please.

-- 
Please update your bookmarks! We have moved to https://discuss.elastic.co/
--- 
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/cbfd8edd-03eb-43dd-94a5-2fbe28edc0fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Is it possible to change the score mode of SHOULD clause?

[Xudong You]

For example I have following 2 documents:

{"id":"1",  "title":"elasticsearch", " description":"elasticsearch" }

{"id":"1",  "title":"elasticsearch", " description":"bing" }

And following query:
{
"query" :  {
"bool": {
"should": [
{
  "match": {
"title": {
  "query": "elasticsearch"
}
  }
},
{
  "match": {
"description": {
  "query": "elasticsearch"
}
  }
  }]
}
  }
}

The result score of documetn "1" is just the *SUM* of the scores of 2 sub 
should clause, since both title and description contains "elasticsearch":

_explanation: 
{
value: 0.4339554
*description: "sum of:*"
details: [2]
0: 
{
value: 0.2169777
description: "weight(title:google in 0) [PerFieldSimilarity], result of:"
}
1: 
{
value: 0.2169777
description: "weight(description:google in 0) [PerFieldSimilarity], result 
of:"
}
}

The result score of document "2", however, is different:

explanation: 
{
value: 0.04500804
*description: "product of:"*
details: [2]
0: 
{
value: 0.09001608
}
1:  
{
value: 0.5
*description: "coord(1/2)"*
}

The final score if NOT "*SUM of"* but *"product of"*, I think it is because 
in document "2", the "description" field does not contains 
"elastticsearch", that is, half of all sub should clause match the query 
term, that is why *coord(1/2) *comes in explanation.

My question is, is it possible to change the score mode of SHOULD clause so 
that, the final score of SHOULD clause is always the *SUM *of sub clause, 
no matter whether the sub clause match the query term or not?

-- 
Please update your bookmarks! We have moved to https://discuss.elastic.co/
--- 
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/30417c8c-35a5-427c-989b-dff063d23eeb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Wild card query with case insensitive search

[David Pilato]

Don't use wildcard query unless you want it to be "slow".
Prefer using ngrams based analyzers (will cost you more disk space).

HTH

David

> Le 26 mai 2015 à 22:29, Sagar Shah  a écrit :
> 
> Hello everyone,
> We are trying to replace application log storage from postgres db with 
> elastic search.
> We had two features in postgres that should not get affected.
> 1. Perform case insensitive search
> 2. Perform wild card search
> 
> In elastic search, we are using lowercase filter with keyword anlayzer to 
> meet point# 1. 
> For performing wild card search, we are using wildQuery (ES Java API).
> 
> 
> Everything looks file as long as I am searching for single word like 'sagar', 
> but searches fail to return any results when I use multiple words in my 
> search criteria like 'sagar shah'. That's probably because of keyword 
> analyzer, which breaks it into multiple words.
> 
> Is there a way to perform search a wild card type search in case-insensitive 
> format.
> 
> Please advise.
> Appreciate your inputs.
> 
> 
> Regards,
> Sagar Shah
> -- 
> Please update your bookmarks! We have moved to https://discuss.elastic.co/
> --- 
> 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/48b9228e-9cd0-4dc8-b4f2-3e5a5d24ddf9%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
Please update your bookmarks! We have moved to https://discuss.elastic.co/
--- 
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/AFA7CBFD-AFF9-421F-88EB-A67C67A65AB7%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Re: Kibana 4 Process Crash

[Mark Walkom]

What do the logs show?


PS - We're moving to https://discuss.elastic.co/, please join us there for
any future discussions!

On 26 May 2015 at 18:03, VV  wrote:

> Hello everyone
> I have a problem with Kibana 4, every moorning I open my browser on kibana
> page and I received the message "Waiting for elasticsearch is loading
> messages", the page don't get results, If I refresh the page Kibana Process
> go down.
>
> I had the following configuration on 2 servers:
>
> - 1 with Logstash that send data to elasticsearch 1.5.0
> - 1 with Elasticsearch 1.5.0 and Kibana 4.0.2
>
> Running on RHEL 5.5 x64.
>
> Could anyone help me?
> Thanks in advance.
>
> VV
>
> --
> Please update your bookmarks! We have moved to https://discuss.elastic.co/
> ---
> 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/3efda0c2-dced-488f-a40f-e0c0785cfd04%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Please update your bookmarks! We have moved to https://discuss.elastic.co/
--- 
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/CAEYi1X-rWrz%3DwQKLPC4%2Bpe12bWJQMcDrw4tUGrTPra7ptPricA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problems with plugins (Kopf)

[Mark Walkom]

Try adding another / to the end - http://localhost:9200/_plugin/kopf/

On 26 May 2015 at 22:34, Invest Ict  wrote:

> I have some troubles with my indexes, so i wanted to install a plugin
> named Kopf. So i downloaded the zip file from GIT and placed it on the
> server. Next thing i do is:
>
> *[root@havok elasticsearch]# bin/plugin -install
> lmenezes/elasticsearch-kopf -u file:///root/elasticsearch-kopf-master.zip*
>
> *-> Installing lmenezes/elasticsearch-kopf...*
>
> *Trying file:/root/elasticsearch-kopf-master.zip...*
>
> *Downloading DONE*
>
> *Installed lmenezes/elasticsearch-kopf into
> /usr/share/elasticsearch/plugins/kopf*
>
> *Identified as a _site plugin, moving to _site structure ...*
>
> *[root@havok elasticsearch]#*
>
>
> It has installed it in /usr/share/elasticsearch/plugins/kopf and it has
> included a _site folder.
>
>
> But when i go to http://localhost:9200/_plugin/kopf really nothing is
> happening. Also replaced localhost with the IP of the server, but still
> nothing.
>
>
> Anyone an idea what i did wrong?
>
>
>  --
> Please update your bookmarks! We have moved to https://discuss.elastic.co/
> ---
> 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/2a89b5f7-68ac-497f-a65e-a85a32c04d20%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Please update your bookmarks! We have moved to https://discuss.elastic.co/
--- 
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/CAEYi1X_%2Bs4wcurkOSuseBMqoHaZiS5yQGqwQsOBQNe45hTvW0A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Curious observation on copying an index

[Jack Park]

Windoz 7: ES 1.3.2: added some 6 million documents distributed over two
index instances.

Decided to "bookmark" that collection by copying it to another directory in
case something crashed going forward.

Something crashed.

Copied the clone back to the index directory. On booting and looking at it
from the Elastic HQ viewer, I could see that it recorded the size of one of
the index, but showed 0 documents in it. The other (smaller) index still
showed all its documents and proper size.

What happened?

Thanks in advance for ideas.
Jack

-- 
Please update your bookmarks! We have moved to https://discuss.elastic.co/
--- 
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/CAH6s0fw55YV_BB8jo3FuPyRL-7G2B-R5YfyRN%3D0ZcggKKCixLA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Wild card query with case insensitive search

[Sagar Shah]

Hello everyone,
We are trying to replace application log storage from postgres db with 
elastic search.
We had two features in postgres that should not get affected.
1. Perform case insensitive search
2. Perform wild card search

In elastic search, we are using lowercase filter with keyword anlayzer to 
meet point# 1. 
For performing wild card search, we are using wildQuery (ES Java API).


Everything looks file as long as I am searching for single word like 
'sagar', but searches fail to return any results when I use multiple words 
in my search criteria like 'sagar shah'. That's probably because of keyword 
analyzer, which breaks it into multiple words.

Is there a way to perform search a wild card type search in 
case-insensitive format.

Please advise.
Appreciate your inputs.


Regards,
Sagar Shah

-- 
Please update your bookmarks! We have moved to https://discuss.elastic.co/
--- 
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/48b9228e-9cd0-4dc8-b4f2-3e5a5d24ddf9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Whats the best way to add mappings programmatically ?

[mooky]

I've been using elastic since about 2009 ... and I've always found myself 
embedding elastic into our app - and configuring it programmatically.
I've always found programmatically configuring the mapping for an index to 
be very clunky.

But perhaps I just havent paid close attention to the enhancements over the 
years and I am now Doing It Wrong.

So, what is the best/cleanest way to configure mappings programmatically?

-- 
Please update your bookmarks! We have moved to https://discuss.elastic.co/
--- 
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/b2536cd4-fa9b-4a94-8d24-09bbb0f648af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Problems with plugins (Kopf)

[Invest Ict]

I have some troubles with my indexes, so i wanted to install a plugin named 
Kopf. So i downloaded the zip file from GIT and placed it on the server. 
Next thing i do is:

*[root@havok elasticsearch]# bin/plugin -install 
lmenezes/elasticsearch-kopf -u file:///root/elasticsearch-kopf-master.zip*

*-> Installing lmenezes/elasticsearch-kopf...*

*Trying file:/root/elasticsearch-kopf-master.zip...*

*Downloading DONE*

*Installed lmenezes/elasticsearch-kopf into 
/usr/share/elasticsearch/plugins/kopf*

*Identified as a _site plugin, moving to _site structure ...*

*[root@havok elasticsearch]#*


It has installed it in /usr/share/elasticsearch/plugins/kopf and it has 
included a _site folder.


But when i go to http://localhost:9200/_plugin/kopf really nothing is 
happening. Also replaced localhost with the IP of the server, but still 
nothing.


Anyone an idea what i did wrong?


-- 
Please update your bookmarks! We have moved to https://discuss.elastic.co/
--- 
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/2a89b5f7-68ac-497f-a65e-a85a32c04d20%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Index creation on Plugin instantiation

[Thomas]

Hi,

I'm experimenting with elasticsearch plugins creation and I'm trying to 
create an index (if missing) on plugin startup.

I wanted to ask what is the best place to add the code snippet for code 
creation? I have added it at an injected binding  with Client as 
constructor parameter but i get the following error:

no known master node, scheduling a retry
> [2015-05-26 12:03:27,289][ERROR][bootstrap] {1.4.1}: 
> Initialization Failed ...
> 1) UncategorizedExecutionException[Failed execution]
> ExecutionException[java.lang.NullPointerException]
> NullPointerException
>

My guess is that Client is not ready yet to handle index creation requests, 
my code snippet is the following:

public class IndexCreator {
>
> private final String indexName;
> private final ESLogger LOG;
>
> @Inject
> public IndexCreator(Settings settings, Client client) {
> this.LOG = Loggers.getLogger(getClass(), settings);
> this.indexName = settings.get("metis.index.name", ".metis");
> 
>
   String indexName = ".metis-registry";
>
>IndicesExistsResponse resp = 
> client.admin().indices().prepareExists(indexName).get();
>
>if (!resp.isExists()) {
>client.admin().indices().prepareCreate(indexName).get();
>} 
>
}
> }
>

And I add this as binding to my module

public class MyModule extends AbstractModule {

private final Settings settings;

public MyModule(Settings settings) {
this.settings = Preconditions.checkNotNull(settings);
}

@Override
protected void configure() {
bind(IndexCreator.class).asEagerSingleton();
}
}


But it produces the overmentioned error, any ideas?

Thanks,

Thomas

-- 
Please update your bookmarks! We have moved to https://discuss.elastic.co/
--- 
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/e7616e28-b6aa-45b0-989f-5ee7d55c02ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ES Indexing from Hadoop Issues

[Allan Mitchell]

Your original error was around a yarn container being destroyed.  My guess
right now would be that this is due to memory pressure in Hadoop.
I would look to increase the heap size AND/OR number of reducers in Hadoop.

Mapreduce is not known for being the fastest thing on the planet to be
honest given there is a lot of overhead.  It works nicely in batch mode
over a large dataset where you want distributed compute but over a smallish
dataset it can be seen as laggy.

Allan

On 23 May 2015 at 20:28, Sudhir Rao  wrote:

> Here is what the indexing performance i see : it takes 10 mins 29 seconds
> to finish indexing 626K records using the mapreduce (pig).  Is this the
> expected performance for 4 node elasticsearch ?
>
> Output(s):
>
> Successfully stored 626283 records in: "index1/raw_data"
>
>
> Counters:
>
> Total records written : 626283
>
> Total bytes written : 0
>
> Spillable Memory Manager spill count : 0
>
> Total bags proactively spilled: 0
>
> Total records proactively spilled: 0
>
>
>
> On Saturday, May 23, 2015 at 12:24:50 PM UTC-7, Sudhir Rao wrote:
>>
>> I see the following in the elasticsearch logs
>>
>> >> stop throttling indexing: numMergesInFlight=4, maxNumMerges=5
>>
>> The indexing however happens for few million records before all the
>> mapper fail - please see the attached error screenshot
>>
>>
>>
>> On Thursday, May 21, 2015 at 12:46:29 AM UTC-7, Allan Mitchell wrote:
>>>
>>> Hi
>>>
>>> The error is a Grunt error which suggests Pig is throwing it not ES.
>>> What do the PIG logs say?  What makes you think ES is the issue?
>>>
>>> I know it works with smaller data but that also means Pig works with
>>> smaller data not just ES.
>>>
>>> Allan
>>>
>>> On 21 May 2015 at 01:34, Sudhir Rao  wrote:
>>>
 Hi all,

 I have 4 node ES running

 ElasticSearch : 1.5.2
 OS : RHEL 6.x
 Java : 1.7
 CPU : 16 cores
 2 machines : 60 GB RAM, 10 TB disk
 2 machines : 120 GB RAM, 5 TB disk


 I also have a 500 node hadoop cluster and am trying to index data from
 Hadoop which is in Avro Format

 Daily size : 1.2 TB
 Hourly size : 40-60 GB


 elasticsearch.yml config
 ==

 cluster.name: zebra
 index.mapping.ignore_malformed: true
 index.merge.scheduler.max_thread_count: 1
 index.store.throttle.type: none
 index.refresh_interval: -1
 index.translog.flush_threshold_size: 102400
 discovery.zen.ping.unicast.hosts: ["node1","node2","node3","node4"]
 path.data:
 /hadoop01/es,/hadoop02/es,/hadoop03/es,/hadoop04/es,/hadoop05/es,/hadoop06/es,/hadoop07/es,/hadoop08/es,/hadoop09/es,/hadoop10/es,/hadoop11/es,/hadoop12/es
 bootstrap.mlockall: true
 indices.memory.index_buffer_size: 30%
 index.translog.flush_threshold_ops: 5
 index.store.type: mmapfs


 Cluster Settings
 

 $ curl -XGET 'http://localhost:9200/_cluster/health?pretty=true'
 {
 "cluster_name" : "zebra",
 "status" : "green",
 "timed_out" : false,
 "number_of_nodes" : 4,
 "number_of_data_nodes" : 4,
 "active_primary_shards" : 21,
 "active_shards" : 22,
 "relocating_shards" : 0,
 "initializing_shards" : 0,
 "unassigned_shards" : 0,
 "number_of_pending_tasks" : 0
 }


 Pig Script:
 

 avro_data = LOAD '$INPUT_PATH' USING AvroStorage ();

 temp_projection = FOREACH avro_data GENERATE
 our.own.udf.ToJsonString(headers,data) as data;

 STORE temp_projection INTO 'fpti/raw_data' USING
 org.elasticsearch.hadoop.pig.EsStorage ('es.resource =
 fpti/raw_data','es.input.json=true', 'node1,node2,node3,node4',
 'mapreduce.map.speculative=false','mapreduce.reduce.speculative=false','es.batch.size.bytes=512mb','es.batch.size.entries=1');
 When i run the above, there are around 300 mappers  none of them
 complete and every time the job fails with the below error. There is some
 documents that gets indexed though.

 *Error:*

 *2015-05-20 15:40:20,618 [main] ERROR
 org.apache.pig.tools.grunt.GruntParser - ERROR 2999: Unexpected internal
 error. Could not write all entries [1/8448] (maybe ES was overloaded?).
 Bailing out...*

 The job however finishes when the data size is few thousands


 Please let me know what else i can do to increase my indexing throughput


 regards

 #sudhir

 --
 Please update your bookmarks! We have moved to
 https://discuss.elastic.co/
 ---
 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/6312a8b6-bde7-40d6-bbf0-8b3fccf7cd12%40googlegroups.com
 

Re: How to response null value fields when query using "fields"

[Allan Mitchell]

Hi

Here is a quick example (pinched from the article I sent you and added to)

You can see that we get the values from two different places.  Whilst the
field exists at the _all level it does not exist in the inverted index.

POST /my_index/posts/_bulk
{ "index": { "_id": "1"  }}
{ "tags" : ["search"]}
{ "index": { "_id": "2"  }}
{ "tags" : ["search", "open_source"] }
{ "index": { "_id": "3"  }}
{ "other_field" : "some data"}
{ "index": { "_id": "4"  }}
{ "tags" : null  }
{ "index": { "_id": "5"  }}
{ "tags" : ["search", null]  }


GET /my_index/_search

GET /my_index/_search
{
"fields": [
   "tags"
],
"query": { "match_all": {}}

}

On 26 May 2015 at 09:33, Xudong You  wrote:

> Thanks your reply!
> But why if I remove "fields" from query DSL, then I can see those null
> value fields in ES response?
>
> On Tuesday, May 26, 2015 at 4:19:30 PM UTC+8, Allan Mitchell wrote:
>>
>> Hi
>>
>> If you have a field that has null as a value then as far as the inverted
>> index is concerned for that document it doesn''t exist
>>
>> Have a look at this
>>
>>
>> https://www.elastic.co/guide/en/elasticsearch/guide/current/_dealing_with_null_values.html
>>
>>
>> On 26 May 2015 at 08:11, Xudong You  wrote:
>>
>>> I used "fields" to limit only return selected fields:
>>> {
>>> "fields" : ["Title", "Price"],
>>> "query" :{
>>>  ...
>>> }
>>> }
>>>
>>> The Price fields might be null for some of the documents, I found that
>>> only when "Price" field value is NOT null, it is returned in ES response,
>>> otherwise, it is missing in response. But if I remove "fields" from the
>>> query, the null value field will appear in response.
>>>
>>> Is it by design of Elasticsearch? How to return the null value fields in
>>> response even using "fields" in query?
>>>
>>>  --
>>> Please update your bookmarks! We have moved to
>>> https://discuss.elastic.co/
>>> ---
>>> 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/3c91fd31-0e13-4afb-a9bf-1a0ec795e68f%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> Please update your bookmarks! We have moved to https://discuss.elastic.co/
> ---
> 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/71e4219a-e9a6-4fa0-a289-9bf3fb6e50a3%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Please update your bookmarks! We have moved to https://discuss.elastic.co/
--- 
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/CAECdJzCt_%2BVvB8JqWRfT7Xs-9%3DHb_Jg-s6Yxarq%2B01b9mn5ggg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to response null value fields when query using "fields"

[Xudong You]

Thanks your reply!
But why if I remove "fields" from query DSL, then I can see those null 
value fields in ES response?

On Tuesday, May 26, 2015 at 4:19:30 PM UTC+8, Allan Mitchell wrote:
>
> Hi
>
> If you have a field that has null as a value then as far as the inverted 
> index is concerned for that document it doesn''t exist
>
> Have a look at this
>
>
> https://www.elastic.co/guide/en/elasticsearch/guide/current/_dealing_with_null_values.html
>
>
> On 26 May 2015 at 08:11, Xudong You > 
> wrote:
>
>> I used "fields" to limit only return selected fields:
>> {
>> "fields" : ["Title", "Price"],
>> "query" :{
>>  ...
>> }
>> }
>>
>> The Price fields might be null for some of the documents, I found that 
>> only when "Price" field value is NOT null, it is returned in ES response, 
>> otherwise, it is missing in response. But if I remove "fields" from the 
>> query, the null value field will appear in response.
>>
>> Is it by design of Elasticsearch? How to return the null value fields in 
>> response even using "fields" in query?
>>
>>  -- 
>> Please update your bookmarks! We have moved to 
>> https://discuss.elastic.co/
>> --- 
>> 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/3c91fd31-0e13-4afb-a9bf-1a0ec795e68f%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
Please update your bookmarks! We have moved to https://discuss.elastic.co/
--- 
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/71e4219a-e9a6-4fa0-a289-9bf3fb6e50a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to response null value fields when query using "fields"

[Allan Mitchell]

Hi

If you have a field that has null as a value then as far as the inverted
index is concerned for that document it doesn''t exist

Have a look at this

https://www.elastic.co/guide/en/elasticsearch/guide/current/_dealing_with_null_values.html


On 26 May 2015 at 08:11, Xudong You  wrote:

> I used "fields" to limit only return selected fields:
> {
> "fields" : ["Title", "Price"],
> "query" :{
>  ...
> }
> }
>
> The Price fields might be null for some of the documents, I found that
> only when "Price" field value is NOT null, it is returned in ES response,
> otherwise, it is missing in response. But if I remove "fields" from the
> query, the null value field will appear in response.
>
> Is it by design of Elasticsearch? How to return the null value fields in
> response even using "fields" in query?
>
>  --
> Please update your bookmarks! We have moved to https://discuss.elastic.co/
> ---
> 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/3c91fd31-0e13-4afb-a9bf-1a0ec795e68f%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Please update your bookmarks! We have moved to https://discuss.elastic.co/
--- 
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/CAECdJzD0GgOE2wz2uoZ974AZtP4BbB%2BK%3DOUbbz5HTQ8rCKh9oA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Kibana 4 Process Crash

[VV]

Hello everyone
I have a problem with Kibana 4, every moorning I open my browser on kibana 
page and I received the message "Waiting for elasticsearch is loading 
messages", the page don't get results, If I refresh the page Kibana Process 
go down.

I had the following configuration on 2 servers:

- 1 with Logstash that send data to elasticsearch 1.5.0
- 1 with Elasticsearch 1.5.0 and Kibana 4.0.2 

Running on RHEL 5.5 x64.

Could anyone help me?
Thanks in advance.

VV

-- 
Please update your bookmarks! We have moved to https://discuss.elastic.co/
--- 
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/3efda0c2-dced-488f-a40f-e0c0785cfd04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Indexing files (docx, xlsx etc)

[Mark Walkom]

For those you will want to use something like Apache Tika, there is nothing
in the ELK stack to do these sorts of files.


PS - We're moving to https://discuss.elastic.co/, please join us there for
any future discussions!

On 26 May 2015 at 17:47, Gary Wenneker  wrote:

> Is there a way to index files in ES using a stream so that the files are
> sent to ES in chunks?
>
> --
> Please update your bookmarks! We have moved to https://discuss.elastic.co/
> ---
> 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/469fbbd2-f66c-4d0b-8903-24aead01af96%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Please update your bookmarks! We have moved to https://discuss.elastic.co/
--- 
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/CAEYi1X-3Fcquim-7qcFfx3P8Mvk_Bp%3DzUmsb%2BqC8MXZqX%3D02kg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Indexing files (docx, xlsx etc)

[Gary Wenneker]

Is there a way to index files in ES using a stream so that the files are 
sent to ES in chunks?

-- 
Please update your bookmarks! We have moved to https://discuss.elastic.co/
--- 
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/469fbbd2-f66c-4d0b-8903-24aead01af96%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How to response null value fields when query using "fields"

[Xudong You]

I used "fields" to limit only return selected fields:
{
"fields" : ["Title", "Price"],
"query" :{
 ...
}
}

The Price fields might be null for some of the documents, I found that only 
when "Price" field value is NOT null, it is returned in ES response, 
otherwise, it is missing in response. But if I remove "fields" from the 
query, the null value field will appear in response.

Is it by design of Elasticsearch? How to return the null value fields in 
response even using "fields" in query?

-- 
Please update your bookmarks! We have moved to https://discuss.elastic.co/
--- 
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/3c91fd31-0e13-4afb-a9bf-1a0ec795e68f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.