Conversation
| * Leverages the same underlying wire format as strings until | ||
| * native JSON serialization support is available server-side. | ||
| */ | ||
| class ColumnJson : public ColumnString { |
There was a problem hiding this comment.
We can create a feature request to support json column to avoid this backward compatibility issue in future
@yuzifeng1984 may you take a look if we can support json native type in this client.
@sofiane-soufi btw, may i ask what's your current use cases you need json type in this client ?
There was a problem hiding this comment.
maybe it is time to get this merged https://github.com/timeplus-io/timeplus-cpp/pull/23/changes
There was a problem hiding this comment.
If I recall correctly, some streams had JSON column types, and querying them from the client would result in errors and no results due to missing JSON column support.
There was a problem hiding this comment.
The previous json PR 23 is for old protocol and seems not working with current timeplus. I will be looking at how to fix the protocol. Using string column to send is fine while may have problem in decoding server json column data.
There was a problem hiding this comment.
One quick solution is to set output_format_native_write_json_as_string = true in query and load json column as string.
In future, we will also need to add variant and dynamic column to fully support json
3 participants
No description provided.