Skip to content

Conversation

@ghalliday
Copy link
Member

@ghalliday ghalliday commented Dec 23, 2025

Type of change:

  • This change is a bug fix (non-breaking change which fixes an issue).
  • This change is a new feature (non-breaking change which adds functionality).
  • This change improves the code (refactor or other change that does not change the functionality)
  • This change fixes warnings (the fix does not alter the functionality or the generated code)
  • This change is a breaking change (fix or feature that will cause existing behavior to change).
  • This change alters the query API (existing queries will have to be recompiled)

Checklist:

  • My code follows the code style of this project.
    • My code does not create any new warnings from compiler, build system, or lint.
  • The commit message is properly formatted and free of typos.
    • The commit message title makes sense in a changelog, by itself.
    • The commit is signed.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly, or...
    • I have created a JIRA ticket to update the documentation.
    • Any new interfaces or exported functions are appropriately commented.
  • I have read the CONTRIBUTORS document.
  • The change has been fully tested:
    • I have added tests to cover my changes.
    • All new and existing tests passed.
    • I have checked that this change does not introduce memory leaks.
    • I have used Valgrind or similar tools to check for potential issues.
  • I have given due consideration to all of the following potential concerns:
    • Scalability
    • Performance
    • Security
    • Thread-safety
    • Cloud-compatibility
    • Premature optimization
    • Existing deployed queries will not be broken
    • This change fixes the problem, not just the symptom
    • The target branch of this pull request is appropriate for such a change.
  • There are no similar instances of the same problem that should be addressed
    • I have addressed them here
    • I have raised JIRA issues to address them separately
  • This is a user interface / front-end modification
    • I have tested my changes in multiple modern browsers
    • The component(s) render as expected

Smoketest:

  • Send notifications about my Pull Request position in Smoketest queue.
  • Test my draft Pull Request.

Testing:

@ghalliday ghalliday requested review from Copilot and dcamper December 23, 2025 14:07
@ghalliday
Copy link
Member Author

Note: Tests are part of a different PR - #20772

@github-actions
Copy link

Jira Issue: https://hpccsystems.atlassian.net//browse/HPCC-35541

Jirabot Action Result:
Assigning user: gavin.halliday@lexisnexisrisk.com
Workflow Transition To: Merge Pending
Updated PR

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR fixes a bug in the handling of FILEPOSITION(TRUE) when the last field of an index record is a string (non-integer type). The issue occurred when the system needed to convert FILEPOSITION(TRUE) to FILEPOSITION(FALSE) but failed to remove the existing attribute before adding the new one, resulting in conflicting attribute values.

Key Changes:

  • Modified the checkIndexRecord function to properly replace the FILEPOSITION attribute instead of appending a duplicate
  • Changed from directly appending FILEPOSITION(false) to: unwinding the attribute list, removing any existing fileposition attributes, then adding the new FILEPOSITION(false) attribute

Signed-off-by: Gavin Halliday <gavin.halliday@lexisnexis.com>
Copy link
Contributor

@dcamper dcamper left a comment

Choose a reason for hiding this comment

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

Looks good.

@ghalliday ghalliday merged commit b48f8cb into hpcc-systems:candidate-9.14.x Jan 5, 2026
50 of 51 checks passed
@github-actions
Copy link

github-actions bot commented Jan 5, 2026

Jirabot Action Result:
Added fix version: 9.14.48
Added fix version: 10.0.22
Workflow Transition: 'Resolve issue'

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.

2 participants