You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -2405,40 +2403,38 @@ Field definition for use with SQLiteLookup in lookup joins.
2405
2403
2406
2404
Enables advanced SQL queries with support for parameter substitution from message columns, allowing dynamic lookups.
2407
2405
2408
-
The `sdf.lookup_join``on` parameter isnot used in the query itself, but is important for cache management. When caching is enabled, the query is executed once per TTLfor each unique target key.
2406
+
The `sdf.join_lookup``on` parameter isnot used in the query itself, but is important for cache management. When caching is enabled, the query is executed once per TTLfor each unique target key.
2409
2407
2410
2408
Query results are returned as tuples of values, without additional deserialization.
2411
2409
2412
2410
**Example**:
2413
2411
2412
+
2414
2413
```python
2415
2414
lookup= SQLiteLookup(path="/path/to/db.sqlite")
2416
2415
2417
-
# Select all columns from the first row of `my_table` where `col2` matches the value of `field1` in the message.
2418
-
fields= {
2419
-
"my_field": SQLiteLookupQueryField("SELECT * FROM my_table WHERE col2 = :field1")}
2416
+
# Select all columns from the first row of `my_table` where `col2` matches the value of `field1` in the message.
2417
+
fields= {"my_field": SQLiteLookupQueryField("SELECT * FROM my_table WHERE col2 = :field1")}
2420
2418
2421
-
# After the lookup, the `my_field` column in the message will contain:
@@ -2995,7 +2991,7 @@ Field definition for use with SQLiteLookup in lookup joins.
2995
2991
2996
2992
Enables advanced SQL queries with support for parameter substitution from message columns, allowing dynamic lookups.
2997
2993
2998
-
The `sdf.lookup_join` `on` parameter is not used in the query itself, but is important for cache management. When caching is enabled, the query is executed once per TTL for each unique target key.
2994
+
The `sdf.join_lookup` `on` parameter is not used in the query itself, but is important for cache management. When caching is enabled, the query is executed once per TTL for each unique target key.
2999
2995
3000
2996
Query results are returned as tuples of values, without additional deserialization.
3001
2997
@@ -3004,31 +3000,28 @@ Example:
3004
3000
```python
3005
3001
lookup = SQLiteLookup(path="/path/to/db.sqlite")
3006
3002
3007
-
# Select all columns from the first row of `my_table` where `col2` matches the value of `field1` in the message.
3008
-
fields = {
3009
-
"my_field": SQLiteLookupQueryField("SELECT * FROM my_table WHERE col2 = :field1")}
3003
+
# Select all columns from the first row of `my_table` where `col2` matches the value of `field1` in the message.
3004
+
fields = {"my_field": SQLiteLookupQueryField("SELECT * FROM my_table WHERE col2 = :field1")}
3010
3005
3011
-
# After the lookup, the `my_field` column in the message will contain:
0 commit comments