Skip to content

Conversation

@rjernst
Copy link
Member

@rjernst rjernst commented Jun 8, 2021

When libs/core was created, several classes were moved from server's
o.e.common package, but they were not moved to a new package. Split
packages need to go away long term, so that Elasticsearch can even think
about modularization. This commit moves all the classes under o.e.common
in core to o.e.core.

relates #73784

When libs/core was created, several classes were moved from server's
o.e.common package, but they were not moved to a new package. Split
packages need to go away long term, so that Elasticsearch can even think
about modularization. This commit moves all the classes under o.e.common
in core to o.e.core.

relates elastic#73784
@rjernst rjernst added :Core/Infra/Core Core issues without another label >refactoring v8.0.0 v7.14.0 labels Jun 8, 2021
@elasticmachine elasticmachine added the Team:Core/Infra Meta label for core/infra team label Jun 8, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (Team:Core/Infra)

@rjernst
Copy link
Member Author

rjernst commented Jun 8, 2021

Note that the classes here are rarely changed, so the possibility for create backport conflicts should be low. I think we can backport this to 7.x, and if for some reason a change is needed in 7.13 to one of these classes, that can be handled manually if the rename is not picked up in the cherry pick.

@rjernst rjernst requested a review from mark-vieira June 8, 2021 15:17
@mark-vieira
Copy link
Contributor

In a lot of cases I find that git's rename detection and handling for merges/cherry-picks is pretty good so it's probably not too much of a concern.

Copy link
Contributor

@mark-vieira mark-vieira left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@rjernst rjernst merged commit 68817d7 into elastic:master Jun 8, 2021
@rjernst rjernst deleted the modularize6 branch June 8, 2021 16:53
rjernst added a commit to rjernst/elasticsearch that referenced this pull request Jun 8, 2021
o.e.common package, but they were not moved to a new package. Split
packages need to go away long term, so that Elasticsearch can even think
about modularization. This commit moves all the classes under o.e.common
in core to o.e.core.

relates elastic#73784
backport elastic#73909
rjernst added a commit that referenced this pull request Jun 8, 2021
When libs/core was created, several classes were moved from server's
o.e.common package, but they were not moved to a new package. Split
packages need to go away long term, so that Elasticsearch can even think
about modularization. This commit moves all the classes under o.e.common
in core to o.e.core.

relates #73784
backport #73909
@dadoonet
Copy link
Contributor

dadoonet commented Aug 4, 2021

When upgrading the HLClient to 7.14.0, this is breaking my project as the BulkProcessor exposes a TimeValue with the setFlushInterval(TimeValue) method.
Note that the BulkProcessor is documented at https://www.elastic.co/guide/en/elasticsearch/client/java-rest/current/java-rest-high-document-bulk.html#java-rest-high-document-bulk-processor

I see several options:

  • Do nothing (the change is trivial)
  • Add back a Deprecated org.elasticsearch.common.unit.TimeValue class in 7.x branch which extends org.elasticsearch.core.TimeValue (and keep it removed in main branch)
  • Add a breaking change in the documentation. We don't have such a page in the Rest Client documentation so this can be added to this page https://www.elastic.co/guide/en/elasticsearch/reference/current/migrating-7.14.html?

@rjernst
Copy link
Member Author

rjernst commented Sep 2, 2021

@dadoonet We discussed this in the core/infra sync and decided to do nothing here (your option 1). As you pointed out, the change is trivial. Additionally, there has always been an expectation for HL Client (and transport client and plugins) that because they depend on the server jar, there is always the possibility of needing compile changes on upgrades.

hmottestad added a commit to eclipse-rdf4j/rdf4j that referenced this pull request Feb 15, 2022
… no deprecation of the old class, see elastic/elasticsearch#73909

Signed-off-by: Håvard Ottestad <[email protected]>
@hmottestad
Copy link

This broke our code by stopping users from upgrading their own code to use a newer minor version of Elasticsearch than the one we are depending on (7.8.1).

hmottestad added a commit to eclipse-rdf4j/rdf4j that referenced this pull request Feb 15, 2022
… no deprecation of the old class, see elastic/elasticsearch#73909

Signed-off-by: Håvard Ottestad <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Core/Infra/Core Core issues without another label >refactoring Team:Core/Infra Meta label for core/infra team v7.14.0 v8.0.0-alpha1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants