Skip to content

Conversation

@cshannon
Copy link
Contributor

@cshannon cshannon commented Feb 23, 2024

Instead of using a boolean value for obtaining table locks, use an enum which makes the code more readable and makes it easier to search and catch errors with the lock type. The enum used already existed in DistributedReadWriteLock.

This closes #4276

Instead of using a boolean value for obtaining table locks, use an enum
which makes the code more readable and makes it easier to search and
catch errors with the lock type.

This closes apache#4276
@cshannon cshannon self-assigned this Feb 23, 2024
@cshannon
Copy link
Contributor Author

This current PR is for main, I'll fix the conflicts when merging into elasticity after this is merged to main

@cshannon
Copy link
Contributor Author

cshannon commented Feb 23, 2024

Actually in elasticity virtually everything is a conflict so it will be simpler to merge this forward as an empty commit and then just do a separate PR for elasticity, #4298

@cshannon cshannon changed the title Replace boolean with enum for table locks Replace boolean with enum for table locks in 3.1 Feb 23, 2024
@cshannon cshannon merged commit 3b1566f into apache:main Feb 26, 2024
@cshannon cshannon deleted the accumulo-4276 branch February 26, 2024 18:28
@ctubbsii ctubbsii added this to the 3.1.0 milestone Jul 12, 2024
@ctubbsii ctubbsii modified the milestones: 3.1.0, 4.0.0 Mar 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Replace boolean with enum for table locks

3 participants