Class ParametrizedUriEmitter
java.lang.Object
org.apache.druid.java.util.emitter.core.ParametrizedUriEmitter
- All Implemented Interfaces:
Closeable,Flushable,AutoCloseable,Emitter
-
Constructor Summary
ConstructorsConstructorDescriptionParametrizedUriEmitter(ParametrizedUriEmitterConfig config, org.asynchttpclient.AsyncHttpClient client, com.fasterxml.jackson.databind.ObjectMapper jsonMapper) ParametrizedUriEmitter(ParametrizedUriEmitterConfig config, org.asynchttpclient.AsyncHttpClient client, com.fasterxml.jackson.databind.ObjectMapper jsonMapper, UriExtractor uriExtractor) -
Method Summary
Modifier and TypeMethodDescriptionvoidclose()voidEmit an event.voidflush()voidforEachEmitter(BiConsumer<URI, HttpPostEmitter> action) voidstart()toString()
-
Constructor Details
-
ParametrizedUriEmitter
public ParametrizedUriEmitter(ParametrizedUriEmitterConfig config, org.asynchttpclient.AsyncHttpClient client, com.fasterxml.jackson.databind.ObjectMapper jsonMapper) -
ParametrizedUriEmitter
public ParametrizedUriEmitter(ParametrizedUriEmitterConfig config, org.asynchttpclient.AsyncHttpClient client, com.fasterxml.jackson.databind.ObjectMapper jsonMapper, UriExtractor uriExtractor)
-
-
Method Details
-
start
public void start() -
emit
Description copied from interface:EmitterEmit an event. This method must not throw exceptions or block. If an implementation receives too many events and internal queues fill up, it should drop events rather than blocking or consuming excessive memory. If an implementation receives input it considers to be invalid, or has an internal problem, it should deal with that by logging a warning rather than throwing an exception. Implementations that log warnings should consider throttling warnings to avoid excessive logs, since a busy Druid cluster can emit a high volume of metric events. -
close
public void close() -
flush
public void flush() -
forEachEmitter
-
toString
-