feat(sink): support geospatial for redis sink #20402
Open
+482
−74
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
in this pr, we support geospatial type for redis sink
https://redis.io/glossary/geospatial-indexing/
Checklist
Documentation
We can use geospatial like
then we can get it in redis like
redis_value_type
must be set tostring
andgeospatial
, default isstring
if
redis_value_type
is set tostring
, we must setkey_format
andvalue_fomat
(Consistent with previous behavior)if
redis_value_type
is set togeospatial
, we must setkey_format
,longitude
,latitude
andmember
The meaning of
key_format
is consistent withredis_value_type = string
The
longitude
is the column name of rw, the datatype must be float, real or varcharThe
latitude
is the column name of rw, the datatype must be float, real or varcharThe
member
is the column name of rw, the datatype must be varchar, and must beprimary_key