Alex ShtinandGitHub e9bf129fdc Unalias and validate search attributes when import workflow history (#6563) ...

## What changed?
<!-- Describe what has changed in this PR -->
Unalias and validate search attributes when import workflow history.

## Why?
<!-- Tell your future self why have you made these changes -->
Search attributes in workflow histostory JSON file might use aliases (if
history was exported using `temporal` cli) or be invalid
(name/type/length). Previously import blindly accepted any search
attributes and then background visibility task processing could fail.
Now search attributes are validated and unaliased (if needed) before
getting to the history service.

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
Added new unit tests for both valid and invalid cases.

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
No risks.

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->
No.

2024-10-04 22:43:34 +00:00

..

main.go

Unalias and validate search attributes when import workflow history (#6563)

2024-10-04 22:43:34 +00:00