rename "Table Input" to "SQL Input" or "Query Input"

[bamaer]

The Table Input transform has a history of about 2 decades, but the transform's name doesn't really match its function.

Instead of reading data from a single table, the transform reads data from a SQL query that in a lot (the majority?) of cases spans multiple tables.

This transform's name may be confusing for new users, but renaming the transform could confuse long-term Apache Hop users and users coming over from PDI/Kettle.

A potential rename of the transform will need to keep the TableInput XML serialization as is for compatibility, so this will only have an impact in Hop Gui. There won't be any impact on existing pipelines.

What do you think? Choose one of the options below or add your own.

[hansva]

I would go for query input, depending on the JDBC driver it can be Not Only SQL (see what I did there?)

[xdelox]

IMHO the word "query" is too generic and might cause misunderstanding, since there are tons of query languages besides SQL and, therefore, people might assume it also supports one or more of them, like GraphQL, Cypher, etc.
So I voted for "SQL Input" just for a matter of clarity.

[smalos]

While not all databases use SQL, most utilize some form of query mechanism to access data. As a result, the name "SQL Input" may not be the most accurate.

More generic alternatives:

• Query Input
• Database Input