UN-3569 [FIX] Pass enable_header_mapping through agentic_params - #2268
Open
harini-venkataraman wants to merge 4 commits into
Open
UN-3569 [FIX] Pass enable_header_mapping through agentic_params#2268harini-venkataraman wants to merge 4 commits into
harini-venkataraman wants to merge 4 commits into
Conversation
The cloud backend stores enable_header_mapping in
tool_metadata["agentic_table_settings"], but structure_tool_task.py
never forwarded it to the executor. The executor already reads
params.get("enable_header_mapping", False), so this one-line addition
closes the gap for API/ETL/workflow runs.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
|
| Filename | Overview |
|---|---|
| workers/file_processing/structure_tool_task.py | Forwards the header-mapping toggle alongside the existing agentic-table execution parameters with a backward-compatible default. |
Reviews (3): Last reviewed commit: "Merge branch 'main' into fix/enable-head..." | Re-trigger Greptile
Signed-off-by: harini-venkataraman <115449948+harini-venkataraman@users.noreply.github.com>
for more information, see https://pre-commit.ci
Deepak-Kesavan
approved these changes
Sep 1, 2026
|
Contributor
Unstract test resultsPer-group results
Critical paths
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The cloud backend stores
enable_header_mappingintool_metadata["agentic_table_settings"], butstructure_tool_task.pynever forwarded it to the executor. The executor already readsparams.get("enable_header_mapping", False), so this one-line addition closes the gap for API/ETL/workflow runs.What
enable_header_mappingsetting fromagentic_table_settingsintoagentic_paramsinstructure_tool_task.pyWhy
enable_header_mappingtoggle stored in the DB was never passed through to the executor, making it inert for API/ETL/workflow runs despite being configurable in the cloud UIHow
"enable_header_mapping": at_settings.get("enable_header_mapping", False)to theagentic_paramsdict in_execute_structure_tool_impl(), alongside the existinggroup_keyentryparams.get("enable_header_mapping", False), so no downstream changes are neededCan this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)
False, which matches the executor's existing default. Existing workflows that don't set this flag will behave identically.Database Migrations
Env Config
Relevant Docs
Related Issues or PRs
Dependencies Versions
Notes on Testing
Falsepreserves backward compatibility)enable_header_mappingtoggle in the cloud UI, run an agentic table extraction, and confirm header mapping is appliedScreenshots
Checklist