github-mirrors/elasticsearch
1
0
Fork 0
mirror of https://github.com/elastic/elasticsearch.git synced 2025-06-28 09:28:55 -04:00
Code Issues Projects Releases Packages Wiki Activity

[ML] [DOCS] update find-structure reference docs (#67586)

Browse source 
The text structure finder API documentation had many references to the "files". While this is one use of the API, the API now has a more generic name. This commit replaces many references to the word "file" to the more generic word "text".
This commit is contained in:
Benjamin Trent 2021-01-15 12:19:38 -05:00 • committed by GitHub
parent a794743d43
commit 24ebcc8c24
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
5 changed files with 62 additions and 63 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/reference/ml/anomaly-detection/apis/find-file-structure.asciidoc
View file

@ -320,7 +320,7 @@ If the request does not encounter errors, you receive the following result:
} }
}, },
"ingest_pipeline" : { "ingest_pipeline" : {
"description" : "Ingest pipeline created by file structure finder", "description" : "Ingest pipeline created by text structure finder",
"processors" : [ "processors" : [
{ {
"date" : { "date" : {
@ -685,7 +685,7 @@ If the request does not encounter errors, you receive the following result:
} }
}, },
"ingest_pipeline" : { "ingest_pipeline" : {
"description" : "Ingest pipeline created by file structure finder", "description" : "Ingest pipeline created by text structure finder",
"processors" : [ "processors" : [
{ {
"csv" : { "csv" : {
@ -1578,7 +1578,7 @@ this:
} }
}, },
"ingest_pipeline" : { "ingest_pipeline" : {
"description" : "Ingest pipeline created by file structure finder", "description" : "Ingest pipeline created by text structure finder",
"processors" : [ "processors" : [
{ {
"grok" : { "grok" : {
@ -1746,7 +1746,7 @@ this:
} }
}, },
"ingest_pipeline" : { "ingest_pipeline" : {
"description" : "Ingest pipeline created by file structure finder", "description" : "Ingest pipeline created by text structure finder",
"processors" : [ "processors" : [
{ {
"grok" : { "grok" : {

99
docs/reference/text-structure/apis/find-structure.asciidoc
View file

@ -3,7 +3,7 @@
[[find-structure]] [[find-structure]]
= Find structure API = Find structure API
Finds the structure of a text file. The text file must Finds the structure of text. The text must
contain data that is suitable to be ingested into the contain data that is suitable to be ingested into the
{stack}. {stack}.
@ -30,25 +30,24 @@ is suitable for subsequent use with other {stack} functionality.
Unlike other {es} endpoints, the data that is posted to this endpoint does not Unlike other {es} endpoints, the data that is posted to this endpoint does not
need to be UTF-8 encoded and in JSON format. It must, however, be text; binary need to be UTF-8 encoded and in JSON format. It must, however, be text; binary
file formats are not currently supported. text formats are not currently supported.
The response from the API contains: The response from the API contains:
* A couple of messages from the beginning of the file. * A couple of messages from the beginning of the text.
* Statistics that reveal the most common values for all fields detected within * Statistics that reveal the most common values for all fields detected within
the file and basic numeric statistics for numeric fields. the text and basic numeric statistics for numeric fields.
* Information about the structure of the file, which is useful when you write * Information about the structure of the text, which is useful when you write
ingest configurations to index the file contents. ingest configurations to index it or similarly formatted text.
* Appropriate mappings for an {es} index, which you could use to ingest the file * Appropriate mappings for an {es} index, which you could use to ingest the text.
contents.
All this information can be calculated by the structure finder with no guidance. All this information can be calculated by the structure finder with no guidance.
However, you can optionally override some of the decisions about the file However, you can optionally override some of the decisions about the text
structure by specifying one or more query parameters. structure by specifying one or more query parameters.
Details of the output can be seen in the <<find-structure-examples,examples>>. Details of the output can be seen in the <<find-structure-examples,examples>>.
If the structure finder produces unexpected results for a particular file, If the structure finder produces unexpected results for some text,
specify the `explain` query parameter. It causes an `explanation` to appear in specify the `explain` query parameter. It causes an `explanation` to appear in
the response, which should help in determining why the returned structure was the response, which should help in determining why the returned structure was
chosen. chosen.
@ -58,7 +57,7 @@ chosen.
== {api-query-parms-title} == {api-query-parms-title}
`charset`:: `charset`::
(Optional, string) The file's character set. It must be a character set that is (Optional, string) The text's character set. It must be a character set that is
supported by the JVM that {es} uses. For example, `UTF-8`, `UTF-16LE`, supported by the JVM that {es} uses. For example, `UTF-8`, `UTF-16LE`,
`windows-1252`, or `EUC-JP`. If this parameter is not specified, the structure `windows-1252`, or `EUC-JP`. If this parameter is not specified, the structure
finder chooses an appropriate character set. finder chooses an appropriate character set.
@ -66,8 +65,8 @@ finder chooses an appropriate character set.
`column_names`:: `column_names`::
(Optional, string) If you have set `format` to `delimited`, you can specify the (Optional, string) If you have set `format` to `delimited`, you can specify the
column names in a comma-separated list. If this parameter is not specified, the column names in a comma-separated list. If this parameter is not specified, the
structure finder uses the column names from the header row of the file. If the structure finder uses the column names from the header row of the text. If the
file does not have a header role, columns are named "column1", "column2", text does not have a header role, columns are named "column1", "column2",
"column3", etc. "column3", etc.
`delimiter`:: `delimiter`::
@ -85,7 +84,7 @@ field named `explanation`, which is an array of strings that indicate how the
structure finder produced its result. The default value is `false`. structure finder produced its result. The default value is `false`.
`format`:: `format`::
(Optional, string) The high level structure of the file. Valid values are (Optional, string) The high level structure of the text. Valid values are
`ndjson`, `xml`, `delimited`, and `semi_structured_text`. By default, the API `ndjson`, `xml`, `delimited`, and `semi_structured_text`. By default, the API
chooses the format. In this default scenario, all rows must have the same number chooses the format. 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 of fields for a delimited format to be detected. If the `format` is set to
@ -95,7 +94,7 @@ of rows that have a different number of columns than the first row.
`grok_pattern`:: `grok_pattern`::
(Optional, string) If you have set `format` to `semi_structured_text`, you can (Optional, string) 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 specify a Grok pattern that is used to extract fields from every message in the
file. The name of the timestamp field in the Grok pattern must match what is text. The name of the timestamp field in the Grok pattern must match what is
specified in the `timestamp_field` parameter. If that parameter is not specified in the `timestamp_field` parameter. If that parameter is not
specified, the name of the timestamp field in the Grok pattern must match specified, the name of the timestamp field in the Grok pattern must match
"timestamp". If `grok_pattern` is not specified, the structure finder creates a "timestamp". If `grok_pattern` is not specified, the structure finder creates a
@ -103,30 +102,30 @@ Grok pattern.
`has_header_row`:: `has_header_row`::
(Optional, Boolean) If you have set `format` to `delimited`, you can use this (Optional, Boolean) If you have set `format` to `delimited`, you can use this
parameter to indicate whether the column names are in the first row of the file. parameter to indicate whether the column names are in the first row of the text.
If this parameter is not specified, the structure finder guesses based on the If this parameter is not specified, the structure finder guesses based on the
similarity of the first row of the file to other rows. similarity of the first row of the text to other rows.
`line_merge_size_limit`:: `line_merge_size_limit`::
(Optional, unsigned integer) The maximum number of characters in a message when (Optional, unsigned integer) The maximum number of characters in a message when
lines are merged to form messages while analyzing semi-structured files. The lines are merged to form messages while analyzing semi-structured text. The
default is `10000`. If you have extremely long messages you may need to increase default is `10000`. If you have extremely long messages you may need to increase
this, but be aware that this may lead to very long processing times if the way this, but be aware that this may lead to very long processing times if the way
to group lines into messages is misdetected. to group lines into messages is misdetected.
`lines_to_sample`:: `lines_to_sample`::
(Optional, unsigned integer) The number of lines to include in the structural (Optional, unsigned integer) The number of lines to include in the structural
analysis, starting from the beginning of the file. The minimum is 2; the default analysis, starting from the beginning of the text. The minimum is 2; the default
is `1000`. If the value of this parameter is greater than the number of lines in is `1000`. If the value of this parameter is greater than the number of lines in
the file, the analysis proceeds (as long as there are at least two lines in the the text, the analysis proceeds (as long as there are at least two lines in the
file) for all of the lines. text) for all of the lines.
+ +
-- --
NOTE: The number of lines and the variation of the lines affects the speed of NOTE: The number of lines and the variation of the lines affects the speed of
the analysis. For example, if you upload a log file where the first 1000 lines the analysis. For example, if you upload text where the first 1000 lines
are all variations on the same message, the analysis will find more commonality are all variations on the same message, the analysis will find more commonality
than would be seen with a bigger sample. If possible, however, it is more than would be seen with a bigger sample. If possible, however, it is more
efficient to upload a sample file with more variety in the first 1000 lines than efficient to upload sample text with more variety in the first 1000 lines than
to request analysis of 100000 lines to achieve some variety. to request analysis of 100000 lines to achieve some variety.
-- --
@ -135,7 +134,7 @@ to request analysis of 100000 lines to achieve some variety.
(Optional, string) If you have set `format` to `delimited`, you can specify the (Optional, string) If you have set `format` to `delimited`, you can specify the
character used to quote the values in each row if they contain newlines or the character used to quote the values in each row if they contain newlines or the
delimiter character. Only a single character is supported. If this parameter is delimiter character. Only a single character is supported. If this parameter is
not specified, the default value is a double quote (`"`). If your delimited file not specified, the default value is a double quote (`"`). If your delimited text
format does not use quoting, a workaround is to set this argument to a character format does not use quoting, a workaround is to set this argument to a character
that does not appear anywhere in the sample. that does not appear anywhere in the sample.
@ -152,25 +151,25 @@ expires then it will be aborted. The default value is 25 seconds.
`timestamp_field`:: `timestamp_field`::
(Optional, string) The name of the field that contains the primary timestamp of (Optional, string) The name of the field that contains the primary timestamp of
each record in the file. In particular, if the file were ingested into an index, each record in the text. In particular, if the text were ingested into an index,
this is the field that would be used to populate the `@timestamp` field. this is the field that would be used to populate the `@timestamp` field.
+ +
-- --
If the `format` is `semi_structured_text`, this field must match the name of the If the `format` is `semi_structured_text`, this field must match the name of the
appropriate extraction in the `grok_pattern`. Therefore, for semi-structured appropriate extraction in the `grok_pattern`. Therefore, for semi-structured
file formats, it is best not to specify this parameter unless `grok_pattern` is text, it is best not to specify this parameter unless `grok_pattern` is
also specified. also specified.
For structured file formats, if you specify this parameter, the field must exist For structured text, if you specify this parameter, the field must exist
within the file. within the text.
If this parameter is not specified, the structure finder makes a decision about If this parameter is not specified, the structure finder makes a decision about
which field (if any) is the primary timestamp field. For structured file which field (if any) is the primary timestamp field. For structured text,
formats, it is not compulsory to have a timestamp in the file. it is not compulsory to have a timestamp in the text.
-- --
`timestamp_format`:: `timestamp_format`::
(Optional, string) The Java time format of the timestamp field in the file. (Optional, string) The Java time format of the timestamp field in the text.
+ +
-- --
Only a subset of Java time format letter groups are supported: Only a subset of Java time format letter groups are supported:
@ -203,7 +202,7 @@ quotes. For example, `MM/dd HH.mm.ss,SSSSSS 'in' yyyy` is a valid override
format. format.
One valuable use case for this parameter is when the format is semi-structured One valuable use case for this parameter is when the format is semi-structured
text, there are multiple timestamp formats in the file, and you know which text, there are multiple timestamp formats in the text, and you know which
format corresponds to the primary timestamp, but you do not want to specify the format corresponds to the primary timestamp, but you do not want to specify the
full `grok_pattern`. Another is when the timestamp format is one that the full `grok_pattern`. Another is when the timestamp format is one that the
structure finder does not consider by default. structure finder does not consider by default.
@ -231,7 +230,7 @@ for more information about date and time format syntax.
[[find-structure-request-body]] [[find-structure-request-body]]
== {api-request-body-title} == {api-request-body-title}
The text file that you want to analyze. It must contain data that is suitable to The text that you want to analyze. It must contain data that is suitable to
be ingested into {es}. It does not need to be in JSON format and it does not be ingested into {es}. It does not need to be in JSON format and it does not
need to be UTF-8 encoded. The size is limited to the {es} HTTP receive buffer need to be UTF-8 encoded. The size is limited to the {es} HTTP receive buffer
size, which defaults to 100 Mb. size, which defaults to 100 Mb.
@ -244,7 +243,7 @@ size, which defaults to 100 Mb.
[[find-structure-example-nld-json]] [[find-structure-example-nld-json]]
=== Ingesting newline-delimited JSON === Ingesting newline-delimited JSON
Suppose you have a newline-delimited JSON file that contains information about Suppose you have newline-delimited JSON text that contains information about
some books. You can send the contents to the `find_structure` endpoint: some books. You can send the contents to the `find_structure` endpoint:
[source,console] [source,console]
@ -317,7 +316,7 @@ If the request does not encounter errors, you receive the following result:
} }
}, },
"ingest_pipeline" : { "ingest_pipeline" : {
"description" : "Ingest pipeline created by file structure finder", "description" : "Ingest pipeline created by text structure finder",
"processors" : [ "processors" : [
{ {
"date" : { "date" : {
@ -525,18 +524,18 @@ If the request does not encounter errors, you receive the following result:
} }
---- ----
// TESTRESPONSE[s/"sample_start" : ".*",/"sample_start" : "$body.sample_start",/] // TESTRESPONSE[s/"sample_start" : ".*",/"sample_start" : "$body.sample_start",/]
// The substitution is because the "file" is pre-processed by the test harness, // The substitution is because the text is pre-processed by the test harness,
// so the fields may get reordered in the JSON the endpoint sees // so the fields may get reordered in the JSON the endpoint sees
<1> `num_lines_analyzed` indicates how many lines of the file were analyzed. <1> `num_lines_analyzed` indicates how many lines of the text were analyzed.
<2> `num_messages_analyzed` indicates how many distinct messages the lines <2> `num_messages_analyzed` indicates how many distinct messages the lines
contained. For NDJSON, this value is the same as `num_lines_analyzed`. For other contained. For NDJSON, this value is the same as `num_lines_analyzed`. For other
file formats, messages can span several lines. text formats, messages can span several lines.
<3> `sample_start` reproduces the first two messages in the file verbatim. This <3> `sample_start` reproduces the first two messages in the text verbatim. This
may help diagnose parse errors or accidental uploads of the wrong file. may help diagnose parse errors or accidental uploads of the wrong text.
<4> `charset` indicates the character encoding used to parse the file. <4> `charset` indicates the character encoding used to parse the text.
<5> For UTF character encodings, `has_byte_order_marker` indicates whether the <5> For UTF character encodings, `has_byte_order_marker` indicates whether the
file begins with a byte order marker. text begins with a byte order marker.
<6> `format` is one of `ndjson`, `xml`, `delimited` or `semi_structured_text`. <6> `format` is one of `ndjson`, `xml`, `delimited` or `semi_structured_text`.
<7> The `timestamp_field` names the field considered most likely to be the <7> The `timestamp_field` names the field considered most likely to be the
primary timestamp of each document. primary timestamp of each document.
@ -544,7 +543,7 @@ primary timestamp of each document.
<9> `java_timestamp_formats` are the Java time formats recognized in the time <9> `java_timestamp_formats` are the Java time formats recognized in the time
fields. {es} mappings and ingest pipelines use this format. fields. {es} mappings and ingest pipelines use this format.
<10> If a timestamp format is detected that does not include a timezone, <10> If a timestamp format is detected that does not include a timezone,
`need_client_timezone` will be `true`. The server that parses the file must `need_client_timezone` will be `true`. The server that parses the text must
therefore be told the correct timezone by the client. therefore be told the correct timezone by the client.
<11> `mappings` contains some suitable mappings for an index into which the data <11> `mappings` contains some suitable mappings for an index into which the data
could be ingested. In this case, the `release_date` field has been given a could be ingested. In this case, the `release_date` field has been given a
@ -683,7 +682,7 @@ If the request does not encounter errors, you receive the following result:
} }
}, },
"ingest_pipeline" : { "ingest_pipeline" : {
"description" : "Ingest pipeline created by file structure finder", "description" : "Ingest pipeline created by text structure finder",
"processors" : [ "processors" : [
{ {
"csv" : { "csv" : {
@ -1463,10 +1462,10 @@ lists the column names in the order they appear in the sample.
<4> `has_header_row` indicates that for this sample the column names were in <4> `has_header_row` indicates that for this sample the column names were in
the first row of the sample. (If they hadn't been then it would have been a good the first row of the sample. (If they hadn't been then it would have been a good
idea to specify them in the `column_names` query parameter.) idea to specify them in the `column_names` query parameter.)
<5> The `delimiter` for this sample is a comma, as it's a CSV file. <5> The `delimiter` for this sample is a comma, as it's CSV formatted text.
<6> The `quote` character is the default double quote. (The structure finder <6> The `quote` character is the default double quote. (The structure finder
does not attempt to deduce any other quote character, so if you have a delimited does not attempt to deduce any other quote character, so if you have delimited
file that's quoted with some other character you must specify it using the text that's quoted with some other character you must specify it using the
`quote` query parameter.) `quote` query parameter.)
<7> The `timestamp_field` has been chosen to be `tpep_pickup_datetime`. <7> The `timestamp_field` has been chosen to be `tpep_pickup_datetime`.
`tpep_dropoff_datetime` would work just as well, but `tpep_pickup_datetime` was `tpep_dropoff_datetime` would work just as well, but `tpep_pickup_datetime` was
@ -1577,7 +1576,7 @@ this:
} }
}, },
"ingest_pipeline" : { "ingest_pipeline" : {
"description" : "Ingest pipeline created by file structure finder", "description" : "Ingest pipeline created by text structure finder",
"processors" : [ "processors" : [
{ {
"grok" : { "grok" : {
@ -1693,7 +1692,7 @@ calculate `field_stats` for your additional fields.
In the case of the {es} log a more complete Grok pattern is In the case of the {es} log a more complete Grok pattern is
`\[%{TIMESTAMP_ISO8601:timestamp}\]\[%{LOGLEVEL:loglevel} *\]\[%{JAVACLASS:class} *\] \[%{HOSTNAME:node}\] %{JAVALOGMESSAGE:message}`. `\[%{TIMESTAMP_ISO8601:timestamp}\]\[%{LOGLEVEL:loglevel} *\]\[%{JAVACLASS:class} *\] \[%{HOSTNAME:node}\] %{JAVALOGMESSAGE:message}`.
You can analyze the same log file again, submitting this `grok_pattern` as a You can analyze the same text again, submitting this `grok_pattern` as a
query parameter (appropriately URL escaped): query parameter (appropriately URL escaped):
[source,js] [source,js]
@ -1745,7 +1744,7 @@ this:
} }
}, },
"ingest_pipeline" : { "ingest_pipeline" : {
"description" : "Ingest pipeline created by file structure finder", "description" : "Ingest pipeline created by text structure finder",
"processors" : [ "processors" : [
{ {
"grok" : { "grok" : {

4
x-pack/plugin/src/test/resources/rest-api-spec/test/text_structure/find_file_structure.yml
View file

@ -40,7 +40,7 @@ setup:
- match: { mappings.properties.sourcetype.type: keyword } - match: { mappings.properties.sourcetype.type: keyword }
- match: { mappings.properties.time.type: date } - match: { mappings.properties.time.type: date }
- match: { mappings.properties.time.format: epoch_second } - match: { mappings.properties.time.format: epoch_second }
- match: { ingest_pipeline.description: "Ingest pipeline created by file structure finder" } - match: { ingest_pipeline.description: "Ingest pipeline created by text structure finder" }
- match: { ingest_pipeline.processors.0.date.field: time } - match: { ingest_pipeline.processors.0.date.field: time }
- match: { ingest_pipeline.processors.0.date.formats.0: UNIX } - match: { ingest_pipeline.processors.0.date.formats.0: UNIX }
- match: { field_stats.airline.count: 3 } - match: { field_stats.airline.count: 3 }
@ -101,7 +101,7 @@ setup:
- match: { mappings.properties.sourcetype.type: keyword } - match: { mappings.properties.sourcetype.type: keyword }
- match: { mappings.properties.time.type: date } - match: { mappings.properties.time.type: date }
- match: { mappings.properties.time.format: epoch_second } - match: { mappings.properties.time.format: epoch_second }
- match: { ingest_pipeline.description: "Ingest pipeline created by file structure finder" } - match: { ingest_pipeline.description: "Ingest pipeline created by text structure finder" }
- match: { ingest_pipeline.processors.0.date.field: time } - match: { ingest_pipeline.processors.0.date.field: time }
- match: { ingest_pipeline.processors.0.date.formats.0: UNIX } - match: { ingest_pipeline.processors.0.date.formats.0: UNIX }
- match: { field_stats.airline.count: 3 } - match: { field_stats.airline.count: 3 }

2
x-pack/plugin/text-structure/src/main/java/org/elasticsearch/xpack/textstructure/structurefinder/FileStructureUtils.java
View file

@ -485,7 +485,7 @@ public final class FileStructureUtils {
} }
Map<String, Object> pipeline = new LinkedHashMap<>(); Map<String, Object> pipeline = new LinkedHashMap<>();
pipeline.put(Pipeline.DESCRIPTION_KEY, "Ingest pipeline created by file structure finder"); pipeline.put(Pipeline.DESCRIPTION_KEY, "Ingest pipeline created by text structure finder");
List<Map<String, Object>> processors = new ArrayList<>(); List<Map<String, Object>> processors = new ArrayList<>();

12
x-pack/plugin/text-structure/src/test/java/org/elasticsearch/xpack/textstructure/structurefinder/TextStructureUtilsTests.java
View file

@ -458,7 +458,7 @@ public class TextStructureUtilsTests extends TextStructureTestCase {
); );
assertNotNull(pipeline); assertNotNull(pipeline);
assertEquals("Ingest pipeline created by file structure finder", pipeline.remove("description")); assertEquals("Ingest pipeline created by text structure finder", pipeline.remove("description"));
List<Map<String, Object>> processors = (List<Map<String, Object>>) pipeline.remove("processors"); List<Map<String, Object>> processors = (List<Map<String, Object>>) pipeline.remove("processors");
assertNotNull(processors); assertNotNull(processors);
@ -496,7 +496,7 @@ public class TextStructureUtilsTests extends TextStructureTestCase {
); );
assertNotNull(pipeline); assertNotNull(pipeline);
assertEquals("Ingest pipeline created by file structure finder", pipeline.remove("description")); assertEquals("Ingest pipeline created by text structure finder", pipeline.remove("description"));
List<Map<String, Object>> processors = (List<Map<String, Object>>) pipeline.remove("processors"); List<Map<String, Object>> processors = (List<Map<String, Object>>) pipeline.remove("processors");
assertNotNull(processors); assertNotNull(processors);
@ -535,7 +535,7 @@ public class TextStructureUtilsTests extends TextStructureTestCase {
); );
assertNotNull(pipeline); assertNotNull(pipeline);
assertEquals("Ingest pipeline created by file structure finder", pipeline.remove("description")); assertEquals("Ingest pipeline created by text structure finder", pipeline.remove("description"));
List<Map<String, Object>> processors = (List<Map<String, Object>>) pipeline.remove("processors"); List<Map<String, Object>> processors = (List<Map<String, Object>>) pipeline.remove("processors");
assertNotNull(processors); assertNotNull(processors);
@ -575,7 +575,7 @@ public class TextStructureUtilsTests extends TextStructureTestCase {
); );
assertNotNull(pipeline); assertNotNull(pipeline);
assertEquals("Ingest pipeline created by file structure finder", pipeline.remove("description")); assertEquals("Ingest pipeline created by text structure finder", pipeline.remove("description"));
List<Map<String, Object>> processors = (List<Map<String, Object>>) pipeline.remove("processors"); List<Map<String, Object>> processors = (List<Map<String, Object>>) pipeline.remove("processors");
assertNotNull(processors); assertNotNull(processors);
@ -628,7 +628,7 @@ public class TextStructureUtilsTests extends TextStructureTestCase {
); );
assertNotNull(pipeline); assertNotNull(pipeline);
assertEquals("Ingest pipeline created by file structure finder", pipeline.remove("description")); assertEquals("Ingest pipeline created by text structure finder", pipeline.remove("description"));
List<Map<String, Object>> processors = (List<Map<String, Object>>) pipeline.remove("processors"); List<Map<String, Object>> processors = (List<Map<String, Object>>) pipeline.remove("processors");
assertNotNull(processors); assertNotNull(processors);
@ -683,7 +683,7 @@ public class TextStructureUtilsTests extends TextStructureTestCase {
); );
assertNotNull(pipeline); assertNotNull(pipeline);
assertEquals("Ingest pipeline created by file structure finder", pipeline.remove("description")); assertEquals("Ingest pipeline created by text structure finder", pipeline.remove("description"));
List<Map<String, Object>> processors = (List<Map<String, Object>>) pipeline.remove("processors"); List<Map<String, Object>> processors = (List<Map<String, Object>>) pipeline.remove("processors");
assertNotNull(processors); assertNotNull(processors);