Introduce a TQL2-only mode #4840
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dominiklohmann
added
feature
dominiklohmann
force-pushed
the
topic/tql2-only-mode
branch
from
0cb4a38 to
ef0a694
Compare
jachris
approved these changes
Dec 5, 2024
dominiklohmann
force-pushed
the
topic/tql2-only-mode
branch
from
08bdd6b to
0de3ba6
Compare
dominiklohmann
force-pushed
the
topic/tql2-only-mode
branch
4 times, most recently
from
92c2a9a to
dacfca6
Compare
dominiklohmann
force-pushed
the
topic/tql2-only-mode
branch
from
dacfca6 to
7a4aa64
Compare
This reverts commit b142f72.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a new TQL2-only mode for nodes. To enable it, either set
TENZIR_TQL2=truein your environment, settenzir.tql2: truein your configuration file, or start the node viatenzir-node --tql2.When TQL2-only mode is enabled, all pipelines will be in TQL2. Using TQL1 is only possible through the
legacyoperator, or in places where TQL2 is not yet supported, for example in user-defined operators.The plan is to phase out TQL1 in three stages:
legacyfor TQL1 (Q1 2025)legacyand everything related to TQL1 (later in 2025)