Hi, a bit more information.
I tried adding a custom analyzer based off a recommendation I saw online
somewhere. This partly works in that it's not tokenising. But I can't do
wildcard searches in Kibana on the fields, and they're now case sensitive :(
curl
Hey,
maybe you should ask your developers, why they recommended logstash for
this, I cant follow here (perhaps there is some export functionality in
your SQL server, which an input of logstash can use?). Would be interested
in reasons in this case.
--Alex
On Wed, Jan 8, 2014 at 5:26 PM, jsp
Hey,
a couple of things:
1. Did you check the log files? Most likely in /var/log/elasticsearch if
you use the packages. Is there anything suspicious at the time of your
outage? Please check your master node as well, if you have one (not sure if
it is a master or client node from the cluster
Then you can put it in $KIBANA_ROOT/app/dashboards and load it from there.
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
web: www.campaignmonitor.com
On 9 January 2014 19:32, vineeth mohan vm.vineethmo...@gmail.com wrote:
Hello Jay ,
An
Hey,
after having a very quick look, it looks like a bug (or wrong
documentation, need to check further). Can you create a github issue?
Thanks!
--Alex
On Wed, Jan 8, 2014 at 11:08 PM, Gabe Gorelick-Feldman
gabegorel...@gmail.com wrote:
The documentation on URL-based access
Hi,
I have following Synonyms that I want to configure.
software engineer = software engineer, se,
senior software engineer = senior software engineer , see
team lead = team lead, lead, tl
So that If I searched for se or Software Engineer it should return me the
records having software
Your configuration looks good to me.
I modified your spring file to add a node and change server location:
elasticsearch:node properties=esProperties name=node /
elasticsearch:client id=esClient2 mappings=experiment2/NewTitles
esNodes=localhost:9300
Hi Chris,
Could you try to escape “-“ in query for “not_analyzed” field?
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html#_reserved_characters
I hope this helps.
Regards,
Jun Ohtani
joht...@gmail.com
blog :
Also I have another scenario where my index is having words like
software engineer, se, --- this should get seached when I do search on
Software engineer
team lead, lead, tl --- this should get seached when I do search on Team
Lead
Following are the query to create the records.
curl -XPUT
Thanks David .
* Yes , I test it with curl. If the json data is not too big, There
is no problem. The test json format is following:*
*{*
*name:[user1,user2,user3,],*
* product:{},*
* price:{}*
*}*
*The difference is the two json data is :*
*The last json data include too many
Hi all,
I am wondering how the ElasticSearch deal with different document with
different encoding, such as different language.
Could you provide me some tutorial about it? Do I need to manually specify
the encoding format of the document when posting?
Best,
Ivan
--
You received this
Hi!
I am using ES together with logstash and we are indexing simple access log
files.
Our problem is that we want to now the number of image views for a resource
which is determined by a specific
REST url:
GET /resource/id/image = i.e GET /resource/abcde/image
This results in millions of
Hi Martijn,
Thanks for your answer. You can find in the gist below some HTTP
conversations made on my ES 0.90.6 node, as well as a link to the Java code
responsible for the calls:
https://gist.github.com/jblievremont/8331460
Please note that the issue appears only when combining scan/scroll
I see. You probably have to merge mappings with very big mappings!
What is your application searching for? Logs? Users?
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 9 janv. 2014 à 10:06, xjj210...@gmail.com a écrit :
Thanks David .
Yes , I test it with curl.
Okay, thank you for your response, here is an attempt of an example of what
I am trying to achieve.
Lets say I have the documents;
{
id: 1
name: peter
class: 2
grade: b
hair:grey
}
{
id:2
name: paul
class:2
grade:b
hair:purple
}
{
id:3
name:john
class:1
grade:b
hair:grey
I have created a timestamp field (not be confused with _timestamp) and want
to sort timestamp field in descending order. But the result contains some
records out of order.
Mapping and the sorting criteria look like :
timestamp:{type
:date,format:dateOptionalTime,include_in_all:false}
My application has the pagination requirement for search. I am using the
offset and size option to achieve the pagination.
Making quick clicks on pagination sometimes does not give results at all.
Does the asynchronous search call bringing any side effects like this?
Thanks,
--
You
For redundancy purposes, our system is split into two datacenters. One of
the DCs is considered central where all the backoffice systems reside and
the other is edge. Recently we started using Logstash with ElasticSearch
and Kibana. The architecture we had is:
- Scribe server on each
Good Morning,
I am running a very basic config of logstash, with the embedded
elasticsearch.
I am able to launch the logstash embedded elasticsearch successfully,
whilst using a local disk for the data directory, however when I use the
option : -Des.path.data to specify the data
issue solved:
in river code, when fetching data from Casandra it
uses HFactory.createRangeSlicesQuery(keyspace, STR, STR, STR); to get data
and the table which i was using to get data contain Primary Key as int id,
after changing that to text it starts pulling data from Cassandra to ES.
Thanks
We don't have that at this time.
Basically, elasticsearch nodes are very often in a backend layer so securing
transport is not something really needed as it comes also with a cost.
Could you secure your transmissions on a network level?
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr /
So after trying around, I have found out that if just have name and
description and not task.name and task.description in the highlight
section, the highlighting works. So is TYPE.FIELD not supported for
highlights in 0.90.x? Or could I do it with some other syntax?
If not, how do you solve
When you delete the river (remove _meta doc).
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 9 janv. 2014 à 14:58, shamsul haque shams...@gmail.com a écrit :
Hi,
i have configured and started river with my ES. But how may i stop OR close
my running river, if i want
There is example in index and query in this SO
http://stackoverflow.com/questions/8734888/how-to-search-for-utf-8-special-characters-in-elasticsearch
hth
Jason
On Thu, Jan 9, 2014 at 5:13 PM, HongXuan Ji hxua...@gmail.com wrote:
Hi all,
I am wondering how the ElasticSearch deal with
Sorry my fault. I stand corrected. There is replication=sync and
consistency=all, but just for index creation that is triggered by a
document creation, and the index does not yet exist (auto creation). It's
not there for explicit index creation (where there is no document to be
created).
In case
Opened an issue: https://github.com/elasticsearch/elasticsearch/issues/4668
On Thursday, January 9, 2014 3:39:39 AM UTC-5, Alexander Reelsen wrote:
Hey,
after having a very quick look, it looks like a bug (or wrong
documentation, need to check further). Can you create a github issue?
He is a little example of query time multi-word synonyms:
https://gist.github.com/mattweber/7374591
Hope this helps.
Thanks,
Matt Weber
On Thu, Jan 9, 2014 at 12:56 AM, Jayesh Bhoyar jsbonline2...@gmail.comwrote:
Also I have another scenario where my index is having words like
software
Use a filtered query, not an outer filter. You only want to use that
outer filter when you are faceting and don't want the filter to change the
facet counts.
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-filtered-query.html
Thanks,
Matt Weber
On Thu, Jan 9,
I'm looking to boost matches that where all the terms in the field match
more than I'm getting out of the default similarity. Is there some way to
ask Elasticsearch to do that? I'm ok with only checking in some small
window of top documents or really anything other than a large performance
hit.
Nik,
No, there is not.
There's a work-around in which the number of terms in a field can be stored
in another field during indexing time. And then you can analyze your query
string to count the number of terms, and then use that count to match
against the documents that have the same count.
Perhaps I am missing some functionality since I am still on version 0.90.2,
but wouldn't you have to disable/enable allocation after each server
restart during a rolling upgrade? A restarted node will not host any shards
with allocation disabled.
Cheers,
Ivan
On Wed, Jan 8, 2014 at 5:48 PM,
Chris,
I updated one of my tests to reproduce your issue. My text field is a
multi-field where *text.na* is the text field without any analysis at all.
This Lucene query does not find anything at all:
{
bool : {
must : {
query_string : {
query : *text.na:Immortal-Li**
*Never, never, never* kill -9 and expect any application to properly and
cleanly shut down. Never.
The -9 signal cannot be caught by the process to which it is directed. The
process is ended in the middle for whatever it is doing.
Issue a normal kill, and then ES (via the JVM) will have a
Hey all,
I just started using ElasticSearch with LogStash and Kibana. I'm able to
extract fields from my log statements using logstash/grok. In Kibana I
have taken some of these fields and created stats panels using them for
stats like total/mean/min/max which works great for just seeing a
Is filtering on the _size field allowed on percolate requests?
Adding into a percolate query in either a filter or the query section a
_size range matches no documents.
Walking through reproducing the problem:
Register the query:
curl -XPUT
I am having trouble with a filter. I have items in my index, with nested
ratings
curl -XPOST http://localhost:9200/nestedfilters/item/_mapping; -d '
{
item : {
properties : {
description : {
type : string
},
ratings : {
Just wanted to add a quick note: long recovery times (due to divergence of
shards between primary/replica) is an issue that we will be an addressing.
No ETA as of yet, but something that is on the roadmap. :)
-Zach
On Wednesday, December 4, 2013 7:48:04 PM UTC-5, Greg Brown wrote:
Thanks
Oh right. That should have been obvious. It seems to be working great that
way. Thanks!
Nathan
On Jan 9, 2014, at 1:10 PM, Sloan Ahrens sl...@stacksearch.com wrote:
You were close. You just had the nested and not filters in the wrong
order, basically.
Your (first) query says return
I am reading data from Sql Server database/table using jdbc-river
currently. As of now I have created a type for each table in my database.
As next step in my implementation I would like to use parent/child types so
that I can translate the relationship between my sql tables and store them.
That setting tells the nodes to hold the shards they currently have, and in
the event of a node going down for a restart/upgrade, don't redistribute
across the cluster.
When you bring the rebooted/upgraded node back it'll locally reinitialise
the shards it still has.
You can set that setting back
That is definitely not the behavior I have ever seen with elasticsearch. If
you restart a node with allocation disabled, the restarted node will have
no shards and the shards that it should contain are marked as unassigned. I
have never seen a node reinitialize the shards it has.
Cheers,
Ivan
Hi, Jason
Thanks for the reply. I read the post.
I am also wondering what the encoding process of ES works and what's the
underlying encoding used in ES to store data?
Do you have some documents about these?
Thanks,!
Regards,
Ivan
Jason Wee於 2014年1月9日星期四UTC+8下午10時08分26秒寫道：
There is
Hi all,
I post several large text files, which are about 20~30MB and contains all
the text, into ES. And I use the attachment mapper to be the field type to
store these file.
It cost memory very much. Even when I post one file, the used memory grows
from about 150MB to 250MB. BTW, I use the
Hi Chris,
I recreate your issue to the following gist.
https://gist.github.com/johtani/8346404
And I try to change query as follows:
User_Name.raw:bob.smith-jones - matches
User_Name.raw:bob.smi* - matches
User_Name.raw:bob.smith-j* - matches
User_Name.raw:bob.smith\-j* - matches
I use
Try with adding ?routing=PARENTID
where PARENTID is equal to the parent ID for a given child
HTH
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 10 janv. 2014 à 01:09, Yuri Panchenko yuri.panche...@gmail.com a écrit :
Hi,
I'm doing a simple test with 1.0.0 Beta 2. I've
If it helps, here are my index settings and mappings. Note that I chose the
name text.na as the non-analyzed form, not text.raw. Perhaps I should
follow convention? But for now, a rose by any other name is still not
analyzed:
{
settings : {
index : {
number_of_shards : 1,
A quick guess: The first one works because the first document for that type
is indexed and therefore the type is created when the operation returns.
But the second one doesn't work because there is a refresh interval between
the completion of a bulk load operation and the actual document being
yes! adding a sleep after Future.get() of bulk op 'fixed' my test - thank
you.
what you said re: bulk op was submitted but not processed makes sense
(perhaps there is a separate API to query for op's completion status?) but
what is puzzling to me is that comments in source of *BulkResponse* seem
Had to add this to /usr/share/elasticsearch/bin/elasticsearch
So any startup of elasticsearch will pickup
ES_JAVA_OPTS=-Des.config=/etc/elasticsearch/elasticsearch.yml
-Des.path.conf=/etc/elasticsearch/ -Des.path.home=/usr/share/elasticsearch
-Des.path.logs=/var/log/elasticsearch
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 lzy3...@gmail.com napsal(a):
Or some detail introduction
50 matches
Mail list logo
