Skip to content

[SR] Selected indices do not show when editing a policy created via console#59486

Closed
jkelastic wants to merge 9 commits intoelastic:masterfrom
jkelastic:bugfix/Snapshot_plugin_restore_custom_pattern
Closed

[SR] Selected indices do not show when editing a policy created via console#59486
jkelastic wants to merge 9 commits intoelastic:masterfrom
jkelastic:bugfix/Snapshot_plugin_restore_custom_pattern

Conversation

@jkelastic
Copy link
Contributor

Summary

Fixes #47156 Rename index pattern to custom pattern and default to customer pattern page

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

For maintainers

Release note

This PR resolves an issue where the indices of a Snapshot Lifecycle Policy were not always displayed correctly in the Snapshot & Restore UI when editing an existing policy.

@jkelastic jkelastic added v7.7.0 v8.0.0 Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more t// labels Mar 5, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/es-ui (Team:Elasticsearch UI)

@jkelastic jkelastic added release_note:fix Feature:Snapshot and Restore Elasticsearch snapshots and repositories UI labels Mar 5, 2020
@alisonelizabeth alisonelizabeth self-requested a review March 6, 2020 02:29
@alisonelizabeth
Copy link
Contributor

alisonelizabeth commented Mar 6, 2020

Hi @jkelastic! Can you please take another look at this one? It looks like the code is referencing an import that does not exist anymore and the settings step no longer loads.

Screen Shot 2020-03-06 at 11 00 33 AM

@jkelastic jkelastic requested review from a team as code owners March 11, 2020 19:54
@cla-checker-service
Copy link

cla-checker-service bot commented Mar 11, 2020

💚 CLA has been signed

@jkelastic jkelastic force-pushed the bugfix/Snapshot_plugin_restore_custom_pattern branch 2 times, most recently from 9eb1596 to 9b84595 Compare March 12, 2020 21:25
@mshustov mshustov removed the request for review from a team March 13, 2020 17:14
@alisonelizabeth
Copy link
Contributor

@jkelastic looks like there are still some problems here. Can you take a look? Once it's been resolved and you have tested the changes, please let know and I will review the PR again. Let me know if you need any help. Thanks!

Screen Shot 2020-03-16 at 11 27 42 AM

@jkelastic jkelastic closed this Mar 24, 2020
@jkelastic
Copy link
Contributor Author

closing temporarily as I'm short on time to make this for 7.7, will reopen later

@jkelastic jkelastic reopened this Aug 3, 2020
@jkelastic jkelastic added v7.10.0 and removed v7.7.0 labels Aug 3, 2020
@jkelastic jkelastic force-pushed the bugfix/Snapshot_plugin_restore_custom_pattern branch from d627633 to 3545c8d Compare August 3, 2020 19:02
@jkelastic jkelastic requested a review from a team as a code owner August 3, 2020 19:02
@alisonelizabeth alisonelizabeth removed the request for review from a team August 5, 2020 03:13
Copy link
Contributor

@alisonelizabeth alisonelizabeth left a comment

Choose a reason for hiding this comment

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

Hi @jkelastic. Thanks for picking this one back up! I didn't test your changes yet, but I did notice a few issues in the translation file. Can you take a look? I believe you should only need to delete xpack.snapshotRestore.policyValidation.indexPatternRequiredErrorMessage; the rest of the translation file should remain the same.

"kbn.advancedSettings.storeUrlTitle": "セッションストレージに URL を格納",
"kbn.advancedSettings.themeVersionText": "現在のバージョンと次のバージョンのKibanaで使用されるテーマを切り替えます。この設定を適用するにはページの更新が必要です。",
"kbn.advancedSettings.themeVersionTitle": "テーマバージョン",
"kbn.advancedSettings.timepicker.timeDefaultsText": "時間フィルターが選択されずに Kibana が起動した際に使用される時間フィルターです",
Copy link
Contributor

