NOTE: You are looking at documentation for an older release. For the latest information, see the current release documentation.

« Ingest Node Analysis »

› › ›

Ingest Pipelines

edit

Ingest Pipelines

edit

An ingest pipeline is a series of processors that are to be executed in the same order as they are declared.

Let’s work with the following POCOs

public class Person
{
    public int Id { get; set; }
    public string FirstName { get; set; }
    public string LastName { get; set; }
    public string IpAddress { get; set; }
    public GeoIp GeoIp { get; set; }
}

public class GeoIp
{
    public string CityName { get; set; }
    public string ContinentName { get; set; }
    public string CountryIsoCode { get; set; }
    public GeoLocation Location { get; set; }
    public string RegionName { get; set; }
}

Create an ingestion pipeline

edit

Assuming we are indexing Person documents, we can create an ingestion pipeline that manipulates the incoming values before they are indexed.

Lets assume that our application always expects surnames to be capitalised, and for initials to be indexed into their own field. We also have an IP address that we’d like to convert into a human-readable location.

We could achieve this requirement by creating a custom mapping and creating an ingest pipeline. The Person type can then be used as-is, without making any changes.

client.CreateIndex("people", c => c
    .Mappings(ms => ms
        .Map<Person>(p => p
            .AutoMap() 
            .Properties(props => props
                    .Keyword(t => t.Name("initials")) 
                    .Ip(t => t.Name(dv => dv.IpAddress)) 
                    .Object<GeoIp>(t => t.Name(dv => dv.GeoIp)) 
            )
        )
    )
);

client.PutPipeline("person-pipeline", p => p
    .Processors(ps => ps
        .Uppercase<Person>(s => s
            .Field(t => t.LastName) 
        )
        .Script(s => s
            .Lang("painless") 
            .Source("ctx.initials = ctx.firstName.substring(0,1) + ctx.lastName.substring(0,1)")
        )
        .GeoIp<Person>(s => s 
            .Field(i => i.IpAddress)
            .TargetField(i => i.GeoIp)
        )
    )
);

var person = new Person
{
    Id = 1,
    FirstName = "Martijn",
    LastName = "Laarman",
    IpAddress = "139.130.4.5"
};

var indexResponse = client.Index(person, p => p.Index("people").Pipeline("person-pipeline"));

	automatically create the mapping from the type
	create an additional field to store the initials
	map field as IP Address type
	map GeoIp as object
	uppercase the lastname
	use a painless script to populate the new field
	use ingest-geoip plugin to enrich the GeoIp object from the supplied IP Address
	index the document using the created pipeline

Increasing timeouts

edit

When a pipeline is specified, there will be the added overhead of document enrichment when indexing, the example given above, the execution of the uppercasing and the Painless script.

For large bulk requests, it could be prudent to increase the default indexing timeout to avoid exceptions.

client.Bulk(b => b
    .Index("people")
    .Pipeline("person-pipeline")
    .Timeout("5m") 
    .Index<Person>(/*snip*/)
    .Index<Person>(/*snip*/)
    .Index<Person>(/*snip*/)
    .RequestConfiguration(rc => rc
        .RequestTimeout(TimeSpan.FromMinutes(5)) 
    )
);

	increases the server-side bulk timeout
	increases the HTTP request timeout

« Ingest Node Analysis »