Hi Kenn,
Thank you for replying back to my email.
I was under the same impression about Calcite. But I wrote a test on
Calcite 1.28 too. It is working without issue that I see on BEAM
Here is my test case. If you want you can also run on Calcite. Please put
under core/src/test/resources/sql as t
+d...@beam.apache.org
I tried reproducing this but was not successful, the output schema was as
expected. I added the following to BeamSqlMultipleSchemasTest.java at head.
(I did discover that PAssert.that(result).containsInAnyOrder(output)
doesn't validate column names however.)
@Test
publ
Adding the Beam user list in case other folks might run into similar issues.
Hi Phani,
PulsarMessage's getMessageRecord() returns the message from the Pulsar
client itself. I haven't really used Pulsar myself but it looks like under
normal circumstances the Pulsar client would handle the translat
Hi Andrew,
Thanks for writing a test for this use case. Without Where clause it works
as expected on our test cases also too. Please add where clause on second
select. With the below query it does not return column names. I tested on
my local also.
WITH tempTable (id, v) AS (SELECT f_int as id, f
