{"action":"opened","issue":{"url":"https://api.github.com/repos/elastic/elasticsearch-net/issues/1528","labels_url":"https://api.github.com/repos/elastic/elasticsearch-net/issues/1528/labels{/name}","comments_url":"https://api.github.com/repos/elastic/elasticsearch-net/issues/1528/comments","events_url":"https://api.github.com/repos/elastic/elasticsearch-net/issues/1528/events","html_url":"https://github.com/elastic/elasticsearch-net/issues/1528","id":102592452,"number":1528,"title":"Having some troubles... and documentation seems inaccurate to current version (v1.7.0)","user":{"login":"thunderstumpges","id":1066202,"avatar_url":"https://avatars.githubusercontent.com/u/1066202?v=3","gravatar_id":"","url":"https://api.github.com/users/thunderstumpges","html_url":"https://github.com/thunderstumpges","followers_url":"https://api.github.com/users/thunderstumpges/followers","following_url":"https://api.github.com/users/thunderstumpges/following{/other_user}","gists_url":"https://api.github.com/users/thunderstumpges/gists{/gist_id}","starred_url":"https://api.github.com/users/thunderstumpges/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thunderstumpges/subscriptions","organizations_url":"https://api.github.com/users/thunderstumpges/orgs","repos_url":"https://api.github.com/users/thunderstumpges/repos","events_url":"https://api.github.com/users/thunderstumpges/events{/privacy}","received_events_url":"https://api.github.com/users/thunderstumpges/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-08-23T06:00:52Z","updated_at":"2015-08-23T06:00:52Z","closed_at":null,"body":"First let me preface this with the comment that I really like the potential of this library, and love the fluent interface approach. I am sorry if I sound frustrated, but with Elasticsearch being a steep learning curve anyway, it is tough if the documentation for the library is incomplete or inaccurate. I can't say for sure if I am running into bugs or just undocumented \"features\" :)\r\n\r\nI am using documentation provided at http://nest.azurewebsites.net/\r\n\r\nStarting at the beginning. I need to create a mapping. \r\n\r\n1. Starting with attribute mapping on my type, the documentation shows many `ElasticType` attribute properties, but on mine I only see two: `Name` and important one for me `IdProperty` which I'm guessing (and hoping) is to tell Nest what property should be mapped to the _id for the type. It is not shown nor discussed in the documentation.\r\n\r\n2. [Documentation](http://nest.azurewebsites.net/nest/indices/put-mapping.html) for `Map<T>()` shows an empty method signature:\r\n```csharp\r\nvar response = this.ConnectedClient.Map<ElasticSearchProject>();\r\n```\r\nHowever in code, it takes a `Func<PutMappingDescriptor<T>,PutMappingDescriptor<T>>` \r\n\r\nWhile I have seen references in other places in the documentation of use of this with `m => m.MapFromAttributes()` I'm not 100% certain what this does (though I guessed that it should map my type from the attributes I specified.\r\n\r\nI have (I believe) successfully created my mapping (though I don't see any reference to the id field when I get the mapping back using a raw REST call)\r\n\r\n3. Attempting to use the BulkAsync call was failing for me using almost exactly the code example in the [Bulk documentation](http://nest.azurewebsites.net/nest/core/bulk.html). Documentation shows:\r\n```csharp\r\nvar descriptor = new BulkDescriptor();\r\n\r\nforeach (var i in Enumerable.Range(0, 1000))\r\n{\r\n    descriptor.Index<ElasticSearchProject>(op => op\r\n        .Document(new ElasticSearchProject {Id = i})\r\n    );\r\n}\r\nvar result = client.Bulk(descriptor);\r\n```\r\n\r\nWith that code, and my attribute annotated type, the result from the Bulk call were validation errors on every operation saying \"missing index, missing type\". SO I then found *undocumented*... an option for \"Index\" and \"Type\" on the descriptor.Index call:\r\n\r\n```csharp\r\nbulk.Index<MyType>(op => op.Index(\"myindex\").Type(\"mytype\").Document(objMyType));\r\n```\r\nThis didn't help :(\r\n\r\nOnly when I finally tried the *also undocumented* `FixedPath` option on the `BulkDescriptor` object did it actually specify the index and type in the request (and I'm guessing it would have to be the same index and type for all documents in the BulkDescriptor request..?\r\n\r\n`bulk.FixedPath(\"myindex\",\"mytype\");`\r\n\r\n4. After finally getting a bunch of documents indexed, I notice it is NOT using my id field as specified in the `ElasticType(IdProperty=\"id\")` attribute. Instead I get internally generated IDs for all of my documents.\r\n\r\nAm I just missing some more documentation somewhere? Is there a bug with the code? I can't tell for sure. Thanks in advance.\r\n"}}