| Deprecation |
The following GraphQL queries and mutations for interacting with
parsers are deprecated and scheduled for removal in version
1.142.
Deprecated createParser mutation
is replaced by
createParserV2(). The
differences between the old and new mutation are:
testData input field is replaced by
testCases, which can contain more
data than the old tests could. This includes adding
assertions to the output of a test.
These assertions are not
displayed in the UI yet. To emulate the old
API, you can take the old test string and put it in the
ParserTestEventInput inside the
ParserTestCaseInput, and they will
behave the same as before.
fieldsToBeRemovedBeforeParsing can
now be specified as part of the parser creation.
force field is renamed to
allowOverwritingExistingParser.
sourceCode field is renamed to
script.
tagFields field is renamed to
fieldsToTag.
languageVersion is no longer an
enum, but a
LanguageVersionInputType instead.
The mutation returns a Parser,
instead of a Parser wrapped in an
object.
The mutation fails when a parser has more than 2,000
test cases, or the test input in a single test case
exceeds 40,000 characters.
Deprecated removeParser mutation
is replaced by deleteParser. The
difference between the old and new mutation is:
Deprecated testParser mutation is
replaced by
testParserV2(). The
differences between the old and new mutation are:
The test cases are now structured types, instead of just
being strings. To emulate the old API, take the test
string and put it in the
ParserTestEventInput inside the
ParserTestCaseInput, and they
will behave the same as before.
The new test cases can contain assertions about the
contents of the output.
The mutation output is significantly different from
before, as it provides more detailed information on how
a test case has failed.
The mutation now accepts both a language version and
list of fields to be removed before parsing.
The parserScript field is renamed
to script.
The tagFields field is renamed to
fieldsToTag.
Deprecated updateParser mutation
is replaced by
updateParserV2(). The
differences between the old and new mutation are:
testData input field is replaced by
testCases, which can contain more
data than the old tests could. This includes adding
assertions to the output of a test.
These assertions are not
displayed in the UI yet. To emulate the old
API, you can take the old test string and put it in the
`ParserTestEventInput` inside the `ParserTestCaseInput`,
and they will behave the same as before.
sourceCode field, used to updating
the parser script, is changed to the
script field, which takes a
UpdateParserScriptInput object. This
updates the parser script and the language version
together.
tagFields field is renamed to
fieldsToTag.
The languageVersion is located
inside the UpdateParserScriptInput object,
and is no longer an enum, but a
LanguageVersionInputType instead.
The repositoryName and
id fields are now correctly marked
as mandatory in the schema. Previously this wasn't the
case, even though the mutation would fail without them.
The mutation returns a Parser,
instead of a Parser wrapped in an
object.
The old mutation had a bug where it would overwrite the
languageVersion with a default
value in some cases, which is fixed in the new one.
The mutation fails when a parser has more than 2,000
test cases, or the test input in a single test case
exceeds 40,000 characters.
On the Parser type:
testData field is deprecated and
replaced by testCases.
sourceCode field is deprecated and
replaced by script.
tagFields field is deprecated and
replaced by fieldsToTag.
| GraphQL API | 1.129.0 | 1.141.0 |
| Deprecation |
The any argument to the
type parameter of
sort() and table() has
been deprecated and will be removed in version 1.142.
Warnings prompts will be shown in queries that fall into either
of these two cases:
If you are explicitly supplying an
any argument,
please either simply remove both the parameter and the
argument, for example change sort(...,
type=any) to sort(...) or
supply the argument for
type that
corresponds to your data.
If you are sorting hexadecimal values by their equivalent
numerical values, please change the argument of
type parameter to
hex e.g.
sort(..., type=hex).
In all other cases, no action is needed.
The new default value for sort() and
table() will be
number. Both functions
will fall back to lexicographical ordering for values that
cannot be understood as the provided argument for
type.
| Functions | 1.125.0 | 1.141.0 |
| Advanced Warning |
The Launcher Script script for starting
LogScale will be modified to change the way CPU core usage can
be configured. The -XX:ActiveProcessorCount=n
command-line option will be ignored if set. Users that need to
configure the core count manually should set
CORES=n environmant variable instead. This will
cause the launcher to configure both LogScale and the JVM
properly.
This change is scheduled for 1.148.0.
| Installation and Deployment | 1.132.0 | 1.148.0 |
| Deprecation |
The following API endpoints are deprecated and marked for
removal in 1.148.0:
POST
/api/v1/clusterconfig/kafka-queues/partition-assignment
GET
/api/v1/clusterconfig/kafka-queues/partition-assignment
POST
/api/v1/clusterconfig/kafka-queues/partition-assignment/set-replication-defaults
The deprecated methods are used for viewing and changing the
partition assignment in Kafka for the ingest queue.
Administrators should use Kafka's own tools for editing
partition assignments instead, such as the
bin/kafka-reassign-partitions.sh and
bin/kafka-topics.sh scripts that ship with
the Kafka install.
| API | 1.132.0 | 1.148.0 |
| Deprecation |
We are deprecating the
humio/kafka and
humio/zookeeper Docker
images due to low use. The planned final release for these
images will be with LogScale 1.148.0.
Better alternatives are available going forward. We recommend
the following:
If you still require
humio/kafka or
humio/zookeeper for
needs that cannot be covered by these alternatives, please
contact Support and
share your concerns.
| Installation and Deployment | 1.123.0 | 1.148.0 |
| Deprecation |
The HUMIO_JVM_ARGS environment variable in the
Launcher Script script will be removed
in 1.154.0.
The variable existed for migration from older deployments where
the launcher script was not available. The launcher script
replaces the need for manually setting parameters in this
variable, so the use of this variable is no longer required.
Using the launcher script is now the recommended method of
launching LogScale. For more details on the launcher script, see
Launcher Script. Clusters that
still set this configuration should migrate to the other
variables described at
Override garbage collection configuration within the launcher script.
| Installation and Deployment | 1.132.0 | 1.154.0 |
