You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
stringdata="{ \"source\":\"my_source\", \"country\":\"my_country\", \"company\":\"my_company\" }";_client.Index(data, s =>s.Index("my_index").Type("my_type").Id(Guid.NewGuid().ToString()));}
Currently (with the master branch 2.0), this does not work for me.
When running, I could notice that the constructor Elasticsearch.Net.PostData(T item) is called instead of (in my humble opinion) Elasticsearch.Net.PostData(string item). So the execution try to serialize a string...
I found a unit test only related with a document as object but not with byte[], string, IEnumerable<string> item, IEnumerable<object> item to confirm this.
NB : Without s.id() the request sent is not POST (and is therefore considered as false by ElasticSearch) but perhaps this is result of the unexpected execution described above.
The text was updated successfully, but these errors were encountered:
Oh! Yes, I tried Id in alpha1 and I haven't try again in alpha2. My mistake, thank you.
Ok, I just test your advice, they seem to work. I'm just sorry for not having found documentation related to this. But it's really good job, thank you guys for all.
Hello,
I try to push some json data as in this exemple :
Currently (with the master branch 2.0), this does not work for me.
When running, I could notice that the constructor
Elasticsearch.Net.PostData(T item)
is called instead of (in my humble opinion)Elasticsearch.Net.PostData(string item)
. So the execution try to serialize astring
...I found a unit test only related with a document as
object
but not withbyte[]
,string
,IEnumerable<string> item
,IEnumerable<object> item
to confirm this.NB : Without
s.id()
the request sent is notPOST
(and is therefore considered as false by ElasticSearch) but perhaps this is result of the unexpected execution described above.The text was updated successfully, but these errors were encountered: