Skip to content

[CLIENT-5057] Fix string operations and expressions append and prepend not working#1155

Open
juliannguyen4 wants to merge 22 commits into
devfrom
CLIENT-5057-fix-string-append-and-prepend
Open

[CLIENT-5057] Fix string operations and expressions append and prepend not working#1155
juliannguyen4 wants to merge 22 commits into
devfrom
CLIENT-5057-fix-string-append-and-prepend

Conversation

@juliannguyen4

Copy link
Copy Markdown
Collaborator

No description provided.

…ditional / changes to tests. Also string ops tests should be refactored to make easier to change across the board.
…the same string bin. This reduces a good amount of tech debt.
… ops. TODO - Some of these are failing locally, so need to triage
…the same string bin. This reduces a good amount of tech debt.
…hange the pad string for pad_start and pad_end, but allow the target_length to be as big as NEEDLE
…non-existent bin name with value set to None instead of the bin name being absent in the bin dictionary. Add more e2e test cases that cover the rest of the string write operations that should be a no-op on a non-existent bin.
…document-string-ops-behavior-when-bin-is-missing
… in each operation's docstring instead of in the string write flags section. Also align with API docs standards by having string write ops' docstrings start with one sentence and have details in a following paragraph.
…ODO - to_string expression currently failing so need to debug it.
…g expression tests currently fail locally, so run in CI/CD
…ag' into CLIENT-5057-document-string-ops-behavior-when-bin-is-missing
…RING_TO_STRING like the to_string() operation helper.
…ions assumes that the bin contains a string. This usually would not be true for the ToString expression. This issue may also happen in other expressions like list, map etc.
…n to contain a string. This is because Aerospike expressions are strictly typed and we must pass in the bin value type
@juliannguyen4 juliannguyen4 marked this pull request as ready for review July 16, 2026 19:41
@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.38%. Comparing base (2f8dab0) to head (8d9e20a).

Additional details and impacted files
@@            Coverage Diff             @@
##              dev    #1155      +/-   ##
==========================================
+ Coverage   85.36%   85.38%   +0.02%     
==========================================
  Files         101      101              
  Lines       14602    14609       +7     
==========================================
+ Hits        12465    12474       +9     
+ Misses       2137     2135       -2     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@juliannguyen4

juliannguyen4 commented Jul 16, 2026

Copy link
Copy Markdown
Collaborator Author

Massif usage looks ok.
Build artifacts passes.
Valgrind shows no memory errors or leaks from this PR

@atripathi-aerospike

Copy link
Copy Markdown

nit: Could you please bit of Description in the PR will be great for quick understanding. Might be quick summary generated by the LLM works for me.

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.

3 participants