jerrinot
commented
2 years ago Just a note I do not want to forget.
There was one more hiccup after implementing pg_catalog.pg_tables: I created a target table in QuestDB called decodable, but Decodable complained it could not find a table public.decodable in a target Postgres server.
After I created a table called literally "public.decodable" then Decodable was happy. It inserts entries into a table called just "decodable". It appears table "public.decodable" is just used for a check during the initial sink creation. Perhaps that's something we could improve together with the Decodable team.
Is your feature request related to a problem?
When adding QuestDB as a Postgres Sink into decodable.co I'm getting this error:
Invalid connection. Reason: ERROR: table does not exist [name=pg_catalog.pg_tables]Apparently, this table is not implemented.
Describe the solution you'd like.
Implement this table so QuestDB can be used as a Sink in Decodable.
Describe alternatives you've considered.
Implement a custom QuestDB sink for Decodable.
Additional context.
Decodable is a data integration platform, I believe it's based on Apache Flink, but it embraces SQL as a first class citizen. While in Flink, it's more of afterthought.