Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multivariant system test support for TSDB enabled package #8827

Closed
wants to merge 2 commits into from
Closed

Multivariant system test support for TSDB enabled package #8827

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ec5d72d
Multivariant system test support for TSDB enabled package
agithomas Jan 4, 2024
857c23b
Update docs/developer_tsdb_migration_guidelines.md
agithomas Jan 17, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/developer_tsdb_migration_guidelines.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -153,6 +153,15 @@ A field that holds millions of unique values may not be an ideal candidate for b

# <a id="troubleshooting"></a> Troubleshooting

### Enabling multiple variants support in system tests
ritalwar marked this conversation as resolved.
Show resolved Hide resolved

If the system test configuration for a TSDB-enabled package contains multiple variants, make sure to set the `kibana.version` specified in the `manifest.yml` file of the package to `8.8.1` or a version higher.
Copy link
Member

Choose a reason for hiding this comment

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

This is actually an issue with any attempt to run the same system tests multiple times in the same deployment. I wonder if we should investigate some way to address this case in elastic-package.

I think the issue was fixed in elastic/elasticsearch#96461.


```yaml
conditions:
kibana.version: "^8.8.1"
```

### Conflicting field type

Fields having conflicting field type will not be considered as dimension. Resolve the field type ambiguity before defining a field as dimension field.
Expand Down