Skip to content

[Backport 9.1] Fix find_stucture format enum #5708

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

Merged
merged 1 commit into from
Nov 20, 2025
Merged

[Backport 9.1] Fix find_stucture format enum #5708

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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: 8 additions & 1 deletion specification/text_structure/find_structure/FindStructureRequest.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,7 @@ export interface Request<TJsonDocument> {
* In this default scenario, all rows must have the same number of fields for a delimited format to be detected.
* If the format is set to `delimited` and the delimiter is not set, however, the API tolerates up to 5% of rows that have a different number of columns than the first row.
*/
format?: string
format?: FindStructureFormat
/**
* If you have set `format` to `semi_structured_text`, you can specify a Grok pattern that is used to extract fields from every message in the text.
* The name of the timestamp field in the Grok pattern must match what is specified in the `timestamp_field` parameter.
Expand Down Expand Up @@ -207,3 +207,10 @@ export interface Request<TJsonDocument> {
* @codegen_name text_files */
body: Array<TJsonDocument>
}

export enum FindStructureFormat {
ndjson,
xml,
delimited,
semi_structured_text
}