Skip to content

Elasticsearch ~6.8 upgrade#25

Draft
kilgore5 wants to merge 3 commits into
feature/security-upgrades-guzzle-etcfrom
feature/elasticsearch-upgrade
Draft

Elasticsearch ~6.8 upgrade#25
kilgore5 wants to merge 3 commits into
feature/security-upgrades-guzzle-etcfrom
feature/elasticsearch-upgrade

Conversation

@kilgore5
Copy link
Copy Markdown
Contributor

@kilgore5 kilgore5 commented Jan 25, 2024 •
edited
Loading

upgrade Elasticsearch 6.1 -> 6.8 (latest release compatible with elasticsearch 6)

Release 6.8.2
Fix #1131 class naming for some endpoints used in elasticsearch-php < 6.8. These endpoints are: NodeAttrs, ForceMerge, MTermVectors, TermVectors (https://github.com/elastic/elasticsearch-php/pull/1151)
Release 6.8.1
Fix missing class aliases in 6.8.0 (https://github.com/elastic/elasticsearch-php/pull/1114)
Backported fix #1066 (https://github.com/elastic/elasticsearch-php/pull/1109)
Release 6.8.0
Added XPack endpoints
Added X-Opaque-Id header (https://github.com/elastic/elasticsearch-php/pull/952)
Added X-Elastic-Client-Meta header (https://github.com/elastic/elasticsearch-php/pull/1089)
Added the license header (https://github.com/elastic/elasticsearch-php/commit/0ff5fb98745a511118df5b1a68ca54d892b08ee3)
Support of PHP 8 (https://github.com/elastic/elasticsearch-php/pull/1095 and https://github.com/elastic/elasticsearch-php/pull/1063)
Replace array_walk with array_map in Connection::getURI (https://github.com/elastic/elasticsearch-php/pull/1075)
Fix for #1064 reset custom headers (https://github.com/elastic/elasticsearch-php/pull/1065)
Replace guzzlehttp/ringphp with ezimuel/ringphp (https://github.com/elastic/elasticsearch-php/pull/1102)v

testing note

kilgore5 added 3 commits January 24, 2024 21:46
composer.json... try updating to elasticsearch 6.8, latest in ~6
37900e9
composer.lock... bin/composer update elasticsearch/elasticsearch
42581e3
composer.lock... bin/composer remove guzzlehttp/ringphp
6855de0 
```
Johns-MBP:elastic-press johnroyall$ bin/composer update elasticsearch/elasticsearch
Loading composer repositories with package information
Warning from https://repo.packagist.org: Support for Composer 1 is deprecated and some packages will not be available. You should upgrade to Composer 2. See https://blog.packagist.com/deprecating-composer-1-support/
Updating dependencies (including require-dev)
Package operations: 2 installs, 1 update, 0 removals
  - Installing ezimuel/guzzlestreams (3.1.0): Downloading (100%)
  - Installing ezimuel/ringphp (1.1.2): Downloading (100%)
  - Updating elasticsearch/elasticsearch (v6.7.2 => v6.8.2): Downloading (100%)
```

```
Johns-MBP:elastic-press johnroyall$ bin/composer remove  guzzlehttp/ringphp
guzzlehttp/ringphp is not required in your composer.json and has not been removed
Loading composer repositories with package information
Warning from https://repo.packagist.org: Support for Composer 1 is deprecated and some packages will not be available. You should upgrade to Composer 2. See https://blog.packagist.com/deprecating-composer-1-support/
Updating dependencies (including require-dev)
Package operations: 0 installs, 1 update, 2 removals
  - Removing guzzlehttp/streams (3.0.0)
  - Removing guzzlehttp/ringphp (1.1.1)
  - Updating react/promise (v2.8.0 => v2.11.0): Downloading (100%)
```
@kilgore5 kilgore5 requested a review from jGRUBBS January 25, 2024 21:47
@kilgore5 kilgore5 added this to the 0-9-stable milestone Jan 25, 2024
@kilgore5 kilgore5 changed the title Feature/elasticsearch upgrade Elasticsearch ~6.8 upgrade Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jGRUBBS jGRUBBS Awaiting requested review from jGRUBBS

Assignees

@jGRUBBS jGRUBBS

Labels

None yet

Projects

None yet

Milestone

0-9-stable

Development

Successfully merging this pull request may close these issues.

2 participants

@kilgore5 @jGRUBBS