Skip to content
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

Fixes #3630 - ClientContext updated to handle time duration values correctly #3631

Merged
merged 1 commit into from Jul 20, 2023

Conversation

keith-ratcliffe
Copy link
Contributor

No description provided.

@keith-ratcliffe
Copy link
Contributor Author

Same bug here which I missed, for conditional writer timeout. The test uses an prop value of "17" (defaulting to time unit of SECONDS) and then asserts that 17000 seconds is expected

- ClientContext updated to handle time duration values correctly
- ClientContextTest updated accordingly
@keith-ratcliffe
Copy link
Contributor Author

Rebased/squash commit now includes the fix for CONDITIONAL_WRITER_TIMEOUT_MAX and also cleanup/refinement of the affected junits in ClientContextTest

@dlmarion
Copy link
Contributor

@keith-ratcliffe - Thanks for your contribution. I see this is your first time contributing. Feel free to put up a PR on https://github.com/apache/accumulo-website to add yourself to the people page.

@dlmarion dlmarion merged commit 2917cdf into apache:2.1 Jul 20, 2023
8 checks passed
@keith-ratcliffe keith-ratcliffe deleted the bugfix/ClientContext branch July 20, 2023 21:11
@ctubbsii ctubbsii added this to In progress in 2.1.2 via automation Jul 25, 2023
@ctubbsii ctubbsii moved this from In progress to Done in 2.1.2 Jul 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
2.1.2
Done
Development

Successfully merging this pull request may close these issues.

ClientContext performing incorrect conversion of PropertyType.TIMEDURATION values
2 participants