Skip to content

Properly account for iterator opt keys with muplitple dots#6195

Open
DomGarguilo wants to merge 1 commit intoapache:2.1from
DomGarguilo:fixIterParse
Open

Properly account for iterator opt keys with muplitple dots#6195
DomGarguilo wants to merge 1 commit intoapache:2.1from
DomGarguilo:fixIterParse

Conversation

@DomGarguilo
Copy link
Member

#6111 added increased checks when parsing iterators. One of the checks disallowed iterator opt keys to have multiple dots in it. This PR fixes that.

A new test was added to cover this case and an existing test case that was failing was fixed here.

@DomGarguilo DomGarguilo self-assigned this Mar 6, 2026
@DomGarguilo DomGarguilo added this to the 2.1.5 milestone Mar 6, 2026
@DomGarguilo DomGarguilo linked an issue Mar 6, 2026 that may be closed by this pull request
var e = assertThrows(AccumuloException.class, () -> c.namespaceOperations()
.checkIteratorConflicts(namespace, setting, EnumSet.allOf(IteratorScope.class)));
assertEquals(IllegalArgumentException.class, e.getCause().getClass());
c.namespaceOperations().checkIteratorConflicts(namespace, setting,
Copy link
Contributor

Choose a reason for hiding this comment

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

Why was this test changed?

Copy link
Contributor

@ddanielr ddanielr left a comment

Choose a reason for hiding this comment

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

Tested, confirmed this works as expected.

The code could be further simplified by stripping off the TABLE_ITERATOR_PREFIX and scope from the property string but that would require more code changes in 2.1

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.

Test failures due to backport of #6111

3 participants