Re: Different configuration servers for master and slave
No. Which copy of the shard is the replica and which is the slave can change all the time. Most actions take almost the same amount of CPU/memory/time on master as slave. If you find this not true for your workload your best bet is to fiddle with the allocation parameters and raise the weight of the one for masters. This will cause elasticsearch to tend to spread masters move evenly. Sent from my iPhone > On Jun 1, 2014, at 8:27 AM, Tamanjit Bindra wrote: > > Hi all, > We are planning to migrate from 0.90 version of ES to the latest version. > Also we are revisiting our production architecture. > > Currently we have one master and one replica of the data. Both currently are > 16G ram servers. > My question is, is it advisable to have a better configuration master sever > ie say 32G ram on master and 16G ram on a slave node? > > -- > 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/CADA%3D_UP8eFs5vgwaRB7Yiu7%2BFxpbjA6XX%3DcK4COJxUker2EaWw%40mail.gmail.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/00B985DD-13E9-422A-B3F6-3A7A6D5F4386%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Hide some system fields
Source filtering is similar but normally returns nicer results.
Sent from my iPhone
> On May 29, 2014, at 8:29 AM, Florentin Zorca wrote:
>
> Hi,
>
> try using fields to specify only the fields you are interested in:
>
> http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-request-fields.html#search-request-fields
>
> Your query should then be something like this:
> {"fields":["date"], "from":0, "size":1000}
> Kind Regards,
> Florentin
>
> Am Donnerstag, 29. Mai 2014 13:11:07 UTC+2 schrieb Сергей Шилов:
>>
>> Hi all!
>> I use elasticsearch in a high-load project where an urgent need to save
>> traffic.
>> I have a some queries like this:
>> curl -XGET
>> 'http://localhost:9200/testindex/testmapping/_search?pretty&scroll=5m' -d
>> '{"from":0, "size":1000}'
>>
>> {
>> "_scroll_id" :
>> "cXVlcnlUaGVuRmV0Y2g7MjszMjp6TmdjNmxkM1NtV1NOeTl5X3dab1FnOzMxOnpOZ2M2bGQzU21XU055OXlfd1pvUWc7MDs=",
>> "took" : 2,
>> "timed_out" : false,
>> "_shards" : {
>> "total" : 2,
>> "successful" : 2,
>> "failed" : 0
>> },
>> "hits" : {
>> "total" : 15457332,
>> "max_score" : 1.0,
>> "hits" : [ {
>> "_index" : "testindex",
>> "_type" : "testmapping",
>> "_id" : "mo7vQrWUTquBRowjq2AVkw",
>> "_score" : 1.0, "_source" :
>> {"reffer_id":"","date":"2013-05-31T00:00:00","source":5,"user_id":"2fdfdf0fbbce603cf24c0eee7dabf28c"}
>> }, ]
>> }
>> }
>>
>> Can I exclude some system fields (like _shards.*, hits._index, hits._type,
>> hits._id, hits._score)? I found how exclude source fields, but not system.
>> Also I need to get _timestamp field in _source rows. It generated from
>> 'date' field:
>> '_timestamp' => array(
>> 'enabled' => true,
>> 'path' => 'date',
>> 'format' => "-MM-dd'T'HH:mm:ss"
>> )
>>
>> Thanks
>
> --
> 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/16245f90-64fc-4a39-adf4-71663e91d950%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/B13EA515-40ED-4F09-97BA-799B23B98DF8%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: How can connect to elastic Search from public ip
Ssh tunneling is how I do it. There is always a way to get to port 22. Sent from my iPhone > On May 27, 2014, at 7:30 AM, David Pilato wrote: > > Is the 9200 port open? > > -- > David ;-) > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > > Le 27 mai 2014 à 05:39, Mas Hgnis a écrit : > > I have installed elastic search on my linux server where my website is > running and I able to access the elastic search using curl > http://localhost:9200/_cluster/health?pretty from local box. > > But for debugging purpose (using head/kopf) i would like access the same from > my public internet but when I am trying it with help > http://xxx.xx.xx.xxx:9200/_cluster/health?pretty, I am not able to connect. > (I am able to ping the ip) > > > Please help in understanding the same and let me know what configurations are > required so as to access elastic search. > > > > Thanks in advance. > -- > 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/02c100df-56ee-434d-8961-08baf5a29594%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/E8B1E66E-40D6-4DF3-869F-B24AA03631F8%40pilato.fr. > 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/81FAF8E5-C9AE-4E4D-B0D2-42961675553C%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Facetted Search Misbehaving
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
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.
Re: bulk indexing and number of shards
Sorry, you can't reduce it. I imagine the performance increase you get is because the merge logic is per shard so it does less when there are more shards for the same data. You can likely get similar numbers if you set the refresh interval to -1 and play with the merge policy before the bulk load. You'd want to reset it afterwords and then run an optimize. This amounts to the same thing as starting with more shards and merging them. Mostly. I think. Sent from my iPhone > On Apr 12, 2014, at 4:05 PM, euneve...@gmail.com wrote: > > Hi, > > I'm testing on a single node. > > I find I can get better bulk indexing performance when the index has more > shards. Does that make sense ? > > My own theory is that when I have multiple bulk clients, then by increasing > shards the server achieves better concurrency (?) > > So if I increase the shards to say 30, and get a good indexing run... is it > possible to reduce the number of shards subsequently.. or does it matter if > the number remains at say 30? > > Thanks, > > > -- > 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/d6006698-0ced-43f4-959f-52def820013f%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/0CCF99CF-B24F-4C39-9C12-703039EB5BB1%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Elasticsearch phrase suggester
Set the min to 2 and max to either 2 or 3 and emit unigrams. That'll get it
working. Also you probably want to set max errors to a number > 1 because .5
means 50% which can get quite large if someone types 20 terms.
That's been my experience with it.
Nik
Sent from my iPhone
> On Apr 10, 2014, at 7:46 PM, Adrien Grand
> wrote:
>
> Hi,
>
> You would get better results with the phrase suggester by using an analyzer
> that has a shingle filter[1]. This filter will help Elasticsearch compute
> frequencies of pairs of terms. Without it, it falls back to single-term
> frequencies, so in your case it would only consider the frequencies of
> 'Johnny' and 'Depp' instead of the frequency of 'Johnny Depp' as a whole.
>
> [1]
> http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-shingle-tokenfilter.html
>
>
>> On Wed, Apr 9, 2014 at 5:57 PM, mstrasser
>> wrote:
>> I would like to use "Phrase Suggester". I've got a problem. When typing
>> "johni depp", it returns several results in this order:
>>
>> john depp
>> johnny depp
>> joann depp
>> johnn depp
>> How can I sort the suggestions using json so that the first result is
>> "johnny depp"? I've tried doing this with a phonetic indexer, but without
>> success.
>>
>> This is my configuration:
>>
>> Query :
>>
>> {
>> "query": {
>> "multi_match": {
>> "query": "johni depp",
>> "fields": [
>> "fullName.word"
>> ],
>> "operator": "and"
>> }
>> },
>> "suggest": {
>> "text": "johni depp",
>> "film": {
>> "phrase": {
>> "analyzer": "whitespace-fullName",
>> "field": "fullName.whitespace",
>> "size": 5,
>> "real_word_error_likelihood": 0.95,
>> "max_errors": 0.5,
>> "gram_size": 2
>> }
>> }
>> },
>> "from": 0,
>> "size": 1,
>> "sort": [],
>> "facets": []
>> }
>> Indexer (I use Elastica, but it's same thing):
>>
>> $elasticaIndex->create(
>> array(
>> 'number_of_shards' => 4,
>> 'number_of_replicas' => 1,
>> 'analysis' => array(
>> 'analyzer' => array(
>> 'autocomplete-index-fullName' => array(
>> 'tokenizer' => 'standard',
>> 'filter'=> 'asciifolding, lowercase,
>> edgeNGram'
>> ),
>> 'autocomplete-search-fullName' => array(
>> 'tokenizer' => 'standard',
>> 'filter'=> 'asciifolding, lowercase'
>> ),
>> 'word-fullName'=> array(
>> 'tokenizer' => 'keyword',
>> 'filter'=> 'lowercase'
>> ),
>> 'whitespace-fullName' => array(
>> 'tokenizer' => 'whitespace',
>> 'filter'=> 'lowercase'
>> ),
>> ),
>> 'filter' => array(
>> 'edgeNGram' => array(
>> 'type' => 'edgeNGram',
>> 'min_gram' => 1,
>> 'max_gram' => 15
>> )
>> )
>> )
>> ),
>> false
>> );
>> Mapping :
>>
>> $mapping->setProperties(
>> array(
>> 'fullName' => array('type' => 'string',
>> 'fields' => array(
>> 'autocomplete' => array(
>> 'type'=> 'string',
>> 'index_analyzer' =>
>> 'autocomplete-index-fullName',
>> 'search_analyzer' =>
>> 'autocomplete-search-fullName'
>> ),
>> 'word' => array(
>> 'type'=> 'string',
>> 'analyzer' => 'word-fullName'
>> ),
>> 'whitespace' => array(
>> 'type'=> 'string',
>> 'analyzer' => 'whitespace-fullName'
>> ),
>> )),
>> )
>> );
>> Examples of referenced values:
>>
>> John Cleese
>> John Gemberling
>> Johnny Hallyday
>> Johnny Depp
>> Joann Sfar
>> Joanna Rytel
>> Samuel Johnson
>> Johnson Traoré
>> Thanks in advance.
>>
>>
>> View this message in context: Elasticsearch phrase suggester
>> Sent from the ElasticSearch Users mailing list archive at N
Re: JSON validation by Sense
The one in chrome will refuse to auto indent invalid json, I believe. Sent from my iPhone > On Mar 28, 2014, at 8:41 AM, aristechnologypartn...@gmail.com wrote: > > perhaps fairly naive question, but does Sense let you validate JSON documents > before they are sent to ES? Thx. > > I'm using one that comes with "latest" Marvel and only see "Request" and > "Copy as cURL" and "Auto Indent" functions. > -- > 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/84b0c616-4f62-4219-9efa-0d293eebd761%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/2CE1D3EF-7A05-4CD3-A0A5-5F0BA147F2C1%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: What happens (or should happen) if your elasticsearch configurations don't match?
My guy says some config will matter on each node (minimum master nodes) and the rest will only use the master's value. Sent from my iPhone > On Mar 7, 2014, at 5:15 AM, Robin Clarke wrote: > > I'm wondering if anyone knows (can't easily test right now) what happens if > your elasticsearch configurations on different nodes don't match: > e.g. > if you have index.number_of_replicas: 0 on one node, and 1 on another - will > replicas be made, or not? > Is there any reasonable use of having different values here? > > Cheers, > -Robin- > -- > 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/2f8f22c5-c8ca-48f2-8517-8c6e93a98eb1%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/647CB501-5634-4404-87CC-B322949CC316%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Setting up elasticsearch to scale: shards per index
If you have an index per (some time period) then you can create the new indexes with more shards when you have more hardware and leave the old ones with their old number. You can also allocate more shards then noses in preparation for getting more nodes. I believe those are the standard tactics for log stash. Sent from my iPhone > On Feb 10, 2014, at 2:23 PM, Matt wrote: > > Hey all! > > Background: I am using elasticsearch with logstash to do some log analysis. > My use-case is write-heavy, and I have configured ES accordingly. After > experimenting with different setups, I am considering the following > implementation: > > separate log processing from ES cluster > 1x Logstash server > > 2x ES server (1x master, 1x data-only): > - 17GB memory > - Running single ES node with 9GB allocated memory > > This should be plenty of memory for the relatively small dataset I am > starting with, and will expand as needed. However, I have the following > questions/concerns: > > It is my understanding that, ideally, we want one shard per index per node > (plus an additional replica shard per primary shard per node assuming number > of replicas is set to 1), meaning in this setup, I would set number of shards > per index to 2. Each index is, as of now, relatively small (~500MB), so two > shards should be fine. However, as we scale the project, the indexes will > grow, and we will eventually want to split them into more shards. On the > hardware side, the ES servers are relatively lightweight. As we scale, we > have the option to simply beef up the hardware. Finally, my understanding is > that increasing the number of shards/index down the line requires a full > reindexing of the data, which I would like to avoid. > > It seems to me that I would be better off setting shards/index to 4, in > anticipation of future scaling. Are there costs to this that I am missing? > > What about starting off with a single ES node on a beefier server? Should I > be concerned about availability with a single-node cluster (no replicas)? > > Thanks for reading :) > -- > 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/6c988e28-58dc-4af7-86a9-16d763ce4ff7%40googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- 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/2864CCBA-4F2F-4F88-A734-300292CD67FB%40gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Are the insert operations to elasticsearch asynchronous in nature
If you are using the java API the answer is maybe, it depends on how you use it. In addition, even if you use the synchronous API you have to wait for a refresh for you data to be searchable. By default they happen every second. Sent from my iPhone > On Jan 31, 2014, at 6:21 AM, sowjanya wrote: > > I am having a client node and a data node. i am using the client node to > communicate to data node. My question is when i perform an insertion from > client node does the program control returns to client node once the > information is sent to data node over the network or is it blocked till the > data is inserted and indexed on the data node. > > Please help me. > > > > -- > View this message in context: > http://elasticsearch-users.115913.n3.nabble.com/Are-the-insert-operations-to-elasticsearch-asynchronous-in-nature-tp4048555.html > Sent from the ElasticSearch Users mailing list archive at Nabble.com. > > -- > 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/1391167290884-4048555.post%40n3.nabble.com. > For more options, visit https://groups.google.com/groups/opt_out. -- 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/81D2EDE3-7106-4A8B-A521-B650F8867772%40gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Native client or REST
The native client is lower overhead but you have to use the same version the client as you do Elasticsearch and you should use the same JVM version as well. If you do java then those are the trade offs. Sent from my iPhone On Jan 23, 2014, at 9:19 AM, Lukáš Vlček wrote: >> Question: If I index the files using native JAVA API, will I be able to >> perform queries/searches from the web application via http/REST API? > > Yes. > -- > 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/CAO9cvUZKd-oWY%3DrZuhQgMeps85TL3qEfKvueFnH6mmDxHRi1nw%40mail.gmail.com. > For more options, visit https://groups.google.com/groups/opt_out. -- 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/BF231D40-F1F9-48AC-84F1-9EEE7F8A1FC2%40gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: boosting according to users preferences
Have a look at the function score query and for using filters with a boost
factor with it.
Sent from my iPhone
> On Jan 17, 2014, at 5:56 PM, khaled gomaa wrote:
>
> Im creating a targeted ads system.
> I have a machine learning part which analyzes the user preference and send me
> a list with scores of these tags.
> I want to boost those tags with their corresponding value. eg, { 'gaming':
> 10, sports: 5, 'movies': -1}
> --
> 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/02475bef-8c39-4c51-a0b6-ddf5cc2d29c6%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
--
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/8660484A-6480-42B0-AC9A-6EC9D44C9817%40gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Upgrade from 0.90.5 to 0.90.9
I was wondering if you technically could downgrade so long as you don't write or optimize. Not that I suggest it, but it would be neat to know Sent from my iPhone > On Jan 5, 2014, at 2:00 PM, "joergpra...@gmail.com" > wrote: > > 0.90.9 uses Lucene 4.6 which is a pretty significant feature update. > > http://lucene.apache.org/core/4_6_0/changes/Changes.html > > Jörg > > >> On Sun, Jan 5, 2014 at 6:58 PM, Robin Verlangen wrote: >> I have already read the release notes, and apart from a minor Lucene upgrade >> to 4.0.6 there's not much that seems to be in the way of doing a roling >> upgrade. > > -- > 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/CAKdsXoFLvK%2BqfzSygTXhW05KeXO1QuanK1uYW25Ra7Ggek500Q%40mail.gmail.com. > For more options, visit https://groups.google.com/groups/opt_out. -- 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/B1CE69BF-1864-4750-915C-EC66A5707626%40gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
