-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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.
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
Add Fleet action results system data stream #71667
Conversation
This commit adds support for system data streams and also the first use of a system data stream with the fleet action results data stream.
@elasticmachine run elasticsearch-ci/1 |
x-pack/plugin/core/src/main/resources/fleet-actions-results.json
Outdated
Show resolved
Hide resolved
The ILM policy did not exist when you tested. I just pushed a change that will create the ILM policy but I do wonder if the UI needs to be updated for system data streams; maybe some options don't make sense? For the ILM policy, I'd expect the user to be able to edit it to change what they want to store in the datastream and how long they want to keep data in a certain data tier even. |
picked up the latest changes, seeing these in the log
|
That's what I get for not writing a test; sorry. Should be good to go now with a test. |
saw this error:
|
Pinging @elastic/es-core-features (Team:Core/Features) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! I left a few small comments.
client/rest-high-level/src/main/java/org/elasticsearch/client/indices/DataStream.java
Outdated
Show resolved
Hide resolved
server/src/main/java/org/elasticsearch/cluster/metadata/MetadataCreateDataStreamService.java
Outdated
Show resolved
Hide resolved
server/src/main/java/org/elasticsearch/indices/SystemDataStreamDescriptor.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Implementation looks good to me. I left a few small comments.
server/src/main/java/org/elasticsearch/indices/SystemDataStreamDescriptor.java
Outdated
Show resolved
Hide resolved
...a-streams/src/internalClusterTest/java/org/elasticsearch/datastreams/SystemDataStreamIT.java
Outdated
Show resolved
Hide resolved
import static org.hamcrest.Matchers.equalTo; | ||
import static org.hamcrest.Matchers.is; | ||
|
||
public class SystemDataStreamIT extends ESIntegTestCase { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this test be turned into a qa module inside ../plugin/data-streams/qa
?
That feels more robust to me. (the qa module would then both be an esplugin and java-rest-test)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you be ok with this refactor being a follow up?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still looking good. One little suggestion on a variable name.
server/src/main/java/org/elasticsearch/cluster/metadata/IndexNameExpressionResolver.java
Outdated
Show resolved
Hide resolved
This commit adds support for system data streams and also the first use of a system data stream with the fleet action results data stream. A system data stream is one that is used to store system data that users should not interact with directly. Elasticsearch will manage these data streams. REST API access is available for external system data streams so that other stack components can store system data within a system data stream. System data streams will not use the system index read and write threadpools. Backport of #71667
This change reenables BWC tests after elastic#71667 was backported in elastic#71966.
This commit adds support for system data streams and also the first use
of a system data stream with the fleet action results data stream. A
system data stream is one that is used to store system data that users
should not interact with directly. Elasticsearch will manage these data
streams. REST API access is available for external system data streams
so that other stack components can store system data within a system
datastream. System data streams will not use the system index read and
write threadpools.