Skip to content

Commit

Permalink
Refactor index refresh logic
Browse files Browse the repository at this point in the history
Instead of refreshing all indices, which could lead to a warning when a system index is refreshed and cause the test to fail due to the unexpected warning, I modified the logic to refresh only the required 'test' index.

Signed-off-by: rithin-pullela-aws <[email protected]>
  • Loading branch information
rithin-pullela-aws committed Feb 5, 2025
1 parent ee3d940 commit 680aed1
Showing 1 changed file with 2 additions and 6 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,8 @@ setup:
index: test
id: 2
body: { "field1": "v1 aoeu", "field2": " ua u v2", "field3": "foo bar text", "user_rating": 0.0 }
- do:
indices.refresh: { test }

- do:
ltr.create_store: {}
Expand Down Expand Up @@ -57,9 +59,6 @@ setup:

# Model only uses a single feature... although feature set has multiple

- do:
indices.refresh: {}

- do:
ltr.create_model_from_set:
name: my_featureset
Expand Down Expand Up @@ -117,9 +116,6 @@ setup:
feature2: 2.3
no_param_feature: 3.0

- do:
indices.refresh: {}

---
"single feature ranklib model":
- do:
Expand Down

0 comments on commit 680aed1

Please sign in to comment.