We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Let us start with a very simple case.
Suppose that we want to regress the salary with respect the age and the gender, we'd train a model using the following SQL statement:
SELECT age, gender, salary FROM engineer_info, engineer_payment WHERE engineer_info.id = engieer_payment.id TRAIN DNNRegressor WITH hidden_units = [10, 30] COLUMN clip(age, 18, 65), gender, cross(clip(age, 18, 65), gender) LABEL salary INTO my_first_model ;
This generates a table my_first_model, which encode
my_first_model
We see that we need both SELECT to specify the fields to retrieve and COLUMN for fields-to-feature mapping.
Given this model, we can infer the salary for any other group of people. For example, the execution of the following statement
SELECT id, age, sex FROM another_company_employee_info INFER my_first_model COLUMN age, vocab(sex, ["Female", "Male"]) LABEL expected_salary INTO a_new_table
should generate a new table a_new_table with fields:
a_new_table
Again, we need COLUMN in addition to SELECT to map different field names, and even field values, to the features acceptable by the model.