Which transformer is designed for performing ad-hoc queries across features from non-database formats?

• A. Filter
• B. InlineQuerier
• C. FeatureJoiner
• D. DatabaseJoiner

Answer: (B)

Ad-hoc SQL-style querying across in-memory features is the idea here. The InlineQuerier lets you write an inline SQL-like statement that can operate on features from multiple inputs within the workspace, even if those features come from non-database formats like CSVs, shapefiles, or other file types. It effectively treats the incoming feature streams as tables you can query, join, filter, or aggregate on the fly without needing a database. That makes it the best fit for performing ad-hoc queries across features from non-database formats.

In contrast, a Filter evaluates a condition on each feature independently and doesn’t combine or query across features. A FeatureJoiner merges features from different streams based on matching attributes but doesn’t provide an ad-hoc SQL interface. A DatabaseJoiner relies on a database to perform the join, which isn’t designed for ad-hoc workspace-wide queries on non-database data.