Client configuration string: Consider trailing semicolon to be optional #4390
Labels
Compatibility
Compatibility with third-party tools and services
ILP
Issues or changes relating to Influx Line Protocol
Java
Improvements that update Java code
To reproduce
I keep forgetting about the trailing semicolon and then clients bark at me.
The frustration is stronger when the client is embedded in something heavyweight. like Kafka Connect. Where changes are slow. Even a simple property change.
If we relax it then we should relax it in all clients, not just Java client. To keep conf strings portable.
See questdb/questdb-confstr-rs#3
QuestDB version:
7.4+
OS, in case of Docker specify Docker and the Host OS:
irrelevant
File System, in case of Docker specify Host File System:
irrelevant
Full Name:
Jaromir Hamala
Affiliation:
QuestDB
Have you followed Linux, MacOs kernel configuration steps to increase Maximum open files and Maximum virtual memory areas limit?
Additional context
No response
The text was updated successfully, but these errors were encountered: