![]() ![]() ![]() We are working on improving resiliency for snapshots, which will provide some relief for the case where snapshots are getting stuck. This completes the work on the new persistence layer, with just a little bit more follow-up work to do on failure handling. We integrated the new cluster state persistence layer into the Zen2 state recovery logic, allowing full-cluster restart tests to properly work now as well. Many of our tests already run with Zen2, and we are quickly moving to migrate all tests to Zen2. Further development for Zen2 will occur directly in master. In order to get to this point, significant work had to be done to ensure this would not affect the stability of the build. Zen2, our new cluster coordination and consensus layer, was just merged to the master branch of Elasticsearch - a huge milestone in this feature’s development. This has been a massive undertaking, as evidenced by the current diff of the feature branch. We are making great progress on supporting Kerberos in Elasticsearch-Hadoop, this week reaching the milestone of the ES-Hadoop test harness fully supporting Kerberos (except for Pig). This API evolves over time as we make breaking changes to the next major version, and so in order to get complete coverage, users will need to upgrade to the final 6.x minor release in order to capture all 7.0 breaking changes via this API. The deprecation info API highlights for users functionality they are using that will be removed or changed on the next major version. Our running list of breaking changes that will be addressed by the API is here. We are upgrading the deprecation info API for all 7.0 breaking changes. This is an important step to ease the usage of synonyms in our analysis chain but we have a lot more to do to improve the overall experience. With the new validation we'll be able to tell the users which filter is responsible of the failure and we'll report an error that explain why the filter should be moved. The synonym filter that we use cannot handle stacked tokens (tokens that appear at the same position) so any filter that produce such tokens throws an error when it is used to build synonyms. ![]() We added a way to fail early when an analysis chain contains a filter that is not compatible with synonyms. In doing so, we also updated the internal navigation to the new K7 breadcrumb style.īetter validation of analyzer with synonyms This will allow users to configure remote clusters to be available for both cross-cluster search and cross-cluster replication. We have finished the full CRUD UI to support managing remote clusters. Shortly after the cutover, the existing repository will be retired. This means that bug reports and feature requests for the Elasticsearch Docker image will also need to go to the main Elasticsearch repository. Starting with version 6.6.0 of Elasticsearch, our Docker image build will be located within the main product repository (e.g., /elastic/elasticsearch). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |