|
2 | 2 |
|
3 | 3 | When working with a [`DataFrame`](DataFrame.md), the most convenient and reliable way |
4 | 4 | to access its columns — including for operations and retrieving column values |
5 | | -in row expressions — is through auto-generated extension properties. |
| 5 | +in row expressions — is through *auto-generated extension properties*. |
6 | 6 | They are generated based on a [dataframe schema](schemas.md), |
7 | 7 | with the name and type of properties inferred from the name and type of the corresponding columns. |
8 | 8 | It also works for all types of hierarchical dataframes. |
9 | 9 |
|
10 | 10 | > The behavior of data schema generation differs between the |
11 | 11 | > [Compiler Plugin](Compiler-Plugin.md) and [Kotlin Notebook](gettingStartedKotlinNotebook.md). |
12 | 12 | > |
13 | | -> * In **Kotlin Notebook**, a schema is generated *only after cell execution* for |
| 13 | +> * In **Kotlin Notebook**, a schema is generated **only after cell execution** for |
14 | 14 | > `DataFrame` variables defined within that cell. |
15 | | -> * With the **Compiler Plugin**, a new schema is generated *after every operation* |
| 15 | +> * With the **Compiler Plugin**, a new schema is generated **after every operation** |
16 | 16 | > — but support for all operations is still in progress. |
17 | | -> Retrieving the schema for `DataFrame` read from a file or URL is *not yet supported* either. |
| 17 | +> Retrieving the schema for `DataFrame` read from a file or URL is **not yet supported** either. |
18 | 18 | > |
19 | 19 | > This behavior may change in future releases. See the [example](#example) below that demonstrates these differences. |
20 | 20 | {style="warning"} |
@@ -64,7 +64,7 @@ Read the [`DataFrame`](DataFrame.md) from the CSV file: |
64 | 64 | val df = DataFrame.readCsv("example.csv") |
65 | 65 | ``` |
66 | 66 |
|
67 | | -*After cell execution* data schema and extensions for this `DataFrame` will be generated |
| 67 | +**After cell execution** data schema and extensions for this `DataFrame` will be generated |
68 | 68 | so you can use extensions for accessing columns, |
69 | 69 | using it in operations inside the [Column Selector DSL](ColumnSelectors.md) |
70 | 70 | and [DataRow API](DataRow.md): |
|
0 commit comments