You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
...so that I can re-index peacefully in a new timestamped index whenever that is going to be needed.
π Additional Details
The timestamped index (e.g. <discipline node>-registry-20250323) have aliases on <discipline node>-registry and registry so that the index access is invariant for the users.
So instead of:
{discipline node}-registry
{discipline node}-registry-refs
{discipline node}-registry-dd
We want to name the registry indexes:
{discipline node}-registry-{YYYYMMDD}
{discipline node}-registry-refs-{YYYYMMDD}
{discipline node}-registry-dd-{YYYYMMDD}
where YYYYMMDD is the time of the day.
The aliases described above are configured with the index at their creation.
Acceptance Criteria
Given When I perform Then I expect
βοΈ Engineering Details
No response
π I&T
No response
The text was updated successfully, but these errors were encountered:
Checked for duplicates
Yes - I've already checked
π§βπ¬ User Persona(s)
Engineering Node administrator
πͺ Motivation
...so that I can re-index peacefully in a new timestamped index whenever that is going to be needed.
π Additional Details
The timestamped index (e.g.
<discipline node>-registry-20250323
) have aliases on<discipline node>-registry
andregistry
so that the index access is invariant for the users.So instead of:
We want to name the registry indexes:
where YYYYMMDD is the time of the day.
The aliases described above are configured with the index at their creation.
Acceptance Criteria
Given
When I perform
Then I expect
βοΈ Engineering Details
No response
π I&T
No response
The text was updated successfully, but these errors were encountered: