Support 7.0

[KodrAus]

Since we don't map a lot of the Query DSL yet this should just be a matter of tweaking some bits in elastic_types and updating CI to target 6.0.

The biggest change to think about is the removing support for multiple types per index. An implication is that we could remove indices as required parameters and rely on the type name as a default. It raises a question of whether all operations, like index_create, should require a generic document type.

[mbilker]

I just tried to use this library with 6.0.0 and I got an error when indexing a document stating missing field "created", which I assume is because the created field has been removed and replaced with the operation field[1].

[1] https://www.elastic.co/guide/en/elasticsearch/reference/6.x/breaking_60_docs_changes.html

[KodrAus]

Ah thanks @mbilker! These are all localised to the responses side but are breaking changes so I'll need to roll them up into the next release. I don't have much blocking that besides a half-baked cluster sniffer so will work on 6.0 support and get that up on crates.io ASAP.

[mbilker]

Thank you very much and glad to be of help!

Luckily I am only working on a small personal project and I just rolled back to 5.6.4, but I will likely test changes for 6.x support as I have two virtual machines, one with 5.6.4 and one with 6.0.0.

[KodrAus]

Just to communicate the plan here, I'm thinking I'll cut a release of 0.21.0 with the new client features, and then focus on support for Elasticsearch 6.0 purely for 0.22.0. I think that path should be clearer for people looking to upgrade, and anyone stuck on 5.0 for now can still get the benefit of some of these new features.

[twilco]

Hey! I'm interested in seeing support for ES6. Is there anywhere I can lend a hand to help with this?

[KodrAus]

Hi @twilco!

This library's in a bit of a state where it's hard to meaningfully contribute to at the moment unfortunately. I need to get #315 polished up and merged, and then get the work-in-progress stuff off the vNext branch and onto master, then we should be in a better place to look at what else needs to be done to support Elasticsearch 6.

I've got a little time later today, so I'll try get that moving again.

[twilco]

Thanks for the update! If there's some way others can contribute once that work has been completed drop another comment 😄

[KodrAus]

Alrighty! I've cleaned up and merged all the work in progress onto master and updated the integration tests to run against Elasticsearch 6.5.

I think what we really need now is some good testing to make sure everything is looking good for 6.0 support, because the integration test coverage is a bit thin at the moment.

If folks would like to give it a go I can publish a preview on crates.io. There are some significant API changes between master and what's published at the moment.