}
}
Am Dienstag, 25. November 2014 13:34:08 UTC+1 schrieb Erlendur Hákonarson:
Thanks Ramy
but how does that strategy work
is there any doc on strategies I can view?
the only one I found was on the jprante github wiki and that only
describes the simple strategy
and if I am using tables
Hi Erlendur,
In your case, you should use the column strategy instead of simple one. The
column strategy requires two columns in the SQL DB.
- cerated_at
- update_at
Cheers, Ramy
Am Dienstag, 25. November 2014 11:04:17 UTC+1 schrieb Erlendur Hákonarson:
Hi I am new to ES but my company
Sorry...
- created_at
- updated_at
Am Dienstag, 25. November 2014 11:55:18 UTC+1 schrieb Ramy:
Hi Erlendur,
In your case, you should use the column strategy instead of simple one.
The column strategy requires two columns in the SQL DB.
- cerated_at
- update_at
Cheers, Ramy
Am Dienstag
: transactions_test,
type: transaction_test,
sql: SELECT * from my_transaction_table
}
}
Am Dienstag, 25. November 2014 13:34:08 UTC+1 schrieb Erlendur Hákonarson:
Thanks Ramy
but how does that strategy work
is there any doc on strategies I can view?
the only one I found was on the jprante
every minutes. But I want to avoid, that ES
execute the update for existing document with no changes. When I take a
look at the ES. I see that river has updated all document.
Is there any solution for my case?
Thank you for any advice for the nice plugin
Ramy
Am Donnerstag, 22. Mai 2014 11:54:18
Hi everyone,
I'm using the river plugin from
https://github.com/jprante/elasticsearch-river-jdbc Does anyone has
experience with it? I'm getting while the login process an access denied
message!
I configured my river like is expected in the documentation:
curl -XPUT
Well i have solved the problem. Everything is working fine :)
The db user was not allowed to use from the internet/intranet. So i added a
new db user with appropriate rights in mysql.
thx
Am Donnerstag, 13. November 2014 11:11:35 UTC+1 schrieb Ramy:
Hi everyone,
I'm using the river plugin
Maybe this would help you:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-lang-analyzer.html#swedish-analyzer
in the example they use only swedish
Am Dienstag, 11. November 2014 14:55:47 UTC+1 schrieb Linus Pettersson:
Hello
I'm trying to use Swedish stemming
This is how regex works.
v = The word must start with the character v
. = Any character after v
* = Zero or more characters after . till the end of the row
Am Donnerstag, 23. Oktober 2014 08:27:24 UTC+2 schrieb Gargoyle:
Hi,
I have a index of documents, where all string fields are
Hi everyone,
How can i use a variable inside include area? is it possible? how?
I'm using groovy script in my query and it looks like:
GET /my_index/my_type/_search
{
_source: false,
query: {
bool: {
...
}
},
aggs: {
group: {
nested: {
path: my_path
I have solved with RegEx
GET /my_index/my_type/_search
{
_source: false,
query: {
bool: {
...
}
},
aggs: {
group: {
nested: {
path: my_path
},
aggs: {
path_id: {
terms: {
field: my_path.id,
lang: groovy,
You should use path for your nested fields!!!
please read this article:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-nested-query.html
Am Mittwoch, 15. Oktober 2014 10:38:24 UTC+2 schrieb José Ramón Palanco:
When I try to query a nested field that exists, I
,
linked_docs.page
]
}
}
}
}
]
}
}
}
Cheers, Ramy
Am Montag, 13. Oktober 2014 12:24:42 UTC+2 schrieb Michael Werner:
I am pretty new to ES and have a problem that I could not yet solve using
the docuemntation, so any
Have you tried like this?
query: {
match: {
test: {
query: routers and switches for home,
*operator: and*
}
}
}
--
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
I'm trying to query two types and want to boost on of them!
I have tried this way. But i wan't successful. Can someone help? How can I
do boost a type?
GET /my_index/*my_type1*,*my_type2*/_search
{
query: {
match: {
value.autocomplete: lorem ipsum
},
function_score: {
i have solved it in that way...
GET /my_index/my_type1,my_type2/_search
{
query: {
function_score: {
query: {
match: {
value.autocomplete: lorem ipsum
}
},
functions: [
{
script_score: {
lang: groovy,
Can someone tell me, why the highlighting works not always? what is my
mistake?
This is my mapping:
curl -XPUT http://localhost:9200/my_index; -d'
{
settings: {
analysis: {
analyzer: {
autocomplete: {
type: custom,
tokenizer: ngram_tokenizer,
Can someone tell me, why the highlighting works not always? what is my
mistake?
This is my mapping:
curl -XPUT http://localhost:9200/my_index; -d'
{
settings: {
analysis: {
analyzer: {
autocomplete: {
type: custom,
tokenizer: ngram_tokenizer,
- Petra
- etc.
thx, Ramy
--
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
Have you tried something like that:
...
date_histogram : {
field : date,
interval : month,
format : M
}
...
And the link for the date format:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-aggregations-bucket-daterange-aggregation.html#date-format-pattern
Try something like that...
aggs: {
agg_name: {
terms: {
field: my_field,
size: 100
}
}
}
Am Donnerstag, 14. August 2014 16:40:11 UTC+2 schrieb julie dabbs:
Unfortunately this does not change the total of results returned
On Thursday, August 14, 2014
You can try to save the user _id in each post!!! maybe it solves your
problem
Am Donnerstag, 14. August 2014 15:34:39 UTC+2 schrieb ali koyuncu:
I have an index named DataIndex. It has two types: posts and users.
The posts have an user which has small info like just id, name but it has
I'm very new in Elasticsearch and have a question about the hierarchical
tokenizer of a path. Here is my code example:
My mapping code:
PUT /my_index
{
settings: {
analysis: {
analyzer: {
path-analyzer: {
type: custom,
tokenizer: path-tokenizer
23 matches
Mail list logo