Skip to content

Remove full-node-capable node allocator#12191

Merged
losipiuk merged 2 commits intotrinodb:masterfrom
losipiuk:lo/rm-full-node-capable-allocator
Apr 29, 2022
Merged

Remove full-node-capable node allocator#12191
losipiuk merged 2 commits intotrinodb:masterfrom
losipiuk:lo/rm-full-node-capable-allocator

Conversation

@losipiuk
Copy link
Copy Markdown
Member

Description

Full-node-capable node allocator was an intermediate step
towards bin-packing one. No longer needed.

Is this change a fix, improvement, new feature, refactoring, or other?

cleanup (removal of obsolete feature)

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

core

How would you describe this change to a non-technical end user or system administrator?

N/A

Documentation

(x) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

(x) No release notes entries required.
( ) Release notes entries required with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

Full-node-capable node allocator was an intermediate step
towards bin-packing one. No longer needed.
@cla-bot cla-bot bot added the cla-signed label Apr 29, 2022
@losipiuk losipiuk requested review from arhimondr and linzebing April 29, 2022 12:12
@losipiuk losipiuk merged commit af33626 into trinodb:master Apr 29, 2022
@github-actions github-actions bot added this to the 380 milestone Apr 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants