Re: Please help with Flink + InfluxDB

2025-01-30 Thread Siva Krishna
Yes Nix. I can confirm that I am able to connect to InfluxDB from Flink(taskmanager). URL="http://influxdb:8086"; And also, I tried with below from inside Flink(taskmanager) container and that also worked. curl influxdb:8086 Siva. On Thu, Jan 30, 2025 at 4:50 PM Nikola Milutinovic wrote: > > Hi.

Unsubscribe

2025-01-30 Thread Muazim Wani
Unsubscribe

Re: Please help with Flink + InfluxDB

2025-01-30 Thread Nikola Milutinovic
Hi. First of all, can you verify your Docker compose InfluxDB is working, is it accepting connections? Can you connect to it from outside Docker Compose? When connecting from Flink, I hope you are referencing the service name as a host, because that is how Docker Compose works. It is a common

Re: Dynamic Kafka Properties

2025-01-30 Thread Salva Alcántara
By looking at: https://github.com/apache/flink-connector-kafka/pull/20 where the "setRackIdSupplier" setter for the kafka source builder was introduced, I guess one could take a more general approach and instead consider overrides for: "setProperty" "setProperties" which receive a supplier for

Re: Please help with Flink + InfluxDB

2025-01-30 Thread Nikola Milutinovic
Hi Siva. What is the InfluxDB URL you are using? I assume it is something like “influxdb://influxdb:8086/…”. If it is “localhost:8086…” that would be a problem. Do you see a connection on InfluxDB? Anything in the logs? Anything in the logs of Job Mnager? Nix, From: Siva Krishna Date: Thurs

Re: Performance problem with FlinkSQL

2025-01-30 Thread Pedro Mázala
> The average output rate needed to avoid lag after filtering messages should be around 60K messages per second. I’ve been testing different configurations of parallelism, slots and pods (everything runs on Kubernetes), but I’m far from achieving those numbers. How are you partitioning your query?

Re: Resolving Table using Java API

2025-01-30 Thread Pedro Mázala
In almost every case, the “table should be resolved” error from FlinkCatalog.createTable() means that the table identifier you are passing is either invalid, incomplete, or the catalog can’t figure out where the table is supposed to live. Most commonly, it’s because: The database (namespace) is emp

Re: Please help with Flink + InfluxDB

2025-01-30 Thread Siva Krishna
Hi Nix, Thank you for your reply. I have small update. For trial/error, I have signed in InfluxDB cloud. This same code is working and data is being save in the cloud. So, I am guessing there might issue with my 'docker compose', which is why the data is not being saved in local(docker InfluxDB). M