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 vincenzo.vign...@gmail.com wrote:
Hello everyone
I have a problem with Kibana 4, every moorning I open my browser on kibana
page and I
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 sagarshah1...@gmail.com a écrit :
Hello everyone,
We are trying to replace application log storage from postgres db with
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: {
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,
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
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 :
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
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 g...@gary.nu wrote:
Is there a way
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
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
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:
-
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
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
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*
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
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
Try adding another / to the end - http://localhost:9200/_plugin/kopf/
On 26 May 2015 at 22:34, Invest Ict i...@investict.nl 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
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
18 matches
Mail list logo
