-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add additional meta fields to DocumentType #315
Conversation
Could also clean up the client methods by wrapping the document type in a separate method so that generics can be used: client.document::<MyType>().get(33).send()?; instead of: client.document_get::<MyType>(Id::from(33)).send()?; That would make it clearer how |
Will need to figure out what the docs should look like for this change to the document methods. |
6614037
to
0d6f05a
Compare
- index - ty - id These can be used by the various high-level APIs to extract values when available
0d6f05a
to
452f87b
Compare
This also includes some movement towards supporting Elasticsearch 6.0, but we'll need to build out more document type integration tests to be confident that stuff is correct. Once this merges we should push |
* add meta fields to document type * add partial static methods * refactor request paths for better inference * update for Elasticsearch 6.0
Closes #301
Closes #302
Closes #308
Closes #313
Includes
index
,ty
andid
. This allows us to infer the values for these document type specific fields in high-level APIs taking aT: DocumentType
instead of requiring them everywhere.It's part of a long-overdue revamp of the
DocumentType
trait design.