You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is because URL is parsed as LogStash::Util::SafeURI and this class has no empty? method.
if I set "" (documentation says that it is possible), then I get this error at Logstash startup:
Failed to execute action {:action=>LogStash::PipelineAction::Create/pipeline_id:kafka, :exception=>"Java::JavaLang::IllegalStateException", :message=>"Unable to configure plugins: (ArgumentError) URI is not valid - host is not specified"
I guess this is because LogStash::Util::SafeURI does not support an empty string as value.
Logstash information:
Please include the following information:
Logstash version : 7.17.8
Logstash installation source : expanded from tar or zip archive
How is Logstash being run : Via command line
How was the Logstash Plugin installed : default version provided by Logstash 7.17.8 (10.9.0)
JVM (e.g. java -version): OpenJDK 11
2. JVM installation source : AdoptOpenJDK distribution
3. Value of the JAVA_HOME environment variable if set: C:\Developpement\OpenJDK11_x64
OS version (uname -a if on a Unix-like system): Windows 10
Description of the problem including expected versus actual behavior:
Given my tests, "schema_registry_proxy" option does not work on kafka input plugin.
I mean:
It is because URL is parsed as
LogStash::Util::SafeURI
and this class has noempty?
method.""
(documentation says that it is possible), then I get this error at Logstash startup:I guess this is because
LogStash::Util::SafeURI
does not support an empty string as value.Logstash information:
Please include the following information:
JVM (e.g.
java -version
): OpenJDK 112. JVM installation source : AdoptOpenJDK distribution
3. Value of the
JAVA_HOME
environment variable if set: C:\Developpement\OpenJDK11_x64OS version (
uname -a
if on a Unix-like system): Windows 10Description of the problem including expected versus actual behavior:
Steps to reproduce:
Provide logs (if relevant):
Already provided above.
The text was updated successfully, but these errors were encountered: