Skip to content
Permalink
Browse files

Fix small typo (#1873)

* Fix small typo

* follow comment
  • Loading branch information
tonyyang-svail committed Mar 25, 2020
1 parent f7d266c commit c4bb37edf8a474932dd23e899b27f7ff122eba7c
Showing with 3 additions and 3 deletions.
  1. +3 −3 docs/designs/data_transform.md
@@ -66,16 +66,16 @@ SELECT * FROM new_plates TO PREDICT price USING a_model;
If the user doesn't want normalization, but the raw value, as the input, she could write the following.

```sql
SELECT * FROM new_plate TO PREDICT price USING a_model COLUMN size
SELECT * FROM new_plates TO PREDICT price USING a_model COLUMN size
```

Or, if she wants standardization instead of normalization, she could write the following.

```sql
SELECT * FROM new_plate TO PREDICT price USING a_model COLUMN standardize(size)
SELECT * FROM new_plates TO PREDICT price USING a_model COLUMN standardize(size)
```

How if the table new_plate doesn't have the field used to train the model? How if there is no field named `size`, but a field `diameter`. We should allow users to use the latter as well.
How if the table new_plates doesn't have the field used to train the model? How if there is no field named `size`, but a field `diameter`. We should allow users to use the latter as well.

```sql
SELECT * FROM new_plates TO PREDICT price USING a_model COLUM normalize(diameter)

0 comments on commit c4bb37e

Please sign in to comment.
You can’t perform that action at this time.