Thank you, Francesco
> On 3 Feb 2022, at 18:21, Francesco Guardiani wrote:
>
> Hi,
>
> I think the more stable option would be the first one, as it also gives you
> more flexibility. Reading the row as string and then parsing it in a query
> definitely costs more, and makes less straightforwa
Hi,
I think the more stable option would be the first one, as it also gives you
more flexibility. Reading the row as string and then parsing it in a query
definitely costs more, and makes less straightforward to use the other
Schema features of table, such as watermark definition, primary keys, et
Hi,
I’m using the Table / SQL API.
I have a stream of strings, where each message contains several json strings
separated by "\n”.
For example:
{“timestamp”: “2021-01-01T00:00:00”, person: {“name”: “Vasya”}}\n
{“timestamp”: “2021-01-01T01:00:00”, person: {“name”: “Max” }}
I would like to sp