Choose a reason for hiding this comment

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

This seems unrelated to your change; I don't think it should be deleted.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@alisonelizabeth I think my local master branch is out of sync. After adding back the translations I'm no longer getting unused translation.

"kbn.advancedSettings.themeVersionText": "現在のバージョンと次のバージョンのKibanaで使用されるテーマを切り替えます。この設定を適用するにはページの更新が必要です。",
"kbn.advancedSettings.themeVersionTitle": "テーマバージョン",
"kbn.advancedSettings.timepicker.timeDefaultsText": "時間フィルターが選択されずに Kibana が起動した際に使用される時間フィルターです",
"kbn.advancedSettings.timepicker.timeDefaultsTitle": "デフォルトのタイムピッカー",
Copy link
Contributor

Choose a reason for hiding this comment

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

Same here

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Same here, everything looks good.

"xpack.watcher.watcherDescription": "アラートの作成、管理、監視によりデータへの変更を検知します。"
}
}
} No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

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

can you add back the new line at the end of the file?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Same here, everything looks good.

"xpack.ml.newJob.wizard.jobDetailsStep.advancedSection.enableModelPlotAnnotations.description": "選択すると、モデルが大幅に変更されたときに注釈を生成します。たとえば、ステップが変更されると、期間や傾向が検出されます。",
"xpack.ml.newJob.wizard.jobDetailsStep.advancedSection.enableModelPlotAnnotations.title": "モデル変更注釈を有効にする",
"xpack.ml.newJob.wizard.jobDetailsStep.advancedSection.mmlWarning.message": "モデルプロットの作成には大量のリソースを消費する可能性があり、選択されたフィールドの基数が100を超える場合はお勧めしません。このジョブの予測基数は{highCardinality}です。 この構成でモデルプロットを有効にする場合、専用の結果インデックスを選択することをお勧めします。",
"xpack.ml.newJob.wizard.jobDetailsStep.advancedSection.mmlWarning.message": "モデルプロットの作成には大量のリソースを消費する可能性があり、選択されたフィールドの基数が100を超える場合はお勧めしません。このジョブの予測基数は{highCardinality}です。 この構成でモデルプロットを有効にする場合、専用の結果インデックスを選択することをお勧めします。",
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not sure why there's a diff here. I think we should try to leave any translations not related to your changes as-is.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will do, thanks.

@jkelastic
Copy link
Contributor Author

@elasticmachine merge upstream

@jkelastic
Copy link
Contributor Author

@elasticmachine merge upstream

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Build metrics

async chunks size

id value diff baseline
snapshotRestore 758.0KB -215.0B 758.2KB

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

Copy link
Contributor

@alisonelizabeth alisonelizabeth left a comment

Choose a reason for hiding this comment

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

Hi @jkelastic! After looking at the code again, I'm not sure the original bug is relevant anymore. I'm going to assign @jloleysens to take a look and confirm. He's made some changes to this area of the code to support data streams, and is probably more familiar than I at this point.

@jkelastic
Copy link
Contributor Author

jkelastic commented Aug 31, 2020

Hi @jkelastic! After looking at the code again, I'm not sure the original bug is relevant anymore. I'm going to assign @jloleysens to take a look and confirm. He's made some changes to this area of the code to support data streams, and is probably more familiar than I at this point.

@alisonelizabeth thank you ^^

@alisonelizabeth
Copy link
Contributor

Hi @jkelastic! I verified that I'm no longer able to reproduce this issue on master, so I'm going to go ahead and close the issue and this PR.

@jkelastic
Copy link
Contributor Author

Hi @jkelastic! I verified that I'm no longer able to reproduce this issue on master, so I'm going to go ahead and close the issue and this PR.

@alisonelizabeth thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Feature:Snapshot and Restore Elasticsearch snapshots and repositories UI release_note:fix Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more t// v7.10.0 v8.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[SR] Selected indices do not show when editing a policy created via console

4 participants