Class IngestService

    • Field Detail


        public static final java.lang.String NOOP_PIPELINE_NAME
        See Also:
        Constant Field Values
    • Method Detail

      • getPipelines

        public static java.util.List<PipelineConfiguration> getPipelines​(ClusterState clusterState,
                                                                         java.lang.String... ids)
        pipeline configuration specified by id. If multiple ids or wildcards are specified multiple pipelines may be returned
      • getPipeline

        public Pipeline getPipeline​(java.lang.String id)
        Returns the pipeline by the specified id
      • getProcessorFactories

        public java.util.Map<java.lang.String,​Processor.Factory> getProcessorFactories()
      • executeBulkRequest

        public void executeBulkRequest​(int numberOfActionRequests,
                                       java.lang.Iterable<DocWriteRequest<?>> actionRequests,
                                       java.util.function.BiConsumer<java.lang.Integer,​java.lang.Exception> onFailure,
                                       java.util.function.BiConsumer<java.lang.Thread,​java.lang.Exception> onCompletion,
                                       java.util.function.IntConsumer onDropped)
      • addIngestClusterStateListener

        public void addIngestClusterStateListener​(java.util.function.Consumer<ClusterState> listener)
        Adds a listener that gets invoked with the current cluster state before processor factories get invoked. This is useful for components that are used by ingest processors, so that they have the opportunity to update before these components get used by the ingest processor factory.
      • applyClusterState

        public void applyClusterState​(ClusterChangedEvent event)
        Description copied from interface: ClusterStateApplier
        Called when a new cluster state (ClusterChangedEvent.state() needs to be applied. The cluster state to be applied is already committed when this method is called, so an applier must therefore be prepared to deal with any state it receives without throwing an exception. Throwing an exception from an applier is very bad because it will stop the application of this state before it has reached all the other appliers, and will likely result in another attempt to apply the same (or very similar) cluster state which might continue until this node is removed from the cluster.
        Specified by:
        applyClusterState in interface ClusterStateApplier
      • getProcessorsInPipeline

        public <P extends Processor> java.util.List<P> getProcessorsInPipeline​(java.lang.String pipelineId,
                                                                               java.lang.Class<P> clazz)
        Gets all the Processors of the given type from within a Pipeline.
        pipelineId - the pipeline to inspect
        clazz - the Processor class to look for
        True if the pipeline contains an instance of the Processor class passed in