The current ETL search functionality is useful, but it becomes limiting in complex pipelines where column names include prefixes and suffixes. In large-scale ETLs with multiple datasets, joins, and transformations, locating specific columns during logic updates is time-consuming and inefficient.
Requesting a wildcard-based column search (e.g., searching City returns ArrivalCity, DepartureCity, OriginCity, DestinationCity) would significantly improve usability.
This enhancement would make column discovery faster, reduce errors during changes, and greatly improve productivity when working with complex ETL workflows.
