When sending a PutMappingRequest I used to receive back a true value for
acknowledged.
client.admin().indices().putMapping(new
PutMappingRequest(indexName).source(value)).actionGet().acknowledged
After my last update from master and build this is always returning false.
What could be the issue here?
Thanks
I am getting back true for my tests, so it might be what you did before that
might cause this? Can you create something simple that recreates this?
On Thu, Jul 15, 2010 at 1:55 AM, Samuel Doyle samueldoyle@gmail.com wrote:
When sending a PutMappingRequest I used to receive back a true value for
acknowledged.client.admin().indices().putMapping(new
PutMappingRequest(indexName).source(value)).actionGet().acknowledgedAfter my last update from master and build this is always returning false.
What could be the issue here?Thanks
Ok, managed to simulate it, opened an issue:
Put Mapping: When updating existing mappings, the request returns with acknowledged `false` · Issue #262 · elastic/elasticsearch · GitHub (check if
this is your case) and pushed a fix for it.
On Thu, Jul 15, 2010 at 7:11 PM, Shay Banon shay.banon@elasticsearch.comwrote:
I am getting back true for my tests, so it might be what you did before
that might cause this? Can you create something simple that recreates this?On Thu, Jul 15, 2010 at 1:55 AM, Samuel Doyle samueldoyle@gmail.comwrote:
When sending a PutMappingRequest I used to receive back a true value for
acknowledged.client.admin().indices().putMapping(new
PutMappingRequest(indexName).source(value)).actionGet().acknowledgedAfter my last update from master and build this is always returning false.
What could be the issue here?Thanks
Yes, it appears the mappings are fine but the ack was false.
On Thu, Jul 15, 2010 at 10:04 AM, Shay Banon
shay.banon@elasticsearch.comwrote:
Ok, managed to simulate it, opened an issue:
Put Mapping: When updating existing mappings, the request returns with acknowledged `false` · Issue #262 · elastic/elasticsearch · GitHub (check if
this is your case) and pushed a fix for it.On Thu, Jul 15, 2010 at 7:11 PM, Shay Banon shay.banon@elasticsearch.comwrote:
I am getting back true for my tests, so it might be what you did before
that might cause this? Can you create something simple that recreates this?On Thu, Jul 15, 2010 at 1:55 AM, Samuel Doyle samueldoyle@gmail.comwrote:
When sending a PutMappingRequest I used to receive back a true value for
acknowledged.client.admin().indices().putMapping(new
PutMappingRequest(indexName).source(value)).actionGet().acknowledgedAfter my last update from master and build this is always returning
false. What could be the issue here?Thanks
Can you verify that it does not happen with the latest fix?
On Fri, Jul 16, 2010 at 1:49 AM, Samuel Doyle samueldoyle@gmail.com wrote:
Yes, it appears the mappings are fine but the ack was false.
On Thu, Jul 15, 2010 at 10:04 AM, Shay Banon <shay.banon@elasticsearch.com
wrote:
Ok, managed to simulate it, opened an issue:
Put Mapping: When updating existing mappings, the request returns with acknowledged `false` · Issue #262 · elastic/elasticsearch · GitHub (check if
this is your case) and pushed a fix for it.On Thu, Jul 15, 2010 at 7:11 PM, Shay Banon <shay.banon@elasticsearch.com
wrote:
I am getting back true for my tests, so it might be what you did before
that might cause this? Can you create something simple that recreates this?On Thu, Jul 15, 2010 at 1:55 AM, Samuel Doyle samueldoyle@gmail.comwrote:
When sending a PutMappingRequest I used to receive back a true value for
acknowledged.client.admin().indices().putMapping(new
PutMappingRequest(indexName).source(value)).actionGet().acknowledgedAfter my last update from master and build this is always returning
false. What could be the issue here?Thanks
Ok, I'll update and give it a try
On Thu, Jul 15, 2010 at 3:49 PM, Shay Banon shay.banon@elasticsearch.comwrote:
Can you verify that it does not happen with the latest fix?
On Fri, Jul 16, 2010 at 1:49 AM, Samuel Doyle samueldoyle@gmail.comwrote:
Yes, it appears the mappings are fine but the ack was false.
On Thu, Jul 15, 2010 at 10:04 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Ok, managed to simulate it, opened an issue:
Put Mapping: When updating existing mappings, the request returns with acknowledged `false` · Issue #262 · elastic/elasticsearch · GitHub (check if
this is your case) and pushed a fix for it.On Thu, Jul 15, 2010 at 7:11 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:I am getting back true for my tests, so it might be what you did before
that might cause this? Can you create something simple that recreates this?On Thu, Jul 15, 2010 at 1:55 AM, Samuel Doyle samueldoyle@gmail.comwrote:
When sending a PutMappingRequest I used to receive back a true value
for acknowledged.client.admin().indices().putMapping(new
PutMappingRequest(indexName).source(value)).actionGet().acknowledgedAfter my last update from master and build this is always returning
false. What could be the issue here?Thanks
thanks!
On Fri, Jul 16, 2010 at 1:51 AM, Samuel Doyle samueldoyle@gmail.com wrote:
Ok, I'll update and give it a try
On Thu, Jul 15, 2010 at 3:49 PM, Shay Banon shay.banon@elasticsearch.comwrote:
Can you verify that it does not happen with the latest fix?
On Fri, Jul 16, 2010 at 1:49 AM, Samuel Doyle samueldoyle@gmail.comwrote:
Yes, it appears the mappings are fine but the ack was false.
On Thu, Jul 15, 2010 at 10:04 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Ok, managed to simulate it, opened an issue:
Put Mapping: When updating existing mappings, the request returns with acknowledged `false` · Issue #262 · elastic/elasticsearch · GitHub (check
if this is your case) and pushed a fix for it.On Thu, Jul 15, 2010 at 7:11 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:I am getting back true for my tests, so it might be what you did before
that might cause this? Can you create something simple that recreates this?On Thu, Jul 15, 2010 at 1:55 AM, Samuel Doyle samueldoyle@gmail.comwrote:
When sending a PutMappingRequest I used to receive back a true value
for acknowledged.client.admin().indices().putMapping(new
PutMappingRequest(indexName).source(value)).actionGet().acknowledgedAfter my last update from master and build this is always returning
false. What could be the issue here?Thanks
Hi, I still see the problem after update with clean build and deploy. I had
also updated the client jars as well.
On Thu, Jul 15, 2010 at 3:54 PM, Shay Banon shay.banon@elasticsearch.comwrote:
thanks!
On Fri, Jul 16, 2010 at 1:51 AM, Samuel Doyle samueldoyle@gmail.comwrote:
Ok, I'll update and give it a try
On Thu, Jul 15, 2010 at 3:49 PM, Shay Banon <shay.banon@elasticsearch.com
wrote:
Can you verify that it does not happen with the latest fix?
On Fri, Jul 16, 2010 at 1:49 AM, Samuel Doyle samueldoyle@gmail.comwrote:
Yes, it appears the mappings are fine but the ack was false.
On Thu, Jul 15, 2010 at 10:04 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Ok, managed to simulate it, opened an issue:
Put Mapping: When updating existing mappings, the request returns with acknowledged `false` · Issue #262 · elastic/elasticsearch · GitHub (check
if this is your case) and pushed a fix for it.On Thu, Jul 15, 2010 at 7:11 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:I am getting back true for my tests, so it might be what you did
before that might cause this? Can you create something simple that recreates
this?On Thu, Jul 15, 2010 at 1:55 AM, Samuel Doyle samueldoyle@gmail.comwrote:
When sending a PutMappingRequest I used to receive back a true value
for acknowledged.client.admin().indices().putMapping(new
PutMappingRequest(indexName).source(value)).actionGet().acknowledgedAfter my last update from master and build this is always returning
false. What could be the issue here?Thanks
I should mention this is only one node as well.
On Thu, Jul 15, 2010 at 7:39 PM, Samuel Doyle samueldoyle@gmail.com wrote:
Hi, I still see the problem after update with clean build and deploy. I had
also updated the client jars as well.On Thu, Jul 15, 2010 at 3:54 PM, Shay Banon shay.banon@elasticsearch.comwrote:
thanks!
On Fri, Jul 16, 2010 at 1:51 AM, Samuel Doyle samueldoyle@gmail.comwrote:
Ok, I'll update and give it a try
On Thu, Jul 15, 2010 at 3:49 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Can you verify that it does not happen with the latest fix?
On Fri, Jul 16, 2010 at 1:49 AM, Samuel Doyle samueldoyle@gmail.comwrote:
Yes, it appears the mappings are fine but the ack was false.
On Thu, Jul 15, 2010 at 10:04 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Ok, managed to simulate it, opened an issue:
Put Mapping: When updating existing mappings, the request returns with acknowledged `false` · Issue #262 · elastic/elasticsearch · GitHub (check
if this is your case) and pushed a fix for it.On Thu, Jul 15, 2010 at 7:11 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:I am getting back true for my tests, so it might be what you did
before that might cause this? Can you create something simple that recreates
this?On Thu, Jul 15, 2010 at 1:55 AM, Samuel Doyle <samueldoyle@gmail.com
wrote:
When sending a PutMappingRequest I used to receive back a true value
for acknowledged.client.admin().indices().putMapping(new
PutMappingRequest(indexName).source(value)).actionGet().acknowledgedAfter my last update from master and build this is always returning
false. What could be the issue here?Thanks
Can you send a simple recreation?
On Fri, Jul 16, 2010 at 5:39 AM, Samuel Doyle samueldoyle@gmail.com wrote:
I should mention this is only one node as well.
On Thu, Jul 15, 2010 at 7:39 PM, Samuel Doyle samueldoyle@gmail.comwrote:
Hi, I still see the problem after update with clean build and deploy. I
had also updated the client jars as well.On Thu, Jul 15, 2010 at 3:54 PM, Shay Banon <shay.banon@elasticsearch.com
wrote:
thanks!
On Fri, Jul 16, 2010 at 1:51 AM, Samuel Doyle samueldoyle@gmail.comwrote:
Ok, I'll update and give it a try
On Thu, Jul 15, 2010 at 3:49 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Can you verify that it does not happen with the latest fix?
On Fri, Jul 16, 2010 at 1:49 AM, Samuel Doyle samueldoyle@gmail.comwrote:
Yes, it appears the mappings are fine but the ack was false.
On Thu, Jul 15, 2010 at 10:04 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Ok, managed to simulate it, opened an issue:
Put Mapping: When updating existing mappings, the request returns with acknowledged `false` · Issue #262 · elastic/elasticsearch · GitHub(check if this is your case) and pushed a fix for it.On Thu, Jul 15, 2010 at 7:11 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:I am getting back true for my tests, so it might be what you did
before that might cause this? Can you create something simple that recreates
this?On Thu, Jul 15, 2010 at 1:55 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:When sending a PutMappingRequest I used to receive back a true
value for acknowledged.client.admin().indices().putMapping(new
PutMappingRequest(indexName).source(value)).actionGet().acknowledgedAfter my last update from master and build this is always returning
false. What could be the issue here?Thanks
Here is the mapping I'm using that always causes the problem
{"sale":{"properties":{"salescode":{"type":"string","boost":1},"sdate":{"type":"date","boost":1,"format":"YYYY-MM-dd
HH:mm:ss.S"},"orgid":{"type":"long","boost":1},"safname":{"type":"string","boost":1},"salname":{"type":"string","index":"not_analyzed","boost":1},"saemail":{"type":"string","boost":1},"saaddr1":{"type":"string","boost":1},"saaddr2":{"type":"string","boost":1},"sacity":{"type":"string","boost":1},"sastateprov":{"type":"string","boost":1},"sapostalcode":{"type":"string","boost":1},"sacountry":{"type":"string","boost":1},"saphone":{"type":"string","boost":1},"bafname":{"type":"string","boost":1},"balname":{"type":"string","boost":1},"baemail":{"type":"string","boost":1},"baaddr1":{"type":"string","boost":1},"baaddr2":{"type":"string","boost":1},"bacity":{"type":"string","boost":1},"bastateprov":{"type":"string","boost":1},"bapostalcode":{"type":"string","boost":1},"bacountry":{"type":"string","boost":1},"baphone":{"type":"string","boost":1},"creditcard":{"type":"string","boost":1},"trxamount":{"type":"double","boost":1},"trxdate":{"type":"date","boost":1,"format":"YYYY-MM-dd
HH:mm:ss.S"},"pgownertype":{"type":"integer","boost":1},"pgownerid":{"type":"integer","boost":1}}}}
On Fri, Jul 16, 2010 at 4:16 AM, Shay Banon shay.banon@elasticsearch.comwrote:
Can you send a simple recreation?
On Fri, Jul 16, 2010 at 5:39 AM, Samuel Doyle samueldoyle@gmail.comwrote:
I should mention this is only one node as well.
On Thu, Jul 15, 2010 at 7:39 PM, Samuel Doyle samueldoyle@gmail.comwrote:
Hi, I still see the problem after update with clean build and deploy. I
had also updated the client jars as well.On Thu, Jul 15, 2010 at 3:54 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:thanks!
On Fri, Jul 16, 2010 at 1:51 AM, Samuel Doyle samueldoyle@gmail.comwrote:
Ok, I'll update and give it a try
On Thu, Jul 15, 2010 at 3:49 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Can you verify that it does not happen with the latest fix?
On Fri, Jul 16, 2010 at 1:49 AM, Samuel Doyle samueldoyle@gmail.comwrote:
Yes, it appears the mappings are fine but the ack was false.
On Thu, Jul 15, 2010 at 10:04 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Ok, managed to simulate it, opened an issue:
Put Mapping: When updating existing mappings, the request returns with acknowledged `false` · Issue #262 · elastic/elasticsearch · GitHub(check if this is your case) and pushed a fix for it.On Thu, Jul 15, 2010 at 7:11 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:I am getting back true for my tests, so it might be what you did
before that might cause this? Can you create something simple that recreates
this?On Thu, Jul 15, 2010 at 1:55 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:When sending a PutMappingRequest I used to receive back a true
value for acknowledged.client.admin().indices().putMapping(new
PutMappingRequest(indexName).source(value)).actionGet().acknowledgedAfter my last update from master and build this is always
returning false. What could be the issue here?Thanks
And you say that with a fresh elasticsearch instance, when you try to put
this mapping, you get the ack=false, or are there certain steps that needs
to be taken in order to reproduce it?
-shay.banon
On Sun, Jul 18, 2010 at 5:58 AM, Samuel Doyle samueldoyle@gmail.com wrote:
Here is the mapping I'm using that always causes the problem
{"sale":{"properties":{"salescode":{"type":"string","boost":1},"sdate":{"type":"date","boost":1,"format":"YYYY-MM-dd
HH:mm:ss.S"},"orgid":{"type":"long","boost":1},"safname":{"type":"string","boost":1},"salname":{"type":"string","index":"not_analyzed","boost":1},"saemail":{"type":"string","boost":1},"saaddr1":{"type":"string","boost":1},"saaddr2":{"type":"string","boost":1},"sacity":{"type":"string","boost":1},"sastateprov":{"type":"string","boost":1},"sapostalcode":{"type":"string","boost":1},"sacountry":{"type":"string","boost":1},"saphone":{"type":"string","boost":1},"bafname":{"type":"string","boost":1},"balname":{"type":"string","boost":1},"baemail":{"type":"string","boost":1},"baaddr1":{"type":"string","boost":1},"baaddr2":{"type":"string","boost":1},"bacity":{"type":"string","boost":1},"bastateprov":{"type":"string","boost":1},"bapostalcode":{"type":"string","boost":1},"bacountry":{"type":"string","boost":1},"baphone":{"type":"string","boost":1},"creditcard":{"type":"string","boost":1},"trxamount":{"type":"double","boost":1},"trxdate":{"type":"date","boost":1,"format":"YYYY-MM-dd
HH:mm:ss.S"},"pgownertype":{"type":"integer","boost":1},"pgownerid":{"type":"integer","boost":1}}}}On Fri, Jul 16, 2010 at 4:16 AM, Shay Banon shay.banon@elasticsearch.comwrote:
Can you send a simple recreation?
On Fri, Jul 16, 2010 at 5:39 AM, Samuel Doyle samueldoyle@gmail.comwrote:
I should mention this is only one node as well.
On Thu, Jul 15, 2010 at 7:39 PM, Samuel Doyle samueldoyle@gmail.comwrote:
Hi, I still see the problem after update with clean build and deploy. I
had also updated the client jars as well.On Thu, Jul 15, 2010 at 3:54 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:thanks!
On Fri, Jul 16, 2010 at 1:51 AM, Samuel Doyle samueldoyle@gmail.comwrote:
Ok, I'll update and give it a try
On Thu, Jul 15, 2010 at 3:49 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Can you verify that it does not happen with the latest fix?
On Fri, Jul 16, 2010 at 1:49 AM, Samuel Doyle <samueldoyle@gmail.com
wrote:
Yes, it appears the mappings are fine but the ack was false.
On Thu, Jul 15, 2010 at 10:04 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Ok, managed to simulate it, opened an issue:
Put Mapping: When updating existing mappings, the request returns with acknowledged `false` · Issue #262 · elastic/elasticsearch · GitHub(check if this is your case) and pushed a fix for it.On Thu, Jul 15, 2010 at 7:11 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:I am getting back true for my tests, so it might be what you did
before that might cause this? Can you create something simple that recreates
this?On Thu, Jul 15, 2010 at 1:55 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:When sending a PutMappingRequest I used to receive back a true
value for acknowledged.client.admin().indices().putMapping(new
PutMappingRequest(indexName).source(value)).actionGet().acknowledgedAfter my last update from master and build this is always
returning false. What could be the issue here?Thanks
This is what I do for the batch indexing:
1.) Delete the index if it exists
2.) Create the index
3.) Check and wait till the index is available
4.) Send the PutMappingRequest which results in the NACK
On Sun, Jul 18, 2010 at 1:35 AM, Shay Banon shay.banon@elasticsearch.comwrote:
And you say that with a fresh elasticsearch instance, when you try to put
this mapping, you get the ack=false, or are there certain steps that needs
to be taken in order to reproduce it?-shay.banon
On Sun, Jul 18, 2010 at 5:58 AM, Samuel Doyle samueldoyle@gmail.comwrote:
Here is the mapping I'm using that always causes the problem
{"sale":{"properties":{"salescode":{"type":"string","boost":1},"sdate":{"type":"date","boost":1,"format":"YYYY-MM-dd
HH:mm:ss.S"},"orgid":{"type":"long","boost":1},"safname":{"type":"string","boost":1},"salname":{"type":"string","index":"not_analyzed","boost":1},"saemail":{"type":"string","boost":1},"saaddr1":{"type":"string","boost":1},"saaddr2":{"type":"string","boost":1},"sacity":{"type":"string","boost":1},"sastateprov":{"type":"string","boost":1},"sapostalcode":{"type":"string","boost":1},"sacountry":{"type":"string","boost":1},"saphone":{"type":"string","boost":1},"bafname":{"type":"string","boost":1},"balname":{"type":"string","boost":1},"baemail":{"type":"string","boost":1},"baaddr1":{"type":"string","boost":1},"baaddr2":{"type":"string","boost":1},"bacity":{"type":"string","boost":1},"bastateprov":{"type":"string","boost":1},"bapostalcode":{"type":"string","boost":1},"bacountry":{"type":"string","boost":1},"baphone":{"type":"string","boost":1},"creditcard":{"type":"string","boost":1},"trxamount":{"type":"double","boost":1},"trxdate":{"type":"date","boost":1,"format":"YYYY-MM-dd
HH:mm:ss.S"},"pgownertype":{"type":"integer","boost":1},"pgownerid":{"type":"integer","boost":1}}}}On Fri, Jul 16, 2010 at 4:16 AM, Shay Banon <shay.banon@elasticsearch.com
wrote:
Can you send a simple recreation?
On Fri, Jul 16, 2010 at 5:39 AM, Samuel Doyle samueldoyle@gmail.comwrote:
I should mention this is only one node as well.
On Thu, Jul 15, 2010 at 7:39 PM, Samuel Doyle samueldoyle@gmail.comwrote:
Hi, I still see the problem after update with clean build and deploy. I
had also updated the client jars as well.On Thu, Jul 15, 2010 at 3:54 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:thanks!
On Fri, Jul 16, 2010 at 1:51 AM, Samuel Doyle samueldoyle@gmail.comwrote:
Ok, I'll update and give it a try
On Thu, Jul 15, 2010 at 3:49 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Can you verify that it does not happen with the latest fix?
On Fri, Jul 16, 2010 at 1:49 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:Yes, it appears the mappings are fine but the ack was false.
On Thu, Jul 15, 2010 at 10:04 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Ok, managed to simulate it, opened an issue:
Put Mapping: When updating existing mappings, the request returns with acknowledged `false` · Issue #262 · elastic/elasticsearch · GitHub(check if this is your case) and pushed a fix for it.On Thu, Jul 15, 2010 at 7:11 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:I am getting back true for my tests, so it might be what you did
before that might cause this? Can you create something simple that recreates
this?On Thu, Jul 15, 2010 at 1:55 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:When sending a PutMappingRequest I used to receive back a true
value for acknowledged.client.admin().indices().putMapping(new
PutMappingRequest(indexName).source(value)).actionGet().acknowledgedAfter my last update from master and build this is always
returning false. What could be the issue here?Thanks
Since you seem to refuse to send some sort of recreation, I wrote one based
on your steps and it works for me. Please don't respond to this email unless
there is some way that I can recreate this, I can't second guess all the
steps you do. Here is what I ran: gist:481733 · GitHub
-shay.banon
On Sun, Jul 18, 2010 at 6:49 PM, Samuel Doyle samueldoyle@gmail.com wrote:
This is what I do for the batch indexing:
1.) Delete the index if it exists
2.) Create the index
3.) Check and wait till the index is available
4.) Send the PutMappingRequest which results in the NACKOn Sun, Jul 18, 2010 at 1:35 AM, Shay Banon shay.banon@elasticsearch.comwrote:
And you say that with a fresh elasticsearch instance, when you try to put
this mapping, you get the ack=false, or are there certain steps that needs
to be taken in order to reproduce it?-shay.banon
On Sun, Jul 18, 2010 at 5:58 AM, Samuel Doyle samueldoyle@gmail.comwrote:
Here is the mapping I'm using that always causes the problem
{"sale":{"properties":{"salescode":{"type":"string","boost":1},"sdate":{"type":"date","boost":1,"format":"YYYY-MM-dd
HH:mm:ss.S"},"orgid":{"type":"long","boost":1},"safname":{"type":"string","boost":1},"salname":{"type":"string","index":"not_analyzed","boost":1},"saemail":{"type":"string","boost":1},"saaddr1":{"type":"string","boost":1},"saaddr2":{"type":"string","boost":1},"sacity":{"type":"string","boost":1},"sastateprov":{"type":"string","boost":1},"sapostalcode":{"type":"string","boost":1},"sacountry":{"type":"string","boost":1},"saphone":{"type":"string","boost":1},"bafname":{"type":"string","boost":1},"balname":{"type":"string","boost":1},"baemail":{"type":"string","boost":1},"baaddr1":{"type":"string","boost":1},"baaddr2":{"type":"string","boost":1},"bacity":{"type":"string","boost":1},"bastateprov":{"type":"string","boost":1},"bapostalcode":{"type":"string","boost":1},"bacountry":{"type":"string","boost":1},"baphone":{"type":"string","boost":1},"creditcard":{"type":"string","boost":1},"trxamount":{"type":"double","boost":1},"trxdate":{"type":"date","boost":1,"format":"YYYY-MM-dd
HH:mm:ss.S"},"pgownertype":{"type":"integer","boost":1},"pgownerid":{"type":"integer","boost":1}}}}On Fri, Jul 16, 2010 at 4:16 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Can you send a simple recreation?
On Fri, Jul 16, 2010 at 5:39 AM, Samuel Doyle samueldoyle@gmail.comwrote:
I should mention this is only one node as well.
On Thu, Jul 15, 2010 at 7:39 PM, Samuel Doyle samueldoyle@gmail.comwrote:
Hi, I still see the problem after update with clean build and deploy.
I had also updated the client jars as well.On Thu, Jul 15, 2010 at 3:54 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:thanks!
On Fri, Jul 16, 2010 at 1:51 AM, Samuel Doyle <samueldoyle@gmail.com
wrote:
Ok, I'll update and give it a try
On Thu, Jul 15, 2010 at 3:49 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Can you verify that it does not happen with the latest fix?
On Fri, Jul 16, 2010 at 1:49 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:Yes, it appears the mappings are fine but the ack was false.
On Thu, Jul 15, 2010 at 10:04 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Ok, managed to simulate it, opened an issue:
Put Mapping: When updating existing mappings, the request returns with acknowledged `false` · Issue #262 · elastic/elasticsearch · GitHub(check if this is your case) and pushed a fix for it.On Thu, Jul 15, 2010 at 7:11 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:I am getting back true for my tests, so it might be what you did
before that might cause this? Can you create something simple that recreates
this?On Thu, Jul 15, 2010 at 1:55 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:When sending a PutMappingRequest I used to receive back a true
value for acknowledged.client.admin().indices().putMapping(new
PutMappingRequest(indexName).source(value)).actionGet().acknowledgedAfter my last update from master and build this is always
returning false. What could be the issue here?Thanks
I never refused to provide a way to recreate and I'm not sure why you are
saying that for, I provided the steps which I followed to recreate the
problem as well as the mappings
I have an integrationtest which always duplicates this problem but contains
information that would be deemed private to the project I am working on.
I have some pretty tight deadlines but I will make an attempt to strip out
those pieces and provide you with a test when I can. If you wish for me not
to mention issues that are encountered with your project I can refrain from
doing so in the future and leave it for others to discover.
On Mon, Jul 19, 2010 at 10:55 AM, Shay Banon
shay.banon@elasticsearch.comwrote:
Since you seem to refuse to send some sort of recreation, I wrote one based
on your steps and it works for me. Please don't respond to this email unless
there is some way that I can recreate this, I can't second guess all the
steps you do. Here is what I ran: gist:481733 · GitHub-shay.banon
On Sun, Jul 18, 2010 at 6:49 PM, Samuel Doyle samueldoyle@gmail.comwrote:
This is what I do for the batch indexing:
1.) Delete the index if it exists
2.) Create the index
3.) Check and wait till the index is available
4.) Send the PutMappingRequest which results in the NACKOn Sun, Jul 18, 2010 at 1:35 AM, Shay Banon <shay.banon@elasticsearch.com
wrote:
And you say that with a fresh elasticsearch instance, when you try to put
this mapping, you get the ack=false, or are there certain steps that needs
to be taken in order to reproduce it?-shay.banon
On Sun, Jul 18, 2010 at 5:58 AM, Samuel Doyle samueldoyle@gmail.comwrote:
Here is the mapping I'm using that always causes the problem
{"sale":{"properties":{"salescode":{"type":"string","boost":1},"sdate":{"type":"date","boost":1,"format":"YYYY-MM-dd
HH:mm:ss.S"},"orgid":{"type":"long","boost":1},"safname":{"type":"string","boost":1},"salname":{"type":"string","index":"not_analyzed","boost":1},"saemail":{"type":"string","boost":1},"saaddr1":{"type":"string","boost":1},"saaddr2":{"type":"string","boost":1},"sacity":{"type":"string","boost":1},"sastateprov":{"type":"string","boost":1},"sapostalcode":{"type":"string","boost":1},"sacountry":{"type":"string","boost":1},"saphone":{"type":"string","boost":1},"bafname":{"type":"string","boost":1},"balname":{"type":"string","boost":1},"baemail":{"type":"string","boost":1},"baaddr1":{"type":"string","boost":1},"baaddr2":{"type":"string","boost":1},"bacity":{"type":"string","boost":1},"bastateprov":{"type":"string","boost":1},"bapostalcode":{"type":"string","boost":1},"bacountry":{"type":"string","boost":1},"baphone":{"type":"string","boost":1},"creditcard":{"type":"string","boost":1},"trxamount":{"type":"double","boost":1},"trxdate":{"type":"date","boost":1,"format":"YYYY-MM-dd
HH:mm:ss.S"},"pgownertype":{"type":"integer","boost":1},"pgownerid":{"type":"integer","boost":1}}}}On Fri, Jul 16, 2010 at 4:16 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Can you send a simple recreation?
On Fri, Jul 16, 2010 at 5:39 AM, Samuel Doyle samueldoyle@gmail.comwrote:
I should mention this is only one node as well.
On Thu, Jul 15, 2010 at 7:39 PM, Samuel Doyle samueldoyle@gmail.comwrote:
Hi, I still see the problem after update with clean build and deploy.
I had also updated the client jars as well.On Thu, Jul 15, 2010 at 3:54 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:thanks!
On Fri, Jul 16, 2010 at 1:51 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:Ok, I'll update and give it a try
On Thu, Jul 15, 2010 at 3:49 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Can you verify that it does not happen with the latest fix?
On Fri, Jul 16, 2010 at 1:49 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:Yes, it appears the mappings are fine but the ack was false.
On Thu, Jul 15, 2010 at 10:04 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Ok, managed to simulate it, opened an issue:
Put Mapping: When updating existing mappings, the request returns with acknowledged `false` · Issue #262 · elastic/elasticsearch · GitHub(check if this is your case) and pushed a fix for it.On Thu, Jul 15, 2010 at 7:11 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:I am getting back true for my tests, so it might be what you
did before that might cause this? Can you create something simple that
recreates this?On Thu, Jul 15, 2010 at 1:55 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:When sending a PutMappingRequest I used to receive back a true
value for acknowledged.client.admin().indices().putMapping(new
PutMappingRequest(indexName).source(value)).actionGet().acknowledgedAfter my last update from master and build this is always
returning false. What could be the issue here?Thanks
Here is a quote from 5 emails ago: "Can you send a simple recreation?".
Really, its up to you, if there is really a problem and you want it to be
fixed, then I need a recreation. Sending me more steps, assumptions,
mappings, or something similar just make me try and recreate it
un-successfully. The problem is with me, its in my nature. Once I get
another bit of information, I spend the time it takes to try and understand
and recreate it, and then get frustrated with myself for doing it and not
just pushing back and saying: just give me that recreation, my time is
precious too 
-shay.banon
On Mon, Jul 19, 2010 at 9:12 PM, Samuel Doyle samueldoyle@gmail.com wrote:
I never refused to provide a way to recreate and I'm not sure why you are
saying that for, I provided the steps which I followed to recreate the
problem as well as the mappings
I have an integrationtest which always duplicates this problem but contains
information that would be deemed private to the project I am working on.
I have some pretty tight deadlines but I will make an attempt to strip out
those pieces and provide you with a test when I can. If you wish for me not
to mention issues that are encountered with your project I can refrain from
doing so in the future and leave it for others to discover.On Mon, Jul 19, 2010 at 10:55 AM, Shay Banon <shay.banon@elasticsearch.com
wrote:
Since you seem to refuse to send some sort of recreation, I wrote one
based on your steps and it works for me. Please don't respond to this email
unless there is some way that I can recreate this, I can't second guess all
the steps you do. Here is what I ran: gist:481733 · GitHub-shay.banon
On Sun, Jul 18, 2010 at 6:49 PM, Samuel Doyle samueldoyle@gmail.comwrote:
This is what I do for the batch indexing:
1.) Delete the index if it exists
2.) Create the index
3.) Check and wait till the index is available
4.) Send the PutMappingRequest which results in the NACKOn Sun, Jul 18, 2010 at 1:35 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:And you say that with a fresh elasticsearch instance, when you try to
put this mapping, you get the ack=false, or are there certain steps that
needs to be taken in order to reproduce it?-shay.banon
On Sun, Jul 18, 2010 at 5:58 AM, Samuel Doyle samueldoyle@gmail.comwrote:
Here is the mapping I'm using that always causes the problem
{"sale":{"properties":{"salescode":{"type":"string","boost":1},"sdate":{"type":"date","boost":1,"format":"YYYY-MM-dd
HH:mm:ss.S"},"orgid":{"type":"long","boost":1},"safname":{"type":"string","boost":1},"salname":{"type":"string","index":"not_analyzed","boost":1},"saemail":{"type":"string","boost":1},"saaddr1":{"type":"string","boost":1},"saaddr2":{"type":"string","boost":1},"sacity":{"type":"string","boost":1},"sastateprov":{"type":"string","boost":1},"sapostalcode":{"type":"string","boost":1},"sacountry":{"type":"string","boost":1},"saphone":{"type":"string","boost":1},"bafname":{"type":"string","boost":1},"balname":{"type":"string","boost":1},"baemail":{"type":"string","boost":1},"baaddr1":{"type":"string","boost":1},"baaddr2":{"type":"string","boost":1},"bacity":{"type":"string","boost":1},"bastateprov":{"type":"string","boost":1},"bapostalcode":{"type":"string","boost":1},"bacountry":{"type":"string","boost":1},"baphone":{"type":"string","boost":1},"creditcard":{"type":"string","boost":1},"trxamount":{"type":"double","boost":1},"trxdate":{"type":"date","boost":1,"format":"YYYY-MM-dd
HH:mm:ss.S"},"pgownertype":{"type":"integer","boost":1},"pgownerid":{"type":"integer","boost":1}}}}On Fri, Jul 16, 2010 at 4:16 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Can you send a simple recreation?
On Fri, Jul 16, 2010 at 5:39 AM, Samuel Doyle samueldoyle@gmail.comwrote:
I should mention this is only one node as well.
On Thu, Jul 15, 2010 at 7:39 PM, Samuel Doyle <samueldoyle@gmail.com
wrote:
Hi, I still see the problem after update with clean build and
deploy. I had also updated the client jars as well.On Thu, Jul 15, 2010 at 3:54 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:thanks!
On Fri, Jul 16, 2010 at 1:51 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:Ok, I'll update and give it a try
On Thu, Jul 15, 2010 at 3:49 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Can you verify that it does not happen with the latest fix?
On Fri, Jul 16, 2010 at 1:49 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:Yes, it appears the mappings are fine but the ack was false.
On Thu, Jul 15, 2010 at 10:04 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Ok, managed to simulate it, opened an issue:
Put Mapping: When updating existing mappings, the request returns with acknowledged `false` · Issue #262 · elastic/elasticsearch · GitHub(check if this is your case) and pushed a fix for it.On Thu, Jul 15, 2010 at 7:11 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:I am getting back true for my tests, so it might be what you
did before that might cause this? Can you create something simple that
recreates this?On Thu, Jul 15, 2010 at 1:55 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:When sending a PutMappingRequest I used to receive back a
true value for acknowledged.client.admin().indices().putMapping(new
PutMappingRequest(indexName).source(value)).actionGet().acknowledgedAfter my last update from master and build this is always
returning false. What could be the issue here?Thanks
My apologies than
It is very obvious you are working hard to produce a great application,
frankly I don't know where you find the time for anything between pushing
out all updates and addressing the steady stream of questions and
investigating issues seemingly around the clock.
I will make more of an effort to provide you with more information for
reproducing any issues in the future
Thanks once again for the great work you are doing for the community!
On Mon, Jul 19, 2010 at 11:23 AM, Shay Banon
shay.banon@elasticsearch.comwrote:
Here is a quote from 5 emails ago: "Can you send a simple recreation?".
Really, its up to you, if there is really a problem and you want it to be
fixed, then I need a recreation. Sending me more steps, assumptions,
mappings, or something similar just make me try and recreate it
un-successfully. The problem is with me, its in my nature. Once I get
another bit of information, I spend the time it takes to try and understand
and recreate it, and then get frustrated with myself for doing it and not
just pushing back and saying: just give me that recreation, my time is
precious too-shay.banon
On Mon, Jul 19, 2010 at 9:12 PM, Samuel Doyle samueldoyle@gmail.comwrote:
I never refused to provide a way to recreate and I'm not sure why you are
saying that for, I provided the steps which I followed to recreate the
problem as well as the mappings
I have an integrationtest which always duplicates this problem but
contains information that would be deemed private to the project I am
working on.
I have some pretty tight deadlines but I will make an attempt to strip out
those pieces and provide you with a test when I can. If you wish for me not
to mention issues that are encountered with your project I can refrain from
doing so in the future and leave it for others to discover.On Mon, Jul 19, 2010 at 10:55 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Since you seem to refuse to send some sort of recreation, I wrote one
based on your steps and it works for me. Please don't respond to this email
unless there is some way that I can recreate this, I can't second guess all
the steps you do. Here is what I ran: gist:481733 · GitHub-shay.banon
On Sun, Jul 18, 2010 at 6:49 PM, Samuel Doyle samueldoyle@gmail.comwrote:
This is what I do for the batch indexing:
1.) Delete the index if it exists
2.) Create the index
3.) Check and wait till the index is available
4.) Send the PutMappingRequest which results in the NACKOn Sun, Jul 18, 2010 at 1:35 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:And you say that with a fresh elasticsearch instance, when you try to
put this mapping, you get the ack=false, or are there certain steps that
needs to be taken in order to reproduce it?-shay.banon
On Sun, Jul 18, 2010 at 5:58 AM, Samuel Doyle samueldoyle@gmail.comwrote:
Here is the mapping I'm using that always causes the problem
{"sale":{"properties":{"salescode":{"type":"string","boost":1},"sdate":{"type":"date","boost":1,"format":"YYYY-MM-dd
HH:mm:ss.S"},"orgid":{"type":"long","boost":1},"safname":{"type":"string","boost":1},"salname":{"type":"string","index":"not_analyzed","boost":1},"saemail":{"type":"string","boost":1},"saaddr1":{"type":"string","boost":1},"saaddr2":{"type":"string","boost":1},"sacity":{"type":"string","boost":1},"sastateprov":{"type":"string","boost":1},"sapostalcode":{"type":"string","boost":1},"sacountry":{"type":"string","boost":1},"saphone":{"type":"string","boost":1},"bafname":{"type":"string","boost":1},"balname":{"type":"string","boost":1},"baemail":{"type":"string","boost":1},"baaddr1":{"type":"string","boost":1},"baaddr2":{"type":"string","boost":1},"bacity":{"type":"string","boost":1},"bastateprov":{"type":"string","boost":1},"bapostalcode":{"type":"string","boost":1},"bacountry":{"type":"string","boost":1},"baphone":{"type":"string","boost":1},"creditcard":{"type":"string","boost":1},"trxamount":{"type":"double","boost":1},"trxdate":{"type":"date","boost":1,"format":"YYYY-MM-dd
HH:mm:ss.S"},"pgownertype":{"type":"integer","boost":1},"pgownerid":{"type":"integer","boost":1}}}}On Fri, Jul 16, 2010 at 4:16 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Can you send a simple recreation?
On Fri, Jul 16, 2010 at 5:39 AM, Samuel Doyle <samueldoyle@gmail.com
wrote:
I should mention this is only one node as well.
On Thu, Jul 15, 2010 at 7:39 PM, Samuel Doyle <
samueldoyle@gmail.com> wrote:Hi, I still see the problem after update with clean build and
deploy. I had also updated the client jars as well.On Thu, Jul 15, 2010 at 3:54 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:thanks!
On Fri, Jul 16, 2010 at 1:51 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:Ok, I'll update and give it a try
On Thu, Jul 15, 2010 at 3:49 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Can you verify that it does not happen with the latest fix?
On Fri, Jul 16, 2010 at 1:49 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:Yes, it appears the mappings are fine but the ack was false.
On Thu, Jul 15, 2010 at 10:04 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Ok, managed to simulate it, opened an issue:
Put Mapping: When updating existing mappings, the request returns with acknowledged `false` · Issue #262 · elastic/elasticsearch · GitHub(check if this is your case) and pushed a fix for it.On Thu, Jul 15, 2010 at 7:11 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:I am getting back true for my tests, so it might be what you
did before that might cause this? Can you create something simple that
recreates this?On Thu, Jul 15, 2010 at 1:55 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:When sending a PutMappingRequest I used to receive back a
true value for acknowledged.client.admin().indices().putMapping(new
PutMappingRequest(indexName).source(value)).actionGet().acknowledgedAfter my last update from master and build this is always
returning false. What could be the issue here?Thanks
Thanks!
On Mon, Jul 19, 2010 at 9:32 PM, Samuel Doyle samueldoyle@gmail.com wrote:
My apologies than
It is very obvious you are working hard to produce a great application,
frankly I don't know where you find the time for anything between pushing
out all updates and addressing the steady stream of questions and
investigating issues seemingly around the clock.
I will make more of an effort to provide you with more information for
reproducing any issues in the futureThanks once again for the great work you are doing for the community!
On Mon, Jul 19, 2010 at 11:23 AM, Shay Banon <shay.banon@elasticsearch.com
wrote:
Here is a quote from 5 emails ago: "Can you send a simple recreation?".
Really, its up to you, if there is really a problem and you want it to be
fixed, then I need a recreation. Sending me more steps, assumptions,
mappings, or something similar just make me try and recreate it
un-successfully. The problem is with me, its in my nature. Once I get
another bit of information, I spend the time it takes to try and understand
and recreate it, and then get frustrated with myself for doing it and not
just pushing back and saying: just give me that recreation, my time is
precious too-shay.banon
On Mon, Jul 19, 2010 at 9:12 PM, Samuel Doyle samueldoyle@gmail.comwrote:
I never refused to provide a way to recreate and I'm not sure why you are
saying that for, I provided the steps which I followed to recreate the
problem as well as the mappings
I have an integrationtest which always duplicates this problem but
contains information that would be deemed private to the project I am
working on.
I have some pretty tight deadlines but I will make an attempt to strip
out those pieces and provide you with a test when I can. If you wish for me
not to mention issues that are encountered with your project I can refrain
from doing so in the future and leave it for others to discover.On Mon, Jul 19, 2010 at 10:55 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Since you seem to refuse to send some sort of recreation, I wrote one
based on your steps and it works for me. Please don't respond to this email
unless there is some way that I can recreate this, I can't second guess all
the steps you do. Here is what I ran: gist:481733 · GitHub-shay.banon
On Sun, Jul 18, 2010 at 6:49 PM, Samuel Doyle samueldoyle@gmail.comwrote:
This is what I do for the batch indexing:
1.) Delete the index if it exists
2.) Create the index
3.) Check and wait till the index is available
4.) Send the PutMappingRequest which results in the NACKOn Sun, Jul 18, 2010 at 1:35 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:And you say that with a fresh elasticsearch instance, when you try to
put this mapping, you get the ack=false, or are there certain steps that
needs to be taken in order to reproduce it?-shay.banon
On Sun, Jul 18, 2010 at 5:58 AM, Samuel Doyle samueldoyle@gmail.comwrote:
Here is the mapping I'm using that always causes the problem
{"sale":{"properties":{"salescode":{"type":"string","boost":1},"sdate":{"type":"date","boost":1,"format":"YYYY-MM-dd
HH:mm:ss.S"},"orgid":{"type":"long","boost":1},"safname":{"type":"string","boost":1},"salname":{"type":"string","index":"not_analyzed","boost":1},"saemail":{"type":"string","boost":1},"saaddr1":{"type":"string","boost":1},"saaddr2":{"type":"string","boost":1},"sacity":{"type":"string","boost":1},"sastateprov":{"type":"string","boost":1},"sapostalcode":{"type":"string","boost":1},"sacountry":{"type":"string","boost":1},"saphone":{"type":"string","boost":1},"bafname":{"type":"string","boost":1},"balname":{"type":"string","boost":1},"baemail":{"type":"string","boost":1},"baaddr1":{"type":"string","boost":1},"baaddr2":{"type":"string","boost":1},"bacity":{"type":"string","boost":1},"bastateprov":{"type":"string","boost":1},"bapostalcode":{"type":"string","boost":1},"bacountry":{"type":"string","boost":1},"baphone":{"type":"string","boost":1},"creditcard":{"type":"string","boost":1},"trxamount":{"type":"double","boost":1},"trxdate":{"type":"date","boost":1,"format":"YYYY-MM-dd
HH:mm:ss.S"},"pgownertype":{"type":"integer","boost":1},"pgownerid":{"type":"integer","boost":1}}}}On Fri, Jul 16, 2010 at 4:16 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Can you send a simple recreation?
On Fri, Jul 16, 2010 at 5:39 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:I should mention this is only one node as well.
On Thu, Jul 15, 2010 at 7:39 PM, Samuel Doyle <
samueldoyle@gmail.com> wrote:Hi, I still see the problem after update with clean build and
deploy. I had also updated the client jars as well.On Thu, Jul 15, 2010 at 3:54 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:thanks!
On Fri, Jul 16, 2010 at 1:51 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:Ok, I'll update and give it a try
On Thu, Jul 15, 2010 at 3:49 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Can you verify that it does not happen with the latest fix?
On Fri, Jul 16, 2010 at 1:49 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:Yes, it appears the mappings are fine but the ack was false.
On Thu, Jul 15, 2010 at 10:04 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:Ok, managed to simulate it, opened an issue:
Put Mapping: When updating existing mappings, the request returns with acknowledged `false` · Issue #262 · elastic/elasticsearch · GitHub(check if this is your case) and pushed a fix for it.On Thu, Jul 15, 2010 at 7:11 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:I am getting back true for my tests, so it might be what you
did before that might cause this? Can you create something simple that
recreates this?On Thu, Jul 15, 2010 at 1:55 AM, Samuel Doyle <
samueldoyle@gmail.com> wrote:When sending a PutMappingRequest I used to receive back a
true value for acknowledged.client.admin().indices().putMapping(new
PutMappingRequest(indexName).source(value)).actionGet().acknowledgedAfter my last update from master and build this is always
returning false. What could be the issue here?Thanks
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.