Skip to content

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
@keith-ratcliffe keith-ratcliffe deleted the bugfix/ClientContext branch July 20, 2023 21:11
@ctubbsii ctubbsii added this to the 2.1.2 milestone Jul 12, 2024
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.

ClientContext performing incorrect conversion of PropertyType.TIMEDURATION values

3 participants