Skip to content

Update 9.0 - backports from main #2613

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

Merged
merged 20 commits into from
Apr 7, 2025
Merged

Update 9.0 - backports from main #2613

merged 20 commits into from
Apr 7, 2025

Conversation

picandocodigo
Copy link
Member

Backporting from main to get this branch up to date for release.

Copy link

github-actions bot commented Apr 1, 2025

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

We use Rubocop just for development and not currently using JRuby for Rubocop development. This
could fix the current dependency problem for now.
@picandocodigo picandocodigo force-pushed the update_9.0 branch 5 times, most recently from 657afa8 to f6a5bbd Compare April 4, 2025 14:09
Based on the code written in the Elasticsearch Serverless client, this change makes the creation of
the namespace clients dynamic, removing all the files that were under `namespace` before.

Some outdated and deprecated code was removed too, like unnecessary namespaces.
* Renames __bulkify to bulkify
* Renames __escape to escape
* Renames __listify to listify
* Renames __pathify to pathify
* Renames __extract_parts to extract_parts
* Renames __rescue_from_not_found to rescue_from_not_found
The rollup feature was never GA-ed and is still tech preview. It has been deprecated since 8.11.0 in favor of downsampling.
The API now makes a request, instead of calling index like in previous versions (< 9.0.0).
* `body`, `index` and `id` are now required parameters.
* `op_type` is now a String parameter: Set to 'create' to only index the document if it does not
already exist (put if absent). If a document with the specified '_id' already exists, the indexing
operation will fail. The behavior is the same as using the '<index>/_create' endpoint. If a document
ID is specified, this paramater defaults to 'index'. Otherwise, it defaults to `create`. If the
request targets a data stream, an `op_type` of `create` is required.

Additional new parameters:
* :if_primary_term (Integer) -  Only perform the operation if the document has this primary term.
* :if_seq_no (Integer) - Only perform the operation if the document has this sequence number.
Since sending the `scroll_id` as a parameter was deprecated, now it needs to be sent in the body for
`clear_scroll`, `scroll`.
Removes connector.last_sync endpoint

The following endpoints have been promoted from Experimental to Beta:
connector.delete, connector.get, connector.list, connector.post, connector.put,
connector.sync_job_cancel, connector.sync_job_delete, connector.sync_job_get,
connector.sync_job_list, connector.sync_job_post, connector.update_api_key_id,
connector.update_configuration, connector.update_filtering, connector.update_index_name,
connector.update_name, connector.update_native, connector.update_pipelien,
connector.update_scheduling, connector.update_service_type
@picandocodigo picandocodigo merged commit 01c2adf into 9.0 Apr 7, 2025
13 checks passed
@picandocodigo picandocodigo deleted the update_9.0 branch April 7, 2025 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant