Skip to content

Commit 82b1ca0

Browse files
authored
Merge pull request ClickHouse#80689 from ClickHouse/Blargian-patch-14
Docs: fix badly formatted table
2 parents 7f9166e + 1551a6a commit 82b1ca0

File tree

1 file changed

+2
-0
lines changed
  • docs/en/sql-reference/statements/select

1 file changed

+2
-0
lines changed

docs/en/sql-reference/statements/select/join.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -317,6 +317,7 @@ USING (equi_column1, ... equi_columnN, asof_column)
317317

318318
For example, consider the following tables:
319319

320+
```text
320321
table_1 table_2
321322
event | ev_time | user_id event | ev_time | user_id
322323
----------|---------|---------- ----------|---------|----------
@@ -325,6 +326,7 @@ For example, consider the following tables:
325326
... event_2_2 | 12:30 | 42
326327
event_1_2 | 13:00 | 42 event_2_3 | 13:00 | 42
327328
... ...
329+
```
328330

329331
`ASOF JOIN` can take the timestamp of a user event from `table_1` and find an event in `table_2` where the timestamp is closest to the timestamp of the event from `table_1` corresponding to the closest match condition. Equal timestamp values are the closest if available. Here, the `user_id` column can be used for joining on equality and the `ev_time` column can be used for joining on the closest match. In our example, `event_1_1` can be joined with `event_2_1` and `event_1_2` can be joined with `event_2_3`, but `event_2_2` can't be joined.
330332

0 commit comments

Comments
 (0